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-1420 Instrument control development <p>Before running any sps/fps/agcc/mcs command which might take an exposure, make sure the current config has been constructed and published. </p> <p>Iterate over `sps.lightSources`, and gather the appropriate `fps.pfsConfig`, `sunss.pointing` and `dcb.bundles` values. When any of those values change, trigger the generation of a new, possibly aggregated, `pfsDesign/pfsConfig`.<br/>  <br/> Put published FITS files in `/data/raw/$date/{pfsDesign,pfsConfig}/` &#8211; these will be copied with the raw data. We want one `pfsConfig` file for each `visit0`, not one per visit.<br/>  <br/> To highlight the most important configuration: when the `pfi` is the only light source, simply copy/link the `pfDesign` file from the targeting/planning software and the `pfsConfig` from the `fpsActor` output.<br/>  </p> INSTRM-1420

Publish final `pfsConfig` and `pfsDesign` FITS files, before taking sps/fps/mcs/agcc exposures.

Task Normal Done Done cloomis cloomis CanBeClosed Fri, 22 Oct 2021 21:14:30 +0000 Wed, 1 Feb 2023 22:41:24 +0000 Wed, 1 Feb 2023 22:41:23 +0000 ics_iicActor 0 2 <p>I don't have clear ideas about what "final" means, and what "publish" means ...<br/> Depending on the intents of tests/observations represented by pfsDesign (and Config) files, the judgement of them being "final" and "publish-iable" may change I presume, so I suspect mechanism(s) with some human intervention are supposed to be discussed here? I am sorry very likely I am just ignorant and behind, but I appreciate a bit more elaboration about intents.</p> <p>This would be the place for the pfsDesign and pfsConfig files which actually get used and observed: the ones which are associated with some PFSx file. This is a subset of the pfsDesign files which are available to observe.</p> <p>To be more concrete, when <tt>iic observePfsDesign designId=xxx</tt> and thus <tt>fps moveToPfsDesign designId=xxx</tt> get called, one design file from the location/directory which is populated by shuffle (see <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1416" title="Define file tree location for the `pfsDesign` files from the planning software" class="issue-link" data-issue-key="INSTRM-1416"><del>INSTRM-1416</del></a>) is read and instantiated by the fpsActor. It is also "published" by iic by being copied to, as proposed, <tt>/data/raw/$date/pfsDesign/</tt>.</p> <p>We now have pfsConfig created before each sps exposure which I think mostly what this ticket was aiming for.<br/> The pfsConfig merging is implemented for dcb + SuNSS, but not for pfi+dcb|SuNSS .<br/> Let's close this one at least, and open new tickets if necessary.</p> Blocks INSTRM-1422 Relates INSTRM-1427 Development Rank 0|02qpjd:00r3000ka