[INSTRM-1939] pfsDesignId reported in header does not match the created pfsConfig Created: 24/Apr/23  Updated: 18/Jul/23

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

Type: Bug Priority: Normal
Reporter: arnaud.lefur Assignee: cloomis
Resolution: Unresolved Votes: 0
Labels: EngRun
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-1980 Accept designId argument to ramp command In Progress

 Description   

Looking at this visit : 91057 

2023-04-22 05:05:44.342Z cmds             20 CommandLink.py:121 > 2 8 i pfsConfig=0x662cf9deec5c1ce9,91057,"2023-04-22",100.000000,100.000000,0.000000,"phiCrossing-2022-06-19",0x0000000000000000,0
2023-04-22 05:05:44.343Z cmdr             20 CmdrConnection.py:218 queueing command sps(expose dark exptime=900.0 cams=b1,r1,n1,b3,r3 visit=91057)

(lsst-scipipe-3.0.0) [alefur@pfsa-usr01-gb sps]$ fitsheader PFSA09105711.fits |grep 'PFD'
W_PFDSGN=  1562097688427952981 / pfsDesign, from pfi

I think it's because a another design has been declared before the dark end which is legitimate.
But apparently ccd actor picked up the next design.

 Comments   
Comment by cloomis [ 24/Apr/23 ]

Currently IIC (sometimes via SPS) passes the visit down to all the camera actors for just this reason. We should add pfsDesignId.

Comment by arnaud.lefur [ 27/Apr/23 ]

IIC and SPS updated, i'm now passing down designId argument to ccd.read and hx.ramp

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