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/OBSPROC-33 PFS observation processing/procedure <ul> <li>What we noticed during the 2022Nov run and will be fixed for the next run <ul> <li>general</li> <li>script <ul> <li>Also, maybe we should fit the `EUPS` mechanism so that we can switch to different versions, but need to check if this is possible.</li> <li>brokenFiber and brokenCobra should be separated in fiberStatus (see <a href="https://pfspipe.ipmu.jp/jira/browse/DAMD-143" title="add brokenCobra to fiberStatus" class="issue-link" data-issue-key="DAMD-143"><del>DAMD-143</del></a>)</li> </ul> </li> <li>fiber allocation <ul> <li>Do we need to control the calibrators (sky and fluxstds) not to be closed to bright fibers? </li> </ul> </li> <li>targetDB <ul> <li>targets <ul> <li>`target` table has columns for epoch and proper motion but pfsDesign datamodel not (see <a href="https://pfspipe.ipmu.jp/jira/browse/DAMD-137" title="Support proper motion and parallax for targets in pfsDesign files" class="issue-link" data-issue-key="DAMD-137"><del>DAMD-137</del></a>).</li> <li>filterNames should follow the rule of fluxCalibration: <ul> <li>HSC: {g,r_old,r2,i_old,i2,z,y}_hsc</li> <li>PS1: {g,r,i,z,y}_ps1</li> <li>Gaia: {bp,rp,g}_gaia</li> <li>SDSS: {u,g,r,i,z}_sdss</li> </ul> </li> </ul> </li> <li>sky objects  <ul> <li>`cat_id` is not propagated to pfsDesign (see <a href="https://pfspipe.ipmu.jp/jira/browse/OBSPROC-34" title="`cat_id` of sky targets is not propagated properly to pfsDesign" class="issue-link" data-issue-key="OBSPROC-34"><del>OBSPROC-34</del></a>) --&gt; <font color="#FF0000">done</font></li> <li>We couldn't utilized the file of mapping between tract information and target coordinates</li> <li>We should think about more on how to make sky targets in a field with diffuse feature and very high target density (such as M31).</li> </ul> </li> </ul> </li> <li>gaiaDB</li> </ul> </li> </ul> OBSPROC-33

Review the pfsDesign generation script in 2022Nov run and plan for 2022Dec run

Task Normal Done Done Unassigned Kiyoto Yabe Tue, 29 Nov 2022 18:34:44 +0000 Mon, 26 Dec 2022 05:02:35 +0000 Mon, 26 Dec 2022 05:02:35 +0000 0 1 <p>Changes made during Dec. run have been merged, so I close this ticket and file another one for the next run.</p> Relates PIPE2D-1110 Development Rank 0|zzsvo7: