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-1210 DRP 2-D Pipeline <p>Similar to <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1140" title="Reduce data obtained in Nov run for the internal release to the collaboration" class="issue-link" data-issue-key="PIPE2D-1140"><del>PIPE2D-1140</del></a>, reduce the data obtained in 2023 Apr commissioning run. <br/> The list of calibration data taken may be found in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1187" title="Plan for data acquisition April 2023 run" class="issue-link" data-issue-key="PIPE2D-1187"><del>PIPE2D-1187</del></a><br/>  </p> <p>A complete set of visits to be reduced are:</p> <p>run12 (Jul 2023): <a href="https://sumire.pbworks.com/w/page/153934425/Science%20Data%20from%20Run%2012" class="external-link" rel="nofollow">https://sumire.pbworks.com/w/page/153934425/Science%20Data%20from%20Run%2012</a></p> <p>run11 (Apr 2023): <a href="https://sumire.pbworks.com/w/page/153263325/Science%20Data%20from%20Run%2011" class="external-link" rel="nofollow">https://sumire.pbworks.com/w/page/153263325/Science%20Data%20from%20Run%2011</a></p> <p>run08 (Nov 2022): <a href="https://docs.google.com/document/d/1qfZV55DYlx9t7ru6dKntg3CiJj2HF3McBwJ2DZUrCWk/edit" class="external-link" rel="nofollow">https://docs.google.com/document/d/1qfZV55DYlx9t7ru6dKntg3CiJj2HF3McBwJ2DZUrCWk/edit</a></p> <p> </p> PIPE2D-1210

Reduce data obtained in Nov 2022, Apr, July 2023 for the internal data release (EDR2)

Task Normal Done Done Kiyoto Yabe Kiyoto Yabe EDR EngRun Mon, 1 May 2023 08:27:44 +0000 Wed, 31 Jan 2024 20:09:01 +0000 Wed, 31 Jan 2024 20:09:01 +0000 0 4 <p>Just a note that the Twilight Sky dates should be 4/22 (UTC) and visit 91183-91187.</p> <p>Thank you for pointing it out. I corrected visit and date. I'm sorry I was not clear, but the dates are the night of observation. (It should be confusing though..)</p> <p>I'm confused by those names. E.g. visit 91178 is <tt>'0x7efb873c7b26a935', 'fluxcal_test_da_4419865155422033280_pa+00_sm1 V001'</tt> but this list calls it "da_4419865155422033280". Maybe we could standardise on the <tt>pfsDesignId</tt> (with or without the <tt>designName</tt>)?</p> <p>I'm sorry for confusion. I agree to add pfsDesignId on the list, I was lazy to put them, hoping someone would like to put one later as long as visit is listed.. (If I do next time, I'll be more careful.) design.Name was sometimes too long and a little confusing as the same name was used for different design, so designId should be listed, I feel.</p> <p>The processing is done for the release as `edr2-20231203`, so I close this ticket.</p> Relates PIPE2D-1241 PIPE2D-1140 Development Rank 0|02qph7:06r0903hr Sprint EDR+AIT Story Points 3.0