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-1427 Instrument control development <p><a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1420" title="Publish final `pfsConfig` and `pfsDesign` FITS files, before taking sps/fps/mcs/agcc exposures." class="issue-link" data-issue-key="INSTRM-1420"><del>INSTRM-1420</del></a> lists 3 tasks that needs to be done in terms of publishing <tt>pfsDesign</tt> and <tt>pfsConfig</tt> files for different light sources.</p> <p>For the upcoming November Engineering Run, please implement the last, most important task described in the above ticket, and only for <tt>pfsConfig</tt> files as standalone <tt>pfsDesign</tt> files are not needed for DRP. Namely:</p> <p>When the `pfi` is the only light source, simply copy/link the <tt>pfsConfig</tt> from the <tt>fpsActor</tt> output.</p> INSTRM-1427

Publish pfsConfig files when the PFI is light source

Task Normal Done Done arnaud.lefur hassan EngRun Mon, 1 Nov 2021 16:35:44 +0000 Thu, 13 Oct 2022 15:35:05 +0000 Thu, 13 Oct 2022 15:35:05 +0000 0 2 <p>We have agreed that the fpsActor will write the pfsConfig outputs directly into <tt>/data/raw/pfsConfig//</tt> : that step is what defines "publishing" a pfsConfig. So no copy/link, just a change to the fpsActor.</p> <p>In the case where we have multiple light sources, IIC will possible generate other pfsConfig files. That is covered by <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1420" title="Publish final `pfsConfig` and `pfsDesign` FITS files, before taking sps/fps/mcs/agcc exposures." class="issue-link" data-issue-key="INSTRM-1420"><del>INSTRM-1420</del></a>.</p> <p>covered by <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1691" title="write pfsConfig with actual cobra position" class="issue-link" data-issue-key="INSTRM-1691"><del>INSTRM-1691</del></a></p> Relates INSTRM-1348 INSTRM-1420 Development Rank 0|02qpjd:00r3000i Sprint PreEngRun4 Story Points 1.0