<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:34:37 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-135] RFC: Allow empty (NAXIS=0) REF HDUs for PFSB ramps</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/DAMD-135</link>
                <project id="10400" key="DAMD">Data Model</project>
                    <description>&lt;p&gt;We currently always save full 4k images for the &quot;REF&quot; IRP HDUs in the PFSB files; when we do not acquire an IRP plane we write a full image of 0-valued pixels. The intent was to make all ramp files look the same regardless of whether IRP was used during acquisition.&lt;/p&gt;

&lt;p&gt;But it turns out that we might not use IRP, and that PFSB simplification comes with some overhead. Yes, RICE compression shrinks all-0 images to ~300k HDUs, but they still need to be read in, etc. &lt;span class=&quot;error&quot;&gt;&amp;#91;and it turns out that the standard IDL FITS I/O routines find this all very expensive&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;Besides, given how we process ramps there might be value in memory-mapping uncompressed PFSB files instead of RICE-compressing. In which case expanding empty REF HDUs to a full 32MB on disk would be significant.&lt;/p&gt;

&lt;p&gt;So I propose writing &quot;empty&quot; HDUs for IRP=0 REF frames, specifically by setting NAXIS=0. Both astropy and (c)fitsio (what the DAQ uses) are happy reading and writing these, accepting and returning None to the various routines. A minor difference is that astropy sets BITPIX=8 and (c)fitsio sets BITPIX=16, but I don&apos;t think that is in any way significant.&lt;/p&gt;

&lt;p&gt;Robert and I have talked about the (fairly minor) DRP changes which would be required. This is FITS-compliant, but I&apos;d like to check with NAOJ. &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;&#160;?&lt;/p&gt;</description>
                <environment></environment>
        <key id="22917">DAMD-135</key>
            <summary>RFC: Allow empty (NAXIS=0) REF HDUs for PFSB ramps</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="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="cloomis">cloomis</reporter>
                        <labels>
                    </labels>
                <created>Thu, 18 Aug 2022 17:45:56 +0000</created>
                <updated>Sun, 2 Oct 2022 01:50:29 +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|02qpjd:00r20061</customfieldvalue>

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