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

Add commands to generate complete pfsDesign and pfsConfig files and rows

    XMLWordPrintable

    Details

    • Story Points:
      3
    • Sprint:
      SM1PD-2021 A9, SM1PD-2021 A10, SM1PD-2021 A 11, SM1PD-2021 A 12, SM1PD-2021 A 13, EngRun03

      Description

      We need top-level iic commands which generate pfsDesign and pfsConfig files, based on the configuration of the entire instrument (primarily the sps.lightSource keys, the targeting and FPS information, the DCBx and SuNSS configurations, and the pfs_instdata status ). These would be called at the start of each field or exposure.

      It may be that we will want per-SM design/configs, but I think those should be derived from the configuration of the entire instrument. I propose that we always generate files describing all 2604 slit holes and treat those as the single sources for all further HDUs, opdb rows, etc.

      An implementation note: any files should be put into per-night directories /data/raw/$date/pfsConfig/, say, just to keepthe pfsDesign directory from becoming a bottleneck.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cloomis cloomis
                Reporter:
                cloomis cloomis
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: