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/PIPE1D-14 DRP 1D pipeline <p>For the first step of the end-to-end processing test, run 1D-DRP for the resulting products from 2D-DRP, and compare the results to the input spectra of the existing simulated 2D image processed by 2D-DRP.</p> PIPE1D-14

Run 1D-DRP for the resulting products from 2D in the end-to-end processing test

Task Normal Done Done Kiyoto Yabe Kiyoto Yabe DRP_end-to-end_processing Fri, 19 Jun 2020 00:27:57 +0000 Thu, 22 Oct 2020 04:41:04 +0000 Thu, 22 Oct 2020 04:41:04 +0000 0 5 <p>Confirmed that the test script to run the example datapack included in the pipeline can be processed.</p> <p>This is an example result for objId=55. 1D spectrum shows <span class="error">&#91;OII&#93;</span>, Hb, <span class="error">&#91;OIII&#93;</span> at z=0.853 clearly, but DRP1D returns the best-fit z of 0.08. Needs to further investigation...</p> <p><span class="image-wrap" style=""><img src="https://pfspipe.ipmu.jp/jira/secure/attachment/12828/12828_example_0x37.png" style="border: 0px solid black" /></span></p> <p>Hi Kiyoto,</p> <p>Sorry to introduce inside your ticket. If you want any help on this spectrum, we'll be glad to contribuate.</p> <p>I confirmed that it returns a good redshift result if we limit the redshift range very narrowly, like  </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-json"> <span class="code-quote">"redshiftrange"</span>: [ <span class="code-quote">"0.8"</span>, <span class="code-quote">"0.9"</span> ], </pre> </div></div> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=pychabau" class="user-hover" rel="pychabau">Pierre-Yves CHABAUD</a> Could you run drp1d for the spectrum below in your side? I also appreciate if you tell me a good parameter configuration?</p> <p><span class="nobr"><a href="https://pfspipe.ipmu.jp/jira/secure/attachment/12900/12900_pfsObject-001-00000-0%2C0-0000000000000037-002-0xe0241444a9af118c.fits" title="pfsObject-001-00000-0,0-0000000000000037-002-0xe0241444a9af118c.fits attached to PIPE1D-14">pfsObject-001-00000-0,0-0000000000000037-002-0xe0241444a9af118c.fits^{<img class="rendericon" src="https://pfspipe.ipmu.jp/jira/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p>I observe a non physical high pick value at pixel 346. By reducing lambda range to</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> <span class="code-quote">"lambdarange"</span>:[<span class="code-quote">"3800"</span>,<span class="code-quote">"13000"</span>] </pre> </div></div> <p>the pick is ignored and the right redshift appears in the candidates list. However, the right redshift remains in lower probability position. We are still investigating on this case.</p> <p>Dear Kyoto,</p> <p>I think I have identified the problem : there is a strong noise peak at 6330 A which is not identified in the variance. This ear is thus used as Ly-alpha, CIII and OII as first solution since it is very strong and has thus more weight than the true emission lines. </p> <p><span class="image-wrap" style=""><img src="https://pfspipe.ipmu.jp/jira/secure/attachment/12904/12904_unidentified_noise_spike.png" style="border: 0px solid black" /></span></p> <p>Thank you for letting me know your results <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=vlebrun" class="user-hover" rel="vlebrun">vlebrun</a> &amp; <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=pychabau" class="user-hover" rel="pychabau">Pierre-Yves CHABAUD</a> (I should have replied earlier). So, in this case, the best redshift is ~4, right? I could not reproduce the same result in my environment. Could you send me your configuration file in json format?</p> <p>Hi <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kiyoto.yabe" class="user-hover" rel="kiyoto.yabe">Kiyoto Yabe</a> , by looking at this issue, we've just found a bug in the pipeline on parameters file overloading ( <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE1D-22" class="external-link" rel="nofollow">https://pfspipe.ipmu.jp/jira/browse/PIPE1D-22</a> ). I propose to wait for fixing it, before going further. Sorry for the delay.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=pychabau" class="user-hover" rel="pychabau">Pierre-Yves CHABAUD</a>  OK, thank you for letting me know <img class="emoticon" src="https://pfspipe.ipmu.jp/jira/images/icons/emoticons/thumbs_up.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>I'm investigating the feature at around 633 nm, which was reproduced with the latest 2D pipeline (`w.2020.39`). As shown in the plots below, this seems to come out after making `pfsMerged` spectrum in only `visit=24`. The plots are for only 2 objects (objId=0x37 and 0x12), but I see the same feature for other fibers. <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=price" class="user-hover" rel="price">price</a> do you have any idea?</p> <p><span class="image-wrap" style=""><a id="13100_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/13100/13100_pfsArm_pfsMerged_v000024_objId0x12.png" title="pfsArm_pfsMerged_v000024_objId0x12.png" file-preview-type="image" file-preview-id="13100" file-preview-title="pfsArm_pfsMerged_v000024_objId0x12.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/13101/_thumb_13101.png" style="border: 0px solid black" /></a></span><span class="image-wrap" style=""><a id="13103_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/13103/13103_pfsArm_pfsMerged_v000025_objId0x37.png" title="pfsArm_pfsMerged_v000025_objId0x37.png" file-preview-type="image" file-preview-id="13103" file-preview-title="pfsArm_pfsMerged_v000025_objId0x37.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/13100/_thumb_13100.png" style="border: 0px solid black" /></a></span><span class="image-wrap" style=""><a id="13102_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/13102/13102_pfsArm_pfsMerged_v000025_objId0x12.png" title="pfsArm_pfsMerged_v000025_objId0x12.png" file-preview-type="image" file-preview-id="13102" file-preview-title="pfsArm_pfsMerged_v000025_objId0x12.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/13103/_thumb_13103.png" style="border: 0px solid black" /></a></span><span class="image-wrap" style=""><a id="13117_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/13117/13117_example_0x37_20201012.png" title="example_0x37_20201012.png" file-preview-type="image" file-preview-id="13117" file-preview-title="example_0x37_20201012.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/13102/_thumb_13102.png" style="border: 0px solid black" /></a></span></p> <p>I am investigating (<a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-633" title="Debug false lines in extracted spectra" class="issue-link" data-issue-key="PIPE2D-633"><del>PIPE2D-633</del></a>; the number of the ticket is completely coincidental!).</p> <p>This is the same object as before but with a fix of <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-635" class="external-link" rel="nofollow">PIPE2D-635</a></p> <p>The 1D output looks reasonable.</p> <p><span class="image-wrap" style=""><a id="13117_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/13117/13117_example_0x37_20201012.png" title="example_0x37_20201012.png" file-preview-type="image" file-preview-id="13117" file-preview-title="example_0x37_20201012.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/13117/_thumb_13117.png" style="border: 0px solid black" /></a></span></p> <p>good to see we are able to measure the redshift on such strong emission lines...</p> <p>I just confirmed that the processing is successfully done with the master branch after <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-635" title="Improve FitFocalPlaneTask" class="issue-link" data-issue-key="PIPE2D-635"><del>PIPE2D-635</del></a> is merged. So, I will close this ticket.</p> Blocks PIPE2D-608 PIPE2D-606 INFRA-278 PIPE1D-20 Relates PIPE2D-633 PIPE2D-635 Development Rank 0|zzs1zs: