-
Type:
Task
-
Status: Done (View Workflow)
-
Priority:
Normal
-
Resolution: Done
-
Component/s: None
-
Labels:
-
Story Points:1
-
Sprint:PreEngRun4
INSTRM-1420 lists 3 tasks that needs to be done in terms of publishing pfsDesign and pfsConfig files for different light sources.
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.
- relates to
-
-
- Done
-
-
-
- Done
-
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue relates to |
| Rank | Ranked higher |
| Summary | Publish pfsDesign/pfsConfig files when the PFI is light source | Publish pfsConfig files when the PFI is light source |
| Description |
For the upcoming November Engineering Run, please implement the last, most important task described in the above ticket, namely: When the `pfi` is the only light source, simply copy/link the {{pfsDesign}} file from the targeting/planning software and the {{pfsConfig}} from the `fpsActor` output. |
For the upcoming November Engineering Run, please implement the last, most important task described in the above ticket, namely: When the `pfi` is the only light source, simply copy/link the {{pfsConfig}} from the `fpsActor` output. |
| Description |
For the upcoming November Engineering Run, please implement the last, most important task described in the above ticket, namely: When the `pfi` is the only light source, simply copy/link the {{pfsConfig}} from the `fpsActor` output. |
For the upcoming November Engineering Run, please implement the last, most important task described in the above ticket, and only for {{pfsConfig}} files as {{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. |
| 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 {{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. |
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. |
| Link |
This issue relates to |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Sprint | PreEngRun4 [ 123 ] | PreEngRun4, preEngRun07Sep [ 123, 152 ] |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Sprint | PreEngRun4, preEngRun07Sep [ 123, 152 ] | PreEngRun4 [ 123 ] |
| Rank | Ranked higher |
covered by INSTRM-1691
| Status | Open [ 1 ] | Done [ 10002 ] |
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
INSTRM-1420.