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/INSTRM-1414 Instrument control development <p>As discussed during the commissioning telecon 2021-10-20: the blackspot geometry is currently not fully understood. Please provide the updated geometry. </p> <p>The most direct method to determine the blackspot geometry, proposed by Craig Loomis, is to 'scan' each blackspot using the related cobra, and monitor the flux variation using the SpS to determine the blackspot boundaries. Two chords across a single blackspot may be sufficient.</p> INSTRM-1414

Update blackspot geometry

Task Normal Done Done chyan hassan EngRun Fri, 22 Oct 2021 02:54:23 +0000 Fri, 2 Sep 2022 12:56:33 +0000 Fri, 1 Jul 2022 04:54:50 +0000 0 6 <p>This is related to the dot-crossing testing. <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=ncaplar" class="user-hover" rel="ncaplar">ncaplar</a> Do you have and update?</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=ncaplar" class="user-hover" rel="ncaplar">ncaplar</a> has provided these data to ASIAA by email 2022-02-24.</p> <p>We need to agree where to store these data.</p> <p>The data also need to be verified separately. </p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=yuki.moritani" class="user-hover" rel="yuki.moritani">yuki.moritani</a> will address both points above.</p> <p>Neven provided the data in pickle on pfsa-user01:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> /work/ncaplar/BlackDotsData/dots_new_Nov /work/ncaplar/BlackDotsData/dots_new_Jan /work/ncaplar/BlackDotsData/dots_new_Feb </pre> </div></div> <p>He also reported position difference in commissioning telecon (<a href="https://sumire.pbworks.com/w/file/148019094/Commissioning_telecon_Feb_15_Neven_Caplar_PSF_Black_dots.pdf" class="external-link" rel="nofollow">Slide</a>)<br/> Each data has 2394 positions. I think the final position and its uncertainty should be obtained after optimizing the algorithm (<a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1530" title="Optimize the dot-crossing algorithm" class="issue-link" data-issue-key="INSTRM-1530"><del>INSTRM-1530</del></a>)<br/> In regard to the place to store the do position, I filed a ticket (<a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1535" title="Determine (again) the places to store the dot position" class="issue-link" data-issue-key="INSTRM-1535"><del>INSTRM-1535</del></a>).</p> <p>Need to verify this with the PFI on POPT2 during daytime, so after May 13.</p> <p>Still plan to do this on the telescope during the June 2022 Eng Run.</p> <p>This file is updated with the Butler class. </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-python"> butler = Butler(configRoot=os.path.join(os.environ[<span class="code-quote">"PFS_INSTDATA_DIR"</span>], <span class="code-quote">"data"</span>)) dotDF = butler.get(<span class="code-quote">'black_dots'</span>) </pre> </div></div> Blocks INSTRM-1385 INSTRM-1397 PIPE2D-914 Relates INSTRM-1503 INSTRM-1447 Development Rank 0|02qpib:i Sprint preEngRun07Sep