https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-1875 Instrument control development <p>As reported on <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1446" title="Pass pfsConfig files to Gen2" class="issue-link" data-issue-key="INSTRM-1446"><del>INSTRM-1446</del></a>, pfsConfig files (PFSF*fits) failed to archive on STARS because of missing header cards, namely <tt>DATA-TYP</tt>, <tt>EQUINOX</tt>, <tt>RA2000</tt>, <tt>DEC2000</tt>, <tt>RADECSYS</tt>, <tt>WCS-ORIG</tt></p> <p>Note that FITS committee is thinking there are many constraints to archive the metadata like the pfsConfig files in the same framework as the detector data, and  trying to discuss how to archive the metadata. </p> <p> </p> <p>Note: as commented below <tt>RA, DEC, DATE-OBS, EQUINOX, DATA-TYP, PROP-ID, FRAMEID</tt> cards should be sorted out.</p> INSTRM-1875

missing pfsConfig (PFSF*fits) headers to archive on STARS

Task Normal Done Done cloomis yuki.moritani EngRun FITS Wed, 1 Mar 2023 09:44:45 +0000 Thu, 6 Apr 2023 20:58:22 +0000 Thu, 6 Apr 2023 19:56:11 +0000 0 2 <p>We certainly can easily add more of the <tt>gen2</tt> card block as seen in the PFSA files, which would include most of those cards.</p> <p>But I think a basic question is whether we just need to add a few more cards or whether the required card list is actually the full <tt>Common</tt> list in the NAOJ <a href="https://www.naoj.org/Observing/fits/data/basic_keyword_dictionary.html" class="external-link" rel="nofollow">Subaru Telescope Basic FITS Header Keyword Dictionary</a>. If that <tt>Common</tt> list only applied to files with <b>image data</b> we would be fine, but it currently is required from <b>all</b> FITS files, and I think is what the STARS acceptance scripts are based on. </p> <p>That declared <tt>WCS-ORIG</tt> requirement worries me – does that imply that we will be asked for a WCS? Since we have no image data even a false WCS makes little sense – what would CRPIX1 refer to? Is that even legal?</p> <p>None of the NAOJ-approved values for <tt>DATA-TYP</tt> look right to me. Since we are archiving one PFSF per PFSA file we could use the SPS DATA-TYP, I suppose. "None" has been suggested, but is not in the NAOJ list.</p> <p>For SPS-aligned PFSA visits we could add the expected <tt>EXPTIME</tt>. We could also add HST/UT/LST timestamps which would be a handful of seconds off the real value, or could describe when the cobras were moved. But these cards are getting far from the real <tt>pfsConfig</tt> content....</p> <p>I know that we want to quickly help this process along, but can we find out what the final requirements are before we do any further work? The requested list is, after all, a list we got after implementing <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1863" title="Add a few FITS header to pfsConfig file" class="issue-link" data-issue-key="INSTRM-1863"><del>INSTRM-1863</del></a></p> <p>From follow-up conversations with Pyo-san and the Subaru FITS committee, the following 7 cards are requested as minimum requirement to archive. :  RA, DEC, DATE-OBS, EQUINOX, DATA-TYP, PROP-ID, FRAMEID</p> <ul> <li>RA, DEC: the command (design) positions are set although Subaru's definition is the real positions. FITS committee allow us to keep command value (=designed value) but told us to put a comment that these are  command value . Unit should be sexagesimal.</li> <li>EQUINOX: as long as RA,DEC is used for pointing telescope, they ask us to set "J2000" (fixed).</li> <li>DATA-TYP: set META_{TATA-TYP of PFSA file}</li> <li>(DATE-OBS, PROP-ID, FRAMEID: already implemented)</li> </ul> <p>DATA-TYP and EQUINOX added to <tt>ics_utils</tt>.</p> <p>Any changes to RA/DEC would be done to <tt>datamodel</tt>, not <tt>ics_utils</tt>. I will point out that any conversion to sexagesimal would be hidden behind the datamodel persistence code &#8211; it can be done.</p> <p>ics_utils tagged 1.6.11</p> <p>If we will need RA and DEC formatting changed to sexagesimal, that should be filed as a <tt>datamodel</tt> ticket.</p> <p>Just for recording, STARS will accept RA,DEC in deg format. But we still need to modify the comments.</p> <p> </p> Blocks INSTRM-1913 Development Rank 0|02qpjd:00r3000k0012m Sprint PreEng11Apr1