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

Populate pfs_visit.pfs_design_id column

    XMLWordPrintable

    Details

      Description

      The gen2Actor currently adds rows to the pfs_visit table: it is the program which consumes the visit from Gen2 and distributes it to PFS, so is the "closest" one to the source of the data.

      We now want to add a pfs_design_id column. I think we should keep the inserts in the gen2Actor, but will need an keyword giving the value. That needs to come from EEK.

      [ Can we defer worrying about the possibility of having multiple active light sources: DCB to SM4 being commissioned, SuNSS to another, PFI for the other two? If that has any chance of happening, this is the wrong design. ]

        Attachments

          Issue Links

          is blocked by

          Task - A task that needs to be done. INSTRM-1095 Add command(s) to declare where light is coming from; generate pfsDesign keyword

          • Normal - Normal priorities
          • Done
          relates to

          Task - A task that needs to be done. INSTRM-1096 Add {{pfs_visit.pfs_design_id}} column

          • Normal - Normal priorities
          • Done

          Task - A task that needs to be done. INSTRM-1101 Populate pfs_visit.pfs_design_id column for LAM opdb

          • Normal - Normal priorities
          • Done

          Task - A task that needs to be done. INSTRM-1102 Temporarily feed pfs_visit.pfs_design_id from the DCB design keyword.

          • Normal - Normal priorities
          • Done

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: