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

            Activity

            Hide
            arnaud.lefur arnaud.lefur added a comment -

            since iicActor scheme is going to change reasonably soon, I think indeed we can defer worrying such cases.

            Show
            arnaud.lefur arnaud.lefur added a comment - since iicActor scheme is going to change reasonably soon, I think indeed we can defer worrying such cases.
            Hide
            hassan hassan added a comment -

            Following discussions between cloomis and arnaud.lefur earlier today: consider this ticket as being already addressed, and in fact superseded by other tickets, such as the work in INSTRM-1095.

            Show
            hassan hassan added a comment - Following discussions between cloomis and arnaud.lefur earlier today: consider this ticket as being already addressed, and in fact superseded by other tickets, such as the work in INSTRM-1095 .

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: