[INSTRM-1422] Publish complete pfsDesign/pfsConfig files before any exposure.

Blocks — Wed, 27 Oct 2021 22:38:23 +0000

At the point when an exposure is taken, it needs to be associated with the correct pfsDesign, along with the correct pfsConfig if possible and appropriate. This set of tickets covers that work.

An overview:

There are currently three sources of light to the SPS: `pfi`, `sunss`, and `dcb`. We can imagine a couple more (`allFiber`, say). For any one of these, the logic for generating their `pfsConfig` is pretty straightforward. Generate these when interesting things change, and aggregate them into single complete `pfsDesign/pfsConfig` files for the entire instrument.

Specifically, we use the `sps.lightsources` key to tell us what is connected to each SM gang connector. Given that, `fps.pfsConfig`, `sunss.pointing`, and `dcb.bundles` tell us all we need to generate the component `pfsDesign/pfsConfigs`.

It is the iicActor's job to "publish" the final `pfsDesign/pfsConfig` files, even when there is a single light source. The `fpsActor` output is not a published version.

Some of this matters for the 2021-11 run. But with only one SM much does not: the existing DCB/SUNSS configs are fine.

PFS-JIRA

[INSTRM-1422] Publish complete pfsDesign/pfsConfig files before any exposure.