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-1446 Instrument control development <p>We need to start thinking about how we send pfsConfig files to STARS.  In the short run, please pass all files to gen2 as soon as the cobra moves have finished.</p> <p>If STARS would like to start accepting these files that would be fine with PFS, but we don't want to spend a lot of time convincing STARS that the file format is acceptable at this time.</p> INSTRM-1446

Pass pfsConfig files to Gen2

Story Normal Done Done cloomis rhl EngRun Sun, 14 Nov 2021 02:13:13 +0000 Wed, 1 Mar 2023 09:46:28 +0000 Wed, 1 Mar 2023 09:46:28 +0000 0 3 <p>The current files have been deemed acceptable as-is.</p> <p>So adding a trigger for the <tt>iic.pfsConfig</tt> key, e.g. <tt>pfsconfig=0x2e772c5f91c219aa,86051,2023-02-09,100.000000,100.000000,0.000000,mergedSunSSAndDCB,0x0000000000000000,0</tt> which will request that <tt>/data/raw/2023-02-09/pfsConfig/pfsConfig-0x2e772c5f91c219aa-086051.fits</tt> be archived.</p> <p>Ticket parked for now: the MHS keyword is parsed and triggers some action. But archiving <tt>pfsConfig</tt> files via Gen2 will not work. We will need to either archive outside Gen2, or rename the files to, say, <tt>PFSE-{visit}00.fits</tt>. If we do that the frame allocator will need to request <tt>PFSE</tt> ids as well as the ones we already get. Not a big deal.</p> <p>Craig, Eric-san, Pyo-san and I had a meeting. Here is a notes:</p> <ul> <li>Basically as long as the file format is FITS, we should follow the regulation <ul> <li>Name should be PFS{A-Z} {visit:06d} <p>00.fits (Note, E, Q, Z are reserved.) -&gt; we agreed to use <b>"F"</b></p></li> <li>Primary HDU should have important header cards (e.g. framId, proposal ID, observation datetime).</li> <li>Since HIERARCH keys are not allowed by STARS/SMOKA, there may be a concern....</li> </ul> </li> <li>To archive pfsConfig file, PFS side can keep the name, and only need to send frameId and path.</li> <li>Gen2 can rename the file to "PFSF{visit:06d}00.fits" on its side for archive to STARS/SMOKA. <ul> <li>A mechanism needs to be developed to use pfsConfig file by renaming again.</li> </ul> </li> </ul> <p>Note from the result of 2023 February run (Run10)</p> <ul> <li>pfsConfig files (PFSF*fits) were transferred to Gen2/STARS</li> <li>PFSF*.fits passed verification on STARS, but failed to register, because some headers (namely, <tt>DATA-TYP</tt>, <tt>EQUINOX</tt>, <tt>RA2000</tt>, <tt>DEC2000</tt>, <tt>RADECSYS</tt>, <tt>WCS-ORIG</tt>) are missing. These cards are basically assumed the file is for the detector data.</li> </ul> <p>We need discussions for archiving on STARS, but this is beyond of this ticket. </p> <p>We should probably set <tt>DATA-TYP</tt>. We could set the others too, if empty/undefined (however FITS wants to specify that) is an allowed value.</p> <p>If this is out of this ticket's scope (as it probably is), we should link the correct ticket to this one.</p> <p>As pfsConfig sent to Gen2, I close this ticket. The missing header cards will be handled with <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1875" title="missing pfsConfig (PFSF*fits) headers to archive on STARS" class="issue-link" data-issue-key="INSTRM-1875"><del>INSTRM-1875</del></a></p> Blocks INSTRM-1863 Development Rank 0|02qpjd:00r3000l Sprint PreEngRun4 PreEngRun10Feb