-
Type: Bug
-
Status: Done (View Workflow)
-
Priority: Normal
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
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 ?