<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:28:04 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-731] Decide on content of H4 ramp time cards.</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-731</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;What does Subaru want for the H4RG ramp time cards? The PHDU can only know about the starting time stamp: should it only have &lt;tt&gt;MJD-STR&lt;/tt&gt; cards (using &lt;tt&gt;MJD&lt;/tt&gt; as the example one of &lt;tt&gt;MJD,HST,UT,LST&lt;/tt&gt;)? Could also make the case for using straight &lt;tt&gt;MJD&lt;/tt&gt; cards instead of &lt;tt&gt;MJD-STR&lt;/tt&gt; cards.&lt;/p&gt;

&lt;p&gt;The per-read HDUs can obviously know about their start and end times; should they &lt;em&gt;each&lt;/em&gt; have &lt;tt&gt;MJD-STR, MJD, MJD-END&lt;/tt&gt; or is that silly and/or conflicting? Note that the times themselves would be boringly predictable: they will be &lt;em&gt;calculated&lt;/em&gt; from the ramp start and the ramp time, and not by asking a clock for the time.&lt;/p&gt;

&lt;p&gt;Do we want &lt;tt&gt;-END&lt;/tt&gt; cards for the entire ramp? Would that go into the last read&apos;s HDU, or would we add a post-ramp HDU for summary/&quot;at-end&quot; cards?&lt;/p&gt;</description>
                <environment></environment>
        <key id="13717">INSTRM-731</key>
            <summary>Decide on content of H4 ramp time cards.</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="furu">Hisanori Furusawa</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>FITS</label>
                            <label>SPS</label>
                    </labels>
                <created>Thu, 15 Aug 2019 00:30:02 +0000</created>
                <updated>Wed, 24 Mar 2021 15:40:28 +0000</updated>
                            <resolved>Wed, 24 Mar 2021 15:40:28 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="15954" author="furu" created="Thu, 15 Aug 2019 00:46:48 +0000"  >&lt;p&gt;What is the data format for the ramp data? Do they come into a multiple HDUs or separate FITS? MJD is a common but *-STR and *-END are optional, so in general, if the instrument team thinks them unnecessary, they simply put MJD (and the other common counterparts UT, LST, ...) only. If *-STR, *-END are helpful for something, it would be good to put them as well. Coexistence of all three keywords is no-silly and a typical case for the existing instruments. Which HDU they should go in? I&apos;d like to hear @&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=monodera&quot; class=&quot;user-hover&quot; rel=&quot;monodera&quot;&gt;monodera&lt;/a&gt;&apos;s comment from a FITS policy point-of-view, but I don&apos;t think that having these important keywords in every IMAGE HDU is a bad idea.&lt;/p&gt;
</comment>
                            <comment id="15955" author="cloomis" created="Thu, 15 Aug 2019 03:05:55 +0000"  >&lt;p&gt;For the PFSB ramp files, one HDU per read.&lt;/p&gt;</comment>
                            <comment id="15977" author="cloomis" created="Thu, 22 Aug 2019 22:16:36 +0000"  >&lt;p&gt;If we know both start and end times we will have, for each of &lt;tt&gt;MJD, LST, HST, UT&lt;/tt&gt;, a &lt;tt&gt;MJD-STR&lt;/tt&gt;, &lt;tt&gt;MJD&lt;/tt&gt;, &lt;tt&gt;MJD-END&lt;/tt&gt; card. Easy.&lt;/p&gt;

&lt;p&gt;What card should there be if we only know the start time? If we use &lt;tt&gt;MJD&lt;/tt&gt;, then the &lt;em&gt;meaning&lt;/em&gt; of that card is &quot;start of exposure&quot; in some headers, and &quot;middle of exposure&quot; on others. So &lt;tt&gt;MJD-STR&lt;/tt&gt;?&lt;/p&gt;</comment>
                            <comment id="18966" author="hassan" created="Wed, 24 Mar 2021 15:40:28 +0000"  >&lt;p&gt;Implemented as proposed.&lt;/p&gt;</comment>
                    </comments>
                    <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|zzs2xr:zzr</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="88">SM1PD-2020 M</customfieldvalue>
    <customfieldvalue id="91">SM1PD-2020 N</customfieldvalue>
    <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>

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