[INSTRM-1094] Populate pfs_visit.pfs_design_id column Created: 29/Oct/20 Updated: 15/Jan/22 Resolved: 05/Dec/20 |
|
| Status: | Won't Fix |
| Project: | Instrument control development |
| Component/s: | ics_iicActor |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | cloomis |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | Gen2, SPS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| 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. ] |
| Comments |
| Comment by arnaud.lefur [ 11/Nov/20 ] |
|
since iicActor scheme is going to change reasonably soon, I think indeed we can defer worrying such cases. |
| Comment by hassan [ 05/Dec/20 ] |
|
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 |