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-1266 DRP 2-D Pipeline <p>The extraction for fiberId 85 in 97127 r1 seems to have problems. It's a single brightish object, and seems to have extracted badly and messed up 84/86 too. b doesn't look great either. <span class="image-wrap" style=""><a id="16182_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/16182/16182_Figure+15+%283%29.png" title="Figure 15 (3).png" file-preview-type="image" file-preview-id="16182" file-preview-title="Figure 15 (3).png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/16164/_thumb_16164.png" style="border: 0px solid black" /></a></span> </p> PIPE2D-1266

Extraction of brightish object fails, and takes down neighbours

Story Normal Done Done price rhl engRun12 Fri, 21 Jul 2023 12:36:37 +0000 Tue, 1 Aug 2023 01:39:07 +0000 Tue, 1 Aug 2023 01:39:07 +0000 0 3 <p>Also seen in 97546 with the <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1271" title="Some r-band detectorMaps are bad with PIPE2D-1267" class="issue-link" data-issue-key="PIPE2D-1271"><del>PIPE2D-1271</del></a> fixes in. <span class="image-wrap" style=""><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/16182/_thumb_16182.png" style="border: 0px solid black" /></span> </p> <p><tt>fiberId=84,85,86</tt> are known to have bad profiles. I believe those cobras are broken so that they cannot be hidden, which means we cannot measure accurate profiles for them. One thing we could do is replace the profile of bad fibers with the average profile.</p> <p><span class="image-wrap" style=""><img src="https://pfspipe.ipmu.jp/jira/secure/attachment/16183/16183_pipe2d-1266.png" width="800" style="border: 0px solid black" /></span></p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=arnaud.lefur" class="user-hover" rel="arnaud.lefur">arnaud.lefur</a>, could we please have these fibers (and others like them) flagged suitably in the pfsConfig? Do we need an extra <tt>FiberStatus</tt> setting?</p> <p>We can surely do better than that? We know that the fibres are broken, so surely we can do no-worse than non-EO traces.</p> <p>The "non-even/odd traces" have the profiles measured completely independently, and so are subject to contamination by nearby fibers. Because of this, we usually limit it to +/- 2 pixels, compared to the +/- 10 pixels for the simultaneous measurement. I think the above profiles look fairly consistent within the +/- 2 pixels limit, but the model can't tell the difference between the three neighboring fibers that can't be hidden, so you see the other bad fibers as well. So how do you want to fix this? Here are some options:<br/> 1. Replace the bad fibers with the average of good nearby fibers. I've implemented this already, and the result (below) looks reasonable. I suggest this could be a suitable interim solution.<br/> 2. Replace the bad fibers with the non-simultaneous profile measurement, limited to +/- 2 pixels.<br/> 3. Attempt to do something more sophisticated in the simultaneous measurement, like measuring all the profiles relative to the average profile. I like this as a long-term solution.<br/> 4. Treat the bad fibers differently in the simultaneous fit, maybe replacing them with the average of good nearby fibers. The difference between this and (1) above is that this replacement is done during the fit rather than after the fact.</p> <p>Replacing bad fibers with the average of good nearby fibers:<br/> <span class="image-wrap" style=""><img src="https://pfspipe.ipmu.jp/jira/secure/attachment/16186/16186_pipe2d-1266-replace.png" width="700" style="border: 0px solid black" /></span></p> <p>I think I like the first solution too.</p> <p>One sounds OK for now. I'd have to think if we can do anything better, but there's probably no need as these will always be mostly-sky fibres. We do need to be able to know when broken cobras fall on bright objects &#8211; something that e.g. <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=msyktnk" class="user-hover" rel="msyktnk">Masayuki Tanaka</a> might want to think about.</p> <p>However, I'm still not happy with the explanation of the original problem. The extractions should mix the spectra from the three bad fibres, but they shouldn't go negative. The problem is apparently that we don't force the fibre profiles to be non-negative; we absolutely need to do this. It may not play well with the scattered light that we're seeing, but we need to fix that too.</p> <p>Filed <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1273" title="Introduce non-negativity constraint in fiber profile measurement" class="issue-link" data-issue-key="PIPE2D-1273">PIPE2D-1273</a> ("Introduce non-negativity constraint in fiber profile measurement") to tackle once we get the background under control.</p> <p>How do we want to get this into the Official Calibs? It's not all that critical now you've diagnosed the problem. I've filed <a href="https://pfspipe.ipmu.jp/jira/browse/DAMD-151" title="Please add information about broken cobras to pfsDesign files" class="issue-link" data-issue-key="DAMD-151">DAMD-151</a> to address the book-keeping problems.</p> <p>I've already copied the updated profiles into <tt>CALIB-2023-07-v3</tt>.</p> <p>Merged changes to master.</p> Development Rank 0|zzsywn: