[INSTRM-1214] Creating pfsDesign objects from multiple light sources Created: 18/Mar/21  Updated: 15/Jan/22

Status: Open
Project: Instrument control development
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: hassan Assignee: cloomis
Resolution: Unresolved Votes: 0
Labels: SPS, SuNSS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-1303 Have sunssActor enable/disable acquis... Open
relates to PIPE2D-842 support engineering fiber for all lig... Open
relates to INSTRM-1304 Add GUI control and display of SM lig... Done
relates to INSTRM-1306 Fix the way gen2Actor establishes the... Done
relates to INSTRM-1278 Add commands to generate complete pfs... Won't Fix
relates to PIPE2D-5 Track (ra, dec) positions of cobras Won't Fix
relates to INSTRM-1095 Add command(s) to declare where light... Done
relates to INSTRM-1141 Add command(s) to declare where light... Done
Story Points: 2

 Description   

As discussed during the ICS/SpS telecon on 2021-03-17: we will have scenarios where we will have light coming in from multiple, differing sources. For example, we may have SuNSS connected to SM1, while DCB is connected to SM2. How is this conveyed in a pfsDesign object?

This general ticket is filed as an INSTRM ticket simply because most of the work is in the ICS domain.



 Comments   
Comment by rhl [ 19/Mar/21 ]

I don't think that there's any difficulty using pfsDesign for this, except that we'll need at least one more fibre types added to TargetType, probably just DCB.

The slightly trickier thing is how to construct the needed pfsDesign from the set of inputs, and how to make sure that the `pfsDesignId` is unique.

Comment by hassan [ 25/Mar/21 ]

Craig has a working proposal that has been iterated with RHL and is almost ready to be distributed.

Comment by hassan [ 26/Aug/21 ]

This is not an issue for the Sep and Oct engineering runs as only one SM is in place.

Generated at Sat Feb 10 16:33:03 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.