https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1360 DRP 2-D Pipeline <p>Looking at some scienceTrace when cobras are all at home,<br/> I noticed that fiberId 1984 which is labelled as broken was apparently getting a lot of flux.<br/> 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.</p> <p>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.<br/> 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.<br/> I will create a ticket to make sure pfsDesign include fiberStatus correctly.</p> <p>But my question here to <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=price" class="user-hover" rel="price">price</a> could that fiberStatus mistake lead to this bug ?</p> PIPE2D-1360

fiberId 1984 detectorMap xCenter is largely misplaced

Bug Normal Open Unresolved Unassigned arnaud.lefur EngRun Mon, 29 Jan 2024 23:43:26 +0000 Sat, 3 Feb 2024 02:52:46 +0000 0 3 <p>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.</p> <p>You're right I skipped one line in my logs, it's not <del>2224</del> it's 1984, I agree.<br/> So the problem was already reported, was there an associated ticket or shall we keep this one ?</p> <p>We can/should keep this ticket. I hesitated to file a ticket at that time, and forgot....</p> <p>Regenerated detectorMaps (see <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1346" title="Generate detectorMaps for Dec. 2023 data" class="issue-link" data-issue-key="PIPE2D-1346">PIPE2D-1346</a>) 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)...</p> <p><span class="image-wrap" style=""><a id="17114_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/17114/17114_detMap_103388r4.png" title="detMap_103388r4.png" file-preview-type="image" file-preview-id="17114" file-preview-title="detMap_103388r4.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/17113/_thumb_17113.png" style="border: 0px solid black" /></a></span> <span class="image-wrap" style=""><a id="17114_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/17114/17114_detMap_103388r4.png" title="detMap_103388r4.png" file-preview-type="image" file-preview-id="17114" file-preview-title="detMap_103388r4.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/17114/_thumb_17114.png" style="border: 0px solid black" /></a></span></p> Development Rank 0|zzt13z: