[INSTRM-1427] Publish pfsConfig files when the PFI is light source Created: 02/Nov/21 Updated: 14/Oct/22 Resolved: 14/Oct/22 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | hassan | Assignee: | arnaud.lefur |
| Resolution: | Done | Votes: | 0 |
| Labels: | EngRun | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Story Points: | 1 | ||||||||||||
| Sprint: | PreEngRun4 | ||||||||||||
| Description |
|
For the upcoming November Engineering Run, please implement the last, most important task described in the above ticket, and only for pfsConfig files as standalone pfsDesign files are not needed for DRP. Namely: When the `pfi` is the only light source, simply copy/link the pfsConfig from the fpsActor output. |
| Comments |
| Comment by cloomis [ 14/Nov/21 ] |
|
We have agreed that the fpsActor will write the pfsConfig outputs directly into /data/raw/pfsConfig// : that step is what defines "publishing" a pfsConfig. So no copy/link, just a change to the fpsActor. In the case where we have multiple light sources, IIC will possible generate other pfsConfig files. That is covered by |
| Comment by arnaud.lefur [ 14/Oct/22 ] |
|
covered by |