[INSTRM-2271] Make pfsConfig ARMS match actual physical configuration. Check vs. pfsDesign request Created: 09/May/24 Updated: 14/May/24 Resolved: 14/May/24 |
|
Status: | Done |
Project: | Instrument control development |
Component/s: | ics_iicActor |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Task | Priority: | Normal |
Reporter: | cloomis | Assignee: | arnaud.lefur |
Resolution: | Done | Votes: | 0 |
Labels: | EngRun | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Story Points: | 1 |
Sprint: | EngRun16May |
Description |
All of the following visits (and several others) were configured with the med res. grating in, and had m-arm FITS files. But some of the pfsConfig files showed r in the ARMS card. For iic/sps, the issues are:
We think the pfsConfig files should always match the physical configuration. If the grating position and the pfsDesign conflict, either the exposure should be rejected, or the grating moved to match the pfsDesign, or some forceGrating argument should be required. pfsConfig name ARMS DSGN_NAM ------------------------- ---- ------------------------------------------ 0x70b4acc77695a624-110023.fits brn cobraHome-MOD4_group2 0x70b4acc77695a624-110024.fits brn cobraHome-MOD4_group2 0x06790bc0ce68e0d3-110264.fits brn cobraHome 0x662cf9deec5c1ce9-110266.fits br phiCrossing-2022-06-19 0x662cf9deec5c1ce9-110267.fits br phiCrossing-2022-06-19 [ ... ] 0x0045d686a297b83b-110439.fits bmn PPC_M_96207814 0x2b06fae346c34863-110464.fits br calspec_3944_sm3_pa+00_run16_fluxstd_v3.3 0x2cf7af63a300c1e6-110489.fits bmn PPC_M_20511660 0x35160c54f442dcb0-110504.fits br allfluxstd_field2_pa+00_run16_fluxstd_v3.3 0x35160c54f442dcb0-110522.fits br allfluxstd_field2_pa+00_run16_fluxstd_v3.3 0x35160c54f442dcb0-110523.fits br allfluxstd_field2_pa+00_run16_fluxstd_v3.3 0x356b50cd140b34e5-110491.fits bmn PPC_M_35334630 0x6d832ca291636984-110480.fits bmn ga1_pa+90_run16_fluxstd_v3.3 0x6d832ca291636984-110481.fits bmn ga1_pa+90_run16_fluxstd_v3.3 0x7a726bf04d6bedfa-110441.fits bmn PPC_M_33407196 0x51773baa1a359f2e-110541.fits br thetaCrossing-2022-06-19 0x51773baa1a359f2e-110543.fits br thetaCrossing-2022-06-19 |
Comments |
Comment by Masayuki Tanaka [ 09/May/24 ] |
I have checked the visits in EDR2. I only looked at visits with pfsMerged, but it looks like a lot of files after the Nov 2022 run need to be corrected (n is missing). 2 pfsConfig.arms 3 arms in pfsMerged 4 ignore ----------------------------------------------------------- 82595 br br [1197, 1196, 1, 0] |
Comment by arnaud.lefur [ 09/May/24 ] |
For the calib(cobraHome, mod4_groupN, does it means the design should have all the arms brnm ? and then the pfsConfig set the current red resolution ? |
Comment by arnaud.lefur [ 14/May/24 ] |
merged as iicActor:2.5.15 . iic will now reject exposure if the arm is not included in the declared pfsDesign |