<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:33:56 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INSTRM-1299] Creation of PfsConfig files for SuNSS/DCB data </title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1299</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;Currently we are using the &lt;tt&gt;0xdeadbeef&lt;/tt&gt; PfsConfig file for SuNSS data. This will need to change once we take into account the SuNSS rotator. Please provide a scheme taking this into account.&lt;/p&gt;

&lt;p&gt;Quoting from a comment from  &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=rhl&quot; class=&quot;user-hover&quot; rel=&quot;rhl&quot;&gt;rhl&lt;/a&gt; in &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/DAMD-91&quot; title=&quot;Update datamodel (pfsDesign/config) to support SuNSS mode&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DAMD-91&quot;&gt;&lt;del&gt;DAMD-91&lt;/del&gt;&lt;/a&gt;, which still needs to be followed up:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;With the current proposal to drive SuNSS to the appropriate hardstop at the beginning of each exposure (or possibly pointing) the rotator angle will not be known until we start observing. I think that this can be handled by having a standard pfsDesign for SuNSS which is converted to pfsConfig once the angle is known. Ideally this only matters for SuNSS&apos;s imaging leg, but that depends on the uniformity of the diffused illumination. This relies on knowing the position angle sufficiently accurately which is not, I think, a problem. If we need a better measurement I suspect that we can get it from a short n channel integration summed in the wavelength direction.&lt;/p&gt;

&lt;p&gt;There is one major difference from regular PFS operations, namely that we cannot specify the fiberId in the pfsDesign file because we don&apos;t control the rotator angle. I think this is OK; we&apos;d set it to -1 (a number which will have to go into the datamodel; real IDs start at 1 so 0 would be an option, but -1 seems safer to me as it&apos;s obviously invalid) and the real fiberId would be written by the code that writes the pfsConfig. Who owns the code that does this transformation? I assume that it&apos;s usually done as part of cobra configuration.&lt;/p&gt;&lt;/blockquote&gt;</description>
                <environment></environment>
        <key id="16900">INSTRM-1299</key>
            <summary>Creation of PfsConfig files for SuNSS/DCB data </summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="1" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="arnaud.lefur">arnaud.lefur</assignee>
                                    <reporter username="hassan">hassan</reporter>
                        <labels>
                            <label>SPS</label>
                            <label>SuNSS</label>
                    </labels>
                <created>Mon, 21 Jun 2021 18:38:41 +0000</created>
                <updated>Thu, 21 Sep 2023 20:05:58 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="21549" author="cloomis" created="Mon, 21 Jun 2021 18:40:04 +0000"  >&lt;p&gt;Surely this is an INSTRM ticket, no?&lt;/p&gt;</comment>
                            <comment id="21550" author="hassan" created="Mon, 21 Jun 2021 18:41:41 +0000"  >&lt;p&gt;You are right. Done.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="15637">INSTRM-1278</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|02qppu:c</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        </customfields>
    </item>
</channel>
</rss>