<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:28:25 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-764] Reconsider FiberPosition, CobraPosition, and FiducialFiberPosition tables</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-764</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;There&apos;s a lot of overlap between these tables, and the naming of fields is confusing.  I think that the &lt;tt&gt;fiberId&lt;/tt&gt; is a unique int from FiberPosition (although it&apos;s only 4 bytes); what I&apos;m proposing calling &lt;tt&gt;FiberPositionSerial&lt;/tt&gt; in &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-762&quot; title=&quot;Reconsider unique columns in e.g. mcsData&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-762&quot;&gt;&lt;del&gt;INSTRM-762&lt;/del&gt;&lt;/a&gt;) which is confusing as elsewhere I think &lt;tt&gt;fiberId&lt;/tt&gt; is used to refer to a cobra &amp;#8211; maybe we should use cobraId consistently (and not worry about the fact that they are spots, not cobras, in the engineering mask!).  Or maybe I don&apos;t understand the point of &lt;tt&gt;fiberId&lt;/tt&gt; as we are not currently moving things;  is it intended to be the &quot;ID for a given cobra/fiducial for this visit&quot;? If so, I think we should come up with a better name.&lt;/p&gt;

&lt;p&gt;It looks to me as if FiberPosition is the union of the cobra and fiducial position tables for a given visit &amp;#8211; is that right?  If so, we really need it?  &lt;/p&gt;

&lt;p&gt;At the very least the column names in all these tables need to be expanded!&lt;/p&gt;</description>
                <environment></environment>
        <key id="13754">INSTRM-764</key>
            <summary>Reconsider FiberPosition, CobraPosition, and FiducialFiberPosition tables</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="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="kiyoto.yabe">Kiyoto Yabe</assignee>
                                    <reporter username="rhl">rhl</reporter>
                        <labels>
                    </labels>
                <created>Sat, 7 Sep 2019 15:59:49 +0000</created>
                <updated>Tue, 24 Dec 2019 01:18:47 +0000</updated>
                            <resolved>Tue, 24 Dec 2019 01:18:46 +0000</resolved>
                                                                    <component>spt_operational_database</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                    <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="14117">INSTRM-844</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="13718">INSTRM-732</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|zy00bc:</customfieldvalue>

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