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-1802 Instrument control development <p>fps write pfsConfig for each convergence, but since sps can take multiple visits with the same designId, that's not enough.</p> <p>IIC needs to be make sure that associated pfsConfig is created whenever sps takes an exposure.<br/> Those would be written to /data/raw/$DATE/pfsConfig.<br/> Would drp be able to ingest that <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=price" class="user-hover" rel="price">price</a> ?</p> INSTRM-1802

write actual pfsConfig for each sps exposure.

Task Normal Done Done arnaud.lefur arnaud.lefur EngRun Wed, 23 Nov 2022 01:56:11 +0000 Tue, 13 Dec 2022 18:03:01 +0000 Tue, 13 Dec 2022 18:01:42 +0000 ics_iicActor 0 2 <p>The original pfsConfig design uses visit0: <tt>"pfsConfig-0x%016x-%06d.fits" % (pfsDesignId, visit0)</tt>, with the intent that only the unique pfsConfigs need to be generated. That does imply book-keeping. At this point, do we want to add the book-keeping on the DRP side, or the shuffling on the ICS side?</p> <p>Discussion on a Hilo porch put the burden on ICS/iic per this ticket, plus removing the "0" from <tt>visit0</tt> from that line in the data model.</p> Relates DAMD-144 INSTRM-1718 Development Rank 0|zzsvmf: Story Points 1.0