[INSTRM-1802] write actual pfsConfig for each sps exposure. Created: 23/Nov/22 Updated: 14/Dec/22 Resolved: 14/Dec/22 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | ics_iicActor |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | arnaud.lefur | 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 | ||||||||||||
| Description |
|
fps write pfsConfig for each convergence, but since sps can take multiple visits with the same designId, that's not enough. IIC needs to be make sure that associated pfsConfig is created whenever sps takes an exposure. |
| Comments |
| Comment by cloomis [ 23/Nov/22 ] |
|
The original pfsConfig design uses visit0: "pfsConfig-0x%016x-%06d.fits" % (pfsDesignId, visit0), 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? |
| Comment by cloomis [ 23/Nov/22 ] |
|
Discussion on a Hilo porch put the burden on ICS/iic per this ticket, plus removing the "0" from visit0 from that line in the data model. |