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/FIBERALLOC-44 Target to fiber allocation and configuration <p>As mentioned in the #obsproc channel on slack: <a href="https://sumire-pfs.slack.com/archives/CA9FJBGD6/p1656687553157589" class="external-link" rel="nofollow">https://sumire-pfs.slack.com/archives/CA9FJBGD6/p1656687553157589</a>, and recent ICS/PFI telecons, bright stars seem to be lost due to fiber collisions in the fiber allocation algorithm.</p> <p>Please investigate and fix.</p> FIBERALLOC-44

Bright stars lost due to fiber collisions

Task Normal Done Done Kiyoto Yabe hassan EngRun Fri, 19 Aug 2022 15:34:43 +0000 Thu, 29 Sep 2022 05:17:19 +0000 Thu, 29 Sep 2022 05:17:19 +0000 0 7 <p>This is under active investigation by MPE/MPA. We received the instructions to run the code at Subaru which we have begun to do now.</p> <p>exec: sum: We found that the particular mentioned bright star was flagged as not visible due it's proximity to a black dot.</p> <p> </p> <p>When netflow is called</p> <p>it in turn calls ics.cobraOps.TargetSelector to compute target visibilities.</p> <p>The attached plot shows a red cross for all non-visible targets. Observe that it falls very close to </p> <p>a black dot. The orange color indicates the priority=nonobservationcost. There is actually another</p> <p>target at x~56, y ~ -70 that gets dropped for the same reason despite large weight (orange halo).</p> <p> </p> <p>We have scanned the entire focal plane and find not situation where a visible </p> <p>high priority target has not been allocated.</p> <p> </p> <p>The definition of the black dot avoidance of course might require attention, but netflow</p> <p>seems to be ok.</p> <p> </p> <p>I'd propose to close this ticket in favor of a new ticket to investigate black dot avoidance criteria.</p> <p> </p> <p><span class="image-wrap" style=""><img src="https://pfspipe.ipmu.jp/jira/secure/attachment/15317/15317_image-2022-09-09-16-44-18-638.png" style="border: 0px solid black" /></span></p> <p> </p> <p> Slides from Max presented during a discussion on this topic 2022-09-12 added: <span class="nobr"><a href="https://pfspipe.ipmu.jp/jira/secure/attachment/15322/15322_bright_star.key.pdf" title="bright_star.key.pdf attached to FIBERALLOC-44">bright_star.key.pdf^{<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>We asked Chi-Hung about xml file at a meeting a few days ago. According to him, xml file was updated in June run based on the measurement during the run, except for the arm length. For arm length, the values measured at test bench (i.e. off-the telescope) which has good repeatability. (The arm length on the telescope has not been confirmed for its repeatability (<a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1671" title="Study why the Cobra arm length were different between Sep 2021 and June 2022." class="issue-link" data-issue-key="INSTRM-1671"><del>INSTRM-1671</del></a>). ) The xml file in the 2021 September is not based on measurement.</p> <p>I have changed the script to generate pfsDesign according to the discussion in the meeting we had on 2022-09-12. The change is in the ticket branch: <a href="https://github.com/Subaru-PFS/ets_target_database/tree/tickets/FIBERALLOC-44" class="external-link" rel="nofollow">https://github.com/Subaru-PFS/ets_target_database/tree/tickets/FIBERALLOC-44</a> . Basically, we get back to the original function so that we can load the measured geometry information of both cobras and dots.</p> <p>Just only checks for NGC6633.</p> <p>If we take a margin fraction of 1.8333 (means the dot radius is 1.375mm, which is the assumption in the previous run), the completeness of bright Gaia sources (in SM1 field) is ~79%, while if we don't take the margin the completeness is ~95%.</p> <p>An example of losing targets by expanding the dot search radius is below:</p> <p><span class="image-wrap" style=""><a id="15326_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/15326/15326_example_dot_margin.png" title="example_dot_margin.png" file-preview-type="image" file-preview-id="15326" file-preview-title="example_dot_margin.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/15326/_thumb_15326.png" style="border: 0px solid black" /></a></span></p> <p> </p> <p>The changes adopted in the last run have been merged, so this ticket can be closed. Note that some quick fixes unrelated to this ticket but necessary for the run are also included in the ticket branch unfortunately.</p> Development Rank 0|02qpio:f Sprint preEngRun07Sep Story Points 2.0