[PIPE2D-1360] fiberId 1984 detectorMap xCenter is largely misplaced Created: 30/Jan/24  Updated: 03/Feb/24

Status: Open
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

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

Attachments: PNG File detMap_103388r4.png     PNG File detMap_104160r4.png     PNG File fiberId2224_2223.png    

 Description   

Looking at some scienceTrace when cobras are all at home,
I noticed that fiberId 1984 which is labelled as broken was apparently getting a lot of flux.
So I look more carefully, and it turn out that the detectorMap is pointing at its neighbouring fiber 1983, fiber centers are separated by 0.4 pixels which of course not physically possible.

To be fair, pfsConfig for that visit was wrong, meaning that fiberStatus was not set to BROKENFIBER, that's the case for almost all the visits taken on december 21, before 103341.
How could this happen ? Because the design was wrong and I set it right when the config is produced except that fps didn't produce a pfsConfig because of another issue.
I will create a ticket to make sure pfsDesign include fiberStatus correctly.

But my question here to price could that fiberStatus mistake lead to this bug ?

 Comments   
Comment by yuki.moritani [ 30/Jan/24 ]

just adding.. as I reported on Slack sometimes ago, x position of fiberId=1984 is defined at the same place as fiberId=1983 for r4.

Comment by arnaud.lefur [ 30/Jan/24 ]

You're right I skipped one line in my logs, it's not 2224 it's 1984, I agree.
So the problem was already reported, was there an associated ticket or shall we keep this one ?

Comment by yuki.moritani [ 30/Jan/24 ]

We can/should keep this ticket. I hesitated to file a ticket at that time, and forgot....

Comment by Kiyoto Yabe [ 03/Feb/24 ]

Regenerated detectorMaps (see PIPE2D-1346) based on 12/28 data (the first image) without doSlitOffset (green cross) show the same mismatch, but it looked to be recovered with doSlitOffsets (red cross). However,  doSlitOffsets didn't help for regenerated detectorMaps based on 12/21 data (the second image)...

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