[DAMD-105] Include which arms should be used in the pfsDesign/pfsConfig file Created: 19/Dec/20  Updated: 02/Apr/21  Resolved: 26/Feb/21

Status: Done
Project: Data Model
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Normal
Reporter: rhl Assignee: hassan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to PIPE2D-741 Update create_weekly.sh script to han... In Progress
relates to SIM2D-134 Update simulator to use arm informati... Open
Story Points: 2
Sprint: 2DDRP-2021 A 2
Reviewers: price

 Description   

I don't think that we have a way to specify and track which arms are to be/were used to expose a given set of fibres. If I'm right, we should add this information to the pfsDesign (and thus pfsConfig) file. The easiest way would be to add it to the PDU along with the RA and DEC (and ROTANG DAMD-100) as e.g. ARMS = 'brn'
This is sufficient for downstream users to figure out what we did, but as a courtesy we should add this information to the metadata for pfsMerged and pfsObject files too.

 Comments   
Comment by cloomis [ 19/Dec/20 ]

In the pfsDesign/Config? Really? I can see indicating what the intended coverage of a pointing is, but isn't which arms are exposed a property which is chosen long after the design/config has been fixed? Or do you mean instances which are created after the data have been taken?

Comment by rhl [ 19/Dec/20 ]

I think so.  You know if you're designing a GA plate (m) or a regular plate (r) once you know the target list.   So I think that this is a natural place to specify the complete PFS configuration.

Generated at Sat Feb 10 15:34:18 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.