<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:24:45 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-414] Add FITS fields to actorkeys dictionaries.</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-414</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;Now that &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-236&quot; title=&quot;Add .fitsCard field to KeyDictionary definitions.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-236&quot;&gt;&lt;del&gt;INSTRM-236&lt;/del&gt;&lt;/a&gt; is done, populate the actorkeys dictionaries for all the actors whose status will go into a FITS file.  For SPS, at least &lt;tt&gt;ics_enuActor&lt;/tt&gt;, &lt;tt&gt;ics_xcuActor&lt;/tt&gt;.&lt;/p&gt;

&lt;p&gt;Yes I should write real documentation, but will sketch that out here for now.&lt;/p&gt;

&lt;p&gt;Most FITS cards will come &lt;em&gt;directly&lt;/em&gt; from actorkeys annotations. Each individual field in a keyword has grown a &lt;tt&gt;FITS&lt;/tt&gt; option, which must be a pair of names: one a proper 8-character SUBARU PFS card name and the other a longer, more descriptive one. As an example, from the &lt;tt&gt;meb&lt;/tt&gt; dictionary:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
Key(&lt;span class=&quot;code-quote&quot;&gt;&apos;flow&apos;&lt;/span&gt;,
       &lt;span class=&quot;code-object&quot;&gt;Float&lt;/span&gt;(name=&lt;span class=&quot;code-quote&quot;&gt;&apos;Flow_meter&apos;&lt;/span&gt;, units=&lt;span class=&quot;code-quote&quot;&gt;&apos;Hz&apos;&lt;/span&gt;,
             help=&lt;span class=&quot;code-quote&quot;&gt;&apos;Flow meter reading&apos;&lt;/span&gt;,
             FITS=(&lt;span class=&quot;code-quote&quot;&gt;&apos;W_MCFLOW&apos;&lt;/span&gt;, &lt;span class=&quot;code-quote&quot;&gt;&apos;MCS_COOLANT_FLOW&apos;&lt;/span&gt;))),
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;would automatically generate a FITS card like:&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;W_MCFLOW=             1.2 / &lt;span class=&quot;error&quot;&gt;&amp;#91;Hz&amp;#93;&lt;/span&gt; Flow meter reading&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;Note that both &lt;tt&gt;units&lt;/tt&gt; and &lt;tt&gt;help&lt;/tt&gt; are picked up. Beware that comments will be truncated at the usual 80 characters, so you need to keep the &lt;tt&gt;help&lt;/tt&gt; field concise.&lt;/p&gt;

&lt;p&gt;The biggest constraint is on the short name, which &lt;b&gt;must&lt;/b&gt; start with &lt;tt&gt;W_&lt;/tt&gt; and &lt;b&gt;must&lt;/b&gt; be no longer than 8 characters. So far I have tried to indicate the subsystem in the first character or two (&quot;MC&quot; for the MCS camera), and possibly a type in the last character (&quot;T&quot; for temperature, say). Doesn&apos;t leave much.&lt;/p&gt;

&lt;p&gt;The longer name should be a little more descriptive. Grab a prefix like &lt;tt&gt;MCS&lt;/tt&gt;, and make sensible names using {&lt;em&gt;} separated words. Not _too&lt;/em&gt; long &amp;#8211; the name eats into the comment space. We had hoped to use these as HIERARCH cards, but I think we are giving up on that. &lt;/p&gt;

&lt;p&gt;The &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-236&quot; title=&quot;Add .fitsCard field to KeyDictionary definitions.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-236&quot;&gt;&lt;del&gt;INSTRM-236&lt;/del&gt;&lt;/a&gt; routines can create a long-to-short name mapping HDU, and I think will: 6 characters is simply too short to give meaningful names.&lt;/p&gt;

&lt;p&gt;The &lt;tt&gt;ics_actorkeys&lt;/tt&gt; dictionaries then become the reference location for most FITS cards. The camera actors will insert their own cards via a different mechanism, for values we probably do not want as MHS keywords (the many internal voltages, say). Maybe we do.&lt;/p&gt;</description>
                <environment></environment>
        <key id="12631">INSTRM-414</key>
            <summary>Add FITS fields to actorkeys dictionaries.</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="-1">Unassigned</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>FITS</label>
                            <label>SM1</label>
                    </labels>
                <created>Wed, 11 Jul 2018 16:18:08 +0000</created>
                <updated>Thu, 9 May 2019 14:42:56 +0000</updated>
                            <resolved>Thu, 20 Dec 2018 21:22:35 +0000</resolved>
                                                                    <component>ics_actorkeys</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="14728" author="cloomis" created="Thu, 20 Dec 2018 21:22:35 +0000"  >&lt;p&gt;Most of the actorkeys dictionaries have been updated. &lt;br/&gt;
The remaining work is in &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-429&quot; title=&quot;Convert ccd and hx actors to use .FITS actorkeys annotations&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-429&quot;&gt;&lt;del&gt;INSTRM-429&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="11345">INSTRM-25</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="12647">INSTRM-427</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="12648">INSTRM-428</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="12649">INSTRM-429</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="11946">INSTRM-236</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_10006" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>INSTRM-510</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|02qpuc:i6i</customfieldvalue>

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