<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:32:16 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-1138] Update grandfibermap to describe all slit holes, and with complete connector mappings.</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1138</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;The current grandfibermap only describes the science fibers: all fibers which are terminated at a cobra. We need to have a map which describes all the slit holes, including the engineering and blank fibers.&lt;/p&gt;

&lt;p&gt;Also, recent work has shown that some of the gang connector mappings might not not correct? These are necessary to map SuNSS fibers to the right slit holes, regardless of the chosen module, since we essentially replace one module&apos;s B-C segment with a B-to-S(unSS) segment.&lt;/p&gt;

&lt;p&gt;grandfibermap is generated using JEG code. I imagine that code should be updated and rerun. If it is surgically exciseable we probably should do so and recode it in pfs_utils or somewhere like that. Some of us even like Forth!&lt;/p&gt;</description>
                <environment></environment>
        <key id="15095">INSTRM-1138</key>
            <summary>Update grandfibermap to describe all slit holes, and with complete connector mappings.</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="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="yuki.moritani">yuki.moritani</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>SPS</label>
                            <label>SuNSS</label>
                    </labels>
                <created>Thu, 10 Dec 2020 01:13:12 +0000</created>
                <updated>Thu, 6 May 2021 20:43:38 +0000</updated>
                            <resolved>Wed, 28 Apr 2021 11:15:29 +0000</resolved>
                                                                    <component>pfs_utils</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                <comments>
                            <comment id="18159" author="cloomis" created="Fri, 11 Dec 2020 00:50:13 +0000"  >&lt;p&gt;And a side note: the existing &quot;mod&quot; column is pretty confusing. Both Chi-Hung and I assumed that it referred to the A and B boards on the 1-42 modules, and we expected the fiber number within a &quot;mod&quot; to increment along the boards, but it turns out to refer to a fiber bundle id, and the fiber numbers zig-zag between boards along the module.&lt;/p&gt;

&lt;p&gt;It would be nice to have a &quot;board&quot; column with the module-board ID.&lt;/p&gt;</comment>
                            <comment id="18161" author="hassan" created="Fri, 11 Dec 2020 02:05:34 +0000"  >&lt;p&gt;Assigned ticket to &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=yuki.moritani&quot; class=&quot;user-hover&quot; rel=&quot;yuki.moritani&quot;&gt;yuki.moritani&lt;/a&gt;, with support from &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=jeg&quot; class=&quot;user-hover&quot; rel=&quot;jeg&quot;&gt;jeg&lt;/a&gt; and &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis&quot; class=&quot;user-hover&quot; rel=&quot;cloomis&quot;&gt;cloomis&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="18400" author="price" created="Wed, 27 Jan 2021 20:23:15 +0000"  >&lt;p&gt;Please note that there are some changes in &lt;tt&gt;tickets/&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/DAMD-96&quot; title=&quot;Index fibers from multiple spectrographs in PfsDesign&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DAMD-96&quot;&gt;&lt;del&gt;DAMD-96&lt;/del&gt;&lt;/a&gt;&lt;/tt&gt;.&lt;/p&gt;</comment>
                            <comment id="18547" author="yuki.moritani" created="Wed, 17 Feb 2021 15:04:41 +0000"  >&lt;p&gt;Here is another comment in &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-1124&quot; title=&quot;Update grandfibermap with all Cable A-B, B-C, B-S interface mappings&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-1124&quot;&gt;&lt;del&gt;INSTRM-1124&lt;/del&gt;&lt;/a&gt; About the column for the cobra:&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Two small-ish requests. If we do these now I think we only need to update the datafile and the code once for a group of similar issues:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;could you add a &quot;module&quot; columns which would be 1-42 module number. ($fld-1)*42 + $mf, I think.&lt;/li&gt;
	&lt;li&gt;could you add a &quot;board number&quot; column (1A, 1B, ... 42A, 42B), where the board is A if $cm is odd, B if $cm is even. Or I guess just A/B, and we could use the &quot;module&quot; column for the module.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The remaining item for GFM or an associated table is how to encode the engineering fibers and the blanks, so that every slit hole can be described.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Note: grandfibermap needs to be updated following the latest cable A-B-C connection configuration.&lt;/p&gt;</comment>
                            <comment id="19233" author="yuki.moritani" created="Wed, 28 Apr 2021 11:15:29 +0000"  >&lt;p&gt;handled with &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-1195&quot; title=&quot;Update grandfibermap following the recent discussions and requests&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-1195&quot;&gt;&lt;del&gt;INSTRM-1195&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="15051">INSTRM-1124</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="15403">INSTRM-1195</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="15047">DAMD-96</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|zzs4y7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="97">SM1PD-2021 A</customfieldvalue>
    <customfieldvalue id="99">SM1PD-2021 A 2</customfieldvalue>
    <customfieldvalue id="100">SM1PD-2021 A 3</customfieldvalue>
    <customfieldvalue id="101">SM1PD-2021 A 4</customfieldvalue>
    <customfieldvalue id="103">SM1PD-2021 A 5</customfieldvalue>
    <customfieldvalue id="104">SM1PD-2021 A 6</customfieldvalue>
    <customfieldvalue id="106">SM1PD-2021 A7</customfieldvalue>
    <customfieldvalue id="107">SM1PD-2021 A8</customfieldvalue>

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