<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:26:40 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-596] Arrange to create a 2d PFSA file for each 3d PFSB file</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-596</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;The hxActor currently writes PFSB files only: the full ramp. We have planned to also write PFSA files: single image versions reduced from the full stack.&lt;/p&gt;

&lt;p&gt;Note that we never settled on exactly &lt;em&gt;what&lt;/em&gt; to write. A reality is that the DAQ BEEs most certainly do not have enough CPU or RAM to compute more than lastRead-firstRead (or the only read), so that&apos;s what we start with. &lt;/p&gt;

&lt;p&gt;One concern is that &quot;A&quot; files from Subaru could be seen as the &quot;correct&quot; raw instrument files, just from past convention. I&apos;ll state that any proper 3d-to-2d reduction is almost certain to evolve, so there might never be a &lt;em&gt;dependably&lt;/em&gt; stable science-grade 2d product: it will always depend on a particular version of the 2D DRP pipeline. [ Besides, any good reduction will come with (at least) both variance and mask images. ]&lt;/p&gt;

&lt;p&gt;I suppose we could call any such quick raw 2d reductions something other than &quot;PFSA&quot; files, and simply not write &quot;PFSA&quot; files for the NIR arms?&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=rhl&quot; class=&quot;user-hover&quot; rel=&quot;rhl&quot;&gt;rhl&lt;/a&gt;, &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=furu&quot; class=&quot;user-hover&quot; rel=&quot;furu&quot;&gt;Hisanori Furusawa&lt;/a&gt;, &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=eric&quot; class=&quot;user-hover&quot; rel=&quot;eric&quot;&gt;eric&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="13235">INSTRM-596</key>
            <summary>Arrange to create a 2d PFSA file for each 3d PFSB file</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="10100" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="No further work should be done on this.">Won&apos;t Fix</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="cloomis">cloomis</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>NIR</label>
                            <label>SPS</label>
                    </labels>
                <created>Fri, 11 Jan 2019 21:52:59 +0000</created>
                <updated>Fri, 21 Apr 2023 01:03:46 +0000</updated>
                            <resolved>Wed, 17 Nov 2021 20:50:36 +0000</resolved>
                                                                    <component>ics_hxActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="15145" author="hassan" created="Wed, 20 Mar 2019 15:10:41 +0000"  >&lt;p&gt;Finish that this week.&lt;/p&gt;</comment>
                            <comment id="15329" author="hassan" created="Wed, 17 Apr 2019 15:18:51 +0000"  >&lt;p&gt;Simple case done; interleaved reference pixel situation needs to be implemented.&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; will break this into separate tickets.&lt;/p&gt;</comment>
                            <comment id="18132" author="cloomis" created="Wed, 9 Dec 2020 15:42:15 +0000"  >&lt;p&gt;The main question still holds. PFSB files holds all the raw data, and we cannot generate anything other than a quick and preliminary CDS files for the entire ramp.&lt;/p&gt;

&lt;p&gt;I think we will need a quick CDS image, but there are strong arguments for not creating official PFSA files from them. We currently do, but they are not documented in datamodel.txt. Should I just call them something else? What?&lt;/p&gt;</comment>
                            <comment id="18435" author="cloomis" created="Wed, 3 Feb 2021 16:34:20 +0000"  >&lt;p&gt;I think this must be an NAOJ question, and the original description still holds. &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=furu&quot; class=&quot;user-hover&quot; rel=&quot;furu&quot;&gt;Hisanori Furusawa&lt;/a&gt;? &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=eric&quot; class=&quot;user-hover&quot; rel=&quot;eric&quot;&gt;eric&lt;/a&gt;?&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;We do currently generate a preliminary (lastRead-firstRead) FITS file, currently named PFSA. These are very practical to have available, but are not science-quality. The instrument cannot improve on the content.&#160;&lt;/p&gt;</comment>
                            <comment id="18440" author="eric" created="Thu, 4 Feb 2021 21:04:42 +0000"  >&lt;p&gt;For traditional Subaru instruments, &quot;A&quot; files are raw data, while &quot;Q&quot; files are quick reduced data.&#160; Both kinds are distributed using the data traversal mechanism of Gen2.&#160; For some instruments, the Q files are archived to STARS, and for some instruments they are not&#8211;this is generally dependent on whether the developers put in any work to make the FITS headers compliant enough to make the data archive people happy.&lt;/p&gt;

&lt;p&gt;I think it would be useful to create such quick reduction files, available to the observers at least during the night. These could be displayed, or have special GUIs to show tables out of them, create graphs or what not.&lt;/p&gt;</comment>
                            <comment id="18442" author="cloomis" created="Thu, 4 Feb 2021 21:37:04 +0000"  >&lt;p&gt;OK, so we could name them PFSQ files. &lt;/p&gt;

&lt;p&gt;In that case, should the (currently off-site only) PFSB ramp files be renamed to PFSA? They are wildly different from normal CCD images and in general pretty inconvenient (~3GB, with ~100 HDU, and no HDU looking like a normal image). The nature of &lt;tt&gt;PFSA*&lt;/tt&gt; would surely surprise people. &lt;/p&gt;

&lt;p&gt;Since we have not yet taken NIR data at Subaru I think we are still free to rename.&lt;/p&gt;</comment>
                            <comment id="25129" author="cloomis" created="Wed, 17 Nov 2021 20:50:36 +0000"  >&lt;p&gt;We long ago decided not to create single image PFSA files for the H4 ramps: if written by the ICS they can only be poor approximations, but by virtue of being named &quot;PFSA&quot; could easily be viewed as real data.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="14686">INSTRM-1061</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="11137">DAMD-7</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23365">INSTRM-1928</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|02qppn:4</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="33">2019 C</customfieldvalue>
    <customfieldvalue id="47">SM1-2019 E</customfieldvalue>
    <customfieldvalue id="48">SM1-2019 F</customfieldvalue>
    <customfieldvalue id="50">SM1-2019 G</customfieldvalue>
    <customfieldvalue id="84">SM1PD-2020 K</customfieldvalue>
    <customfieldvalue id="88">SM1PD-2020 M</customfieldvalue>
    <customfieldvalue id="89">SM1PD-2020 L</customfieldvalue>
    <customfieldvalue id="91">SM1PD-2020 N</customfieldvalue>
    <customfieldvalue id="92">SM1PD-2021 A 12</customfieldvalue>
    <customfieldvalue id="97">SM1PD-2021 A</customfieldvalue>
    <customfieldvalue id="99">SM1PD-2021 A 2</customfieldvalue>
    <customfieldvalue id="100">SM1PD-2021 A 3</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>