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-322 DRP 2-D Pipeline <p>Using the results from <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-380" title="Write fitted wavelength position and error to file" class="issue-link" data-issue-key="PIPE2D-380"><del>PIPE2D-380</del></a>, provide functions that analyze the accuracy of the wavelength solution determined by the 2D DRP pipeline.</p> <p>Checks include (but not exhaustive):</p> <ol> <li>For a given exposure, estimate the RMS error in wavelength for each fibers. This can be compared with that determined from the pipeline.</li> <li>As above, but provide an overall estimate across all fibers.</li> <li>Examine the error evolution across a number of exposures for any time-dependent trend.</li> </ol> <p>In addition to the RMS error, other statistics should be considered and if appropriate provided. Plots in addition to textual output should be provided - anything that can assist the team to determine any problems with the wavelength solution.</p> PIPE2D-322

Write a function and task to determine wavelength accuracy

Task Normal Won't Fix Won't Fix Kiyoto Yabe hassan Wed, 30 Jan 2019 21:26:45 +0000 Fri, 31 Mar 2023 09:08:41 +0000 Fri, 31 Mar 2023 09:08:41 +0000 5.0 6.0 0 4 <p>The pipelines calculate these numbers (so the code exists), we need to extract this information; it keeps back some number of lines for the purpose.  We also need to compare one arc exposure with others.</p> <p> </p> <p>The very initial results:</p> <p><span class="image-wrap" style=""><a id="12427_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12427/12427_arc_ne_17297_wl_calib_rms.png" title="arc_ne_17297_wl_calib_rms.png" file-preview-type="image" file-preview-id="12427" file-preview-title="arc_ne_17297_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12314/_thumb_12314.png" style="border: 0px solid black" /></a></span></p> <p>The residual of the wavelength calibration (`fitWavelength` - `refWavelength`) as a function of `refWavelength` based on the output of in wlFitData of a Ne arc (visit=17244). I assumed that `status`=1 means good results here. The color in the plot indicates `fiberId`.</p> <p><span class="image-wrap" style=""><a id="12510_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12510/12510_arc_hgar_visit_wl_calib_rms.png" title="arc_hgar_visit_wl_calib_rms.png" file-preview-type="image" file-preview-id="12510" file-preview-title="arc_hgar_visit_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12427/_thumb_12427.png" style="border: 0px solid black" /></a></span></p> <p>The RMS error in wavelength for each fiber as a function of `fiberId`. The measured RMS errors are basically consistent with the output displayed during the pipeline processing.</p> <p>I will think about what other statistics we need later.</p> <p>Here are plots of the RMS errors as a function of visit for May2019 data (left=HgAr and right=Ne):</p> <p><span class="image-wrap" style=""><a id="12509_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12509/12509_arc_ne_visit_wl_calib_rms.png" title="arc_ne_visit_wl_calib_rms.png" file-preview-type="image" file-preview-id="12509" file-preview-title="arc_ne_visit_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12510/_thumb_12510.png" style="border: 0px solid black" /></a></span><span class="image-wrap" style=""><a id="12511_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12511/12511_arc_hgar_17197_wl_calib_residual.png" title="arc_hgar_17197_wl_calib_residual.png" file-preview-type="image" file-preview-id="12511" file-preview-title="arc_hgar_17197_wl_calib_residual.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12509/_thumb_12509.png" style="border: 0px solid black" /></a></span></p> <p>Visits with small RMS error (left) and large RMS error (right) for HgAr data:</p> <p><span class="image-wrap" style=""><a id="12512_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12512/12512_arc_hgar_17209_wl_calib_residual.png" title="arc_hgar_17209_wl_calib_residual.png" file-preview-type="image" file-preview-id="12512" file-preview-title="arc_hgar_17209_wl_calib_residual.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12511/_thumb_12511.png" style="border: 0px solid black" /></a></span> <span class="image-wrap" style=""><a id="12523_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12523/12523_arc_hgar_fiberId_wl_calib_rms.png" title="arc_hgar_fiberId_wl_calib_rms.png" file-preview-type="image" file-preview-id="12523" file-preview-title="arc_hgar_fiberId_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12512/_thumb_12512.png" style="border: 0px solid black" /></a></span></p> <p>Below are the RMS errors in each fiberId for all visits (left=HgAr and right=Ne):</p> <p><span class="image-wrap" style=""><a id="12524_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12524/12524_arc_ne_fiberId_wl_calib_rms.png" title="arc_ne_fiberId_wl_calib_rms.png" file-preview-type="image" file-preview-id="12524" file-preview-title="arc_ne_fiberId_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12523/_thumb_12523.png" style="border: 0px solid black" /></a></span> <span class="image-wrap" style=""><a id="12519_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12519/12519_arc_jul2019calibs_hgar_visit_wl_calib_rms.png" title="arc_jul2019calibs_hgar_visit_wl_calib_rms.png" file-preview-type="image" file-preview-id="12519" file-preview-title="arc_jul2019calibs_hgar_visit_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12524/_thumb_12524.png" style="border: 0px solid black" /></a></span></p> <p>Note: the solid line is the average of the RMS errors in each fiberId.</p> <p> </p> <p>Here are plots of RMS error as a function of visit for July2019 data (left=HgAr and right=Ne):</p> <p><span class="image-wrap" style=""><a id="12521_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12521/12521_arc_jul2019calibs_ne_visit_wl_calib_rms.png" title="arc_jul2019calibs_ne_visit_wl_calib_rms.png" file-preview-type="image" file-preview-id="12521" file-preview-title="arc_jul2019calibs_ne_visit_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12519/_thumb_12519.png" style="border: 0px solid black" /></a></span><span class="image-wrap" style=""><a id="12520_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12520/12520_arc_jul2019calibs_ne_fiberId_wl_calib_rms.png" title="arc_jul2019calibs_ne_fiberId_wl_calib_rms.png" file-preview-type="image" file-preview-id="12520" file-preview-title="arc_jul2019calibs_ne_fiberId_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12521/_thumb_12521.png" style="border: 0px solid black" /></a></span></p> <p>Below are the RMS errors in each fiberId for all visits (left=HgAr and right=Ne):</p> <p><span class="image-wrap" style=""><a id="12520_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12520/12520_arc_jul2019calibs_ne_fiberId_wl_calib_rms.png" title="arc_jul2019calibs_ne_fiberId_wl_calib_rms.png" file-preview-type="image" file-preview-id="12520" file-preview-title="arc_jul2019calibs_ne_fiberId_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12522/_thumb_12522.png" style="border: 0px solid black" /></a></span><span class="image-wrap" style=""><a id="12520_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/12520/12520_arc_jul2019calibs_ne_fiberId_wl_calib_rms.png" title="arc_jul2019calibs_ne_fiberId_wl_calib_rms.png" file-preview-type="image" file-preview-id="12520" file-preview-title="arc_jul2019calibs_ne_fiberId_wl_calib_rms.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/12520/_thumb_12520.png" style="border: 0px solid black" /></a></span></p> <p> </p> <p>I think this will be covered by detectorMap QA (<a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1172" class="external-link" rel="nofollow">PIPE2D-1172</a>), so we close this ticket.</p> Blocks PIPE2D-380 Development Epic Link PIPE2D-15 Rank 0|02qpt6:508yl0chzzy0000qr Sprint 2DDRP-2019 G 2DDRP-2019 H Story Points 4.0