Instrument control developmentIcon indicating the project type

Instrument control development

Uploaded image for project: 'Instrument control development'
  1. Instrument control development
  2. INSTRM-1427

Publish pfsConfig files when the PFI is light source

    Details

    • Type: Task
    • Status: Done (View Workflow)
    • Priority: Normal
    • Resolution: Done
    • Component/s: None
    • Labels:
    • Story Points:
      1
    • Sprint:
      PreEngRun4

      Description

      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.

        Attachments

          Issue Links

          relates to

          Task - A task that needs to be done. INSTRM-1348 Ingest pfsDesign/pfsConfig files to opDB

          • Normal - Normal priorities
          • Done

          Task - A task that needs to be done. INSTRM-1420 Publish final `pfsConfig` and `pfsDesign` FITS files, before taking sps/fps/mcs/agcc exposures.

          • Normal - Normal priorities
          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            cloomis cloomis added a comment -

            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.

            Show
            cloomis cloomis added a comment - 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 .
            Hide
            Permalink
            arnaud.lefur arnaud.lefur added a comment -

            covered by INSTRM-1691

            Show
            arnaud.lefur arnaud.lefur added a comment - covered by INSTRM-1691

              People

              • Assignee:
                arnaud.lefur arnaud.lefur
                Reporter:
                hassan hassan
              • Votes:
                0 Vote for this issue
                Watchers:
                Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: