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-794 DRP 2-D Pipeline <p>As discussed during the internal Princeton Group telecon 2021-03-22, please go through the recent stability data acquired at Subaru this year, identifying those visits which are 'good' and those which are problematic, due to hardware configuration changes, significant SCR temperature variations, etc. This requires sifting through the relevant logs etc.</p> <p>The 'good' visits will be passed on to the automatic pipeline for subsequent processing and analysis.</p> PIPE2D-794

Review recent stability data

Task Normal Open Unresolved arnaud.lefur hassan Thu, 25 Mar 2021 13:36:34 +0000 Thu, 13 Jan 2022 14:37:01 +0000 0 4 <p>I think we need a bit more than that.  I'd like to label a subset of the data as calibration data and a subset as science data (and this may mean a new way to do the book-keeping).  Then generate calibrations using the calibs (and Mineo-kun's scripts), and look at the results and sort out what's going on.</p> <p>For example, using the calibs in <tt>/scratch/pprice/pipe2d-706/CALIB</tt> I see fiberId 464 as consistently offset; why?</p> <p>Ultimately, we want a set of calibrations produced using the automated tools that are as good as we can produce.</p> <p>The labelling of the 'good' stability data into calibration data and science data is the subject of <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-791" title="Stability tests: separate visits into calibration and &#39;science&#39;" class="issue-link" data-issue-key="PIPE2D-791">PIPE2D-791</a> (linked). I'm fine to close that ticket and combine both tasks into this single ticket if in practice they cannot be separated easily, and there's less confusion.</p> <p>Good point, Hassan.  I think we may want to merge the two tickets as exactly how to do <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-791" title="Stability tests: separate visits into calibration and &#39;science&#39;" class="issue-link" data-issue-key="PIPE2D-791">PIPE2D-791</a> will become clearer as part of this work, but let's leave them as-is for now.</p> Blocks PIPE2D-711 PIPE2D-791 Relates PIPE2D-727 Development Rank 0|02qpq3:r3y7 Sprint 2DDRP-2021 A3 2DDRP-2021 A 4 2DDRP-2021 A5 2DDRP-2021 A 6 2DDRP-2021 A 7 2DDRP-2021 A 8 2DDRP-2021 A 10 Story Points 3.0