<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:34:48 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>[DAMD-151] Please add information about broken cobras to pfsDesign files</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/DAMD-151</link>
                <project id="10400" key="DAMD">Data Model</project>
                    <description>&lt;p&gt;We need to track broken cobras in the reductions (as e.g. we cannot get good fibre profiles).  They will probably mostly be UNASSIGNED, but maybe sometimes usable as SKY. Note that broken cobras with broken (or cut?) fibres are already marked as BROKENFIBER and that this ticket is about fibres that don&apos;t move properly, but which carry good fibres.&lt;/p&gt;

&lt;p&gt;There are three cases:  both axes (theta and phi) are broken so the cobra cannot move, and those with one broken motor, either theta or phi.  The latter can be moved away from stars, while the former can happen to lie near bright stars or galaxies.&lt;/p&gt;

&lt;p&gt;It&apos;s tempting to simply add BROKENCOBRA, BROKENCOBRA_PHI, and BROKEN_COBRA_THETA to pfsDesign.fiberStatus, and I think that this is probably the right solution as although in theory we might want to say, &quot;BROKENCOBRA and BLOCKED&quot; it seems unlikely in practice.  &lt;/p&gt;

&lt;p&gt;The added complexity of adding another HDU doesn&apos;t seem worth it.  However, if we define these enum values use high bits (e.g. &lt;tt&gt;BROKENCOBRA = 0x1000&lt;/tt&gt; ) we could decide to use e.g. &lt;tt&gt;fiberStatus = BLOCKED &amp;amp; BROKENCOBRA&lt;/tt&gt; if the need arises.&lt;/p&gt;</description>
                <environment></environment>
        <key id="23763">DAMD-151</key>
            <summary>Please add information about broken cobras to pfsDesign files</summary>
                <type id="10001" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10515&amp;avatarType=issuetype">Story</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="-1">Unassigned</assignee>
                                    <reporter username="rhl">rhl</reporter>
                        <labels>
                    </labels>
                <created>Fri, 28 Jul 2023 04:18:19 +0000</created>
                <updated>Fri, 28 Jul 2023 04:18:19 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                        <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|zzsz2v:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>