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-1792 Instrument control development <p><a href="https://github.com/Subaru-PFS/pfs_utils/blob/master/python/pfs/utils/coordinates/transform.py#L180" class="external-link" rel="nofollow">Here</a> in the pfs_utils, the boresight location is hard coded based on different elevation angle with initial value. We should think about possibility of using database value. </p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=rhl" class="user-hover" rel="rhl">rhl</a> Do you have any suggestion?</p> INSTRM-1792

Reading MCS boresight from database instead of hard coded.

Task Normal In Progress Unresolved karr chyan EngRun Thu, 17 Nov 2022 04:40:37 +0000 Thu, 18 Jan 2024 03:29:06 +0000 pfs_utils 0 4 <p>My guess is that it doesn't matter, and that the fit will converge even if the model I hardwired is pretty bad.  In fact, it would probably converge even if we didn't attempt to correct for altitude.</p> <p>However, this is something that we could and should confirm.</p> <p>To be addressed sometime in the next 6 months.</p> <p>At ASIAA software informal meeting, we agreed to start with to check difference run by run difference.</p> <p>Here is a visit for the previous Boresight measurements:</p> <div class='table-wrap'> <table class='confluenceTable'><tbody> <tr> <th class='confluenceTh'>Run</th> <th class='confluenceTh'>visit</th> <th class='confluenceTh'>El <span class="error">&#91;deg&#93;</span></th> <th class='confluenceTh'>InR range <span class="error">&#91;deg&#93;</span></th> <th class='confluenceTh'>InR step <span class="error">&#91;deg&#93;</span></th> <th class='confluenceTh'>Note</th> </tr> <tr> <td class='confluenceTd'>2021.09</td> <td class='confluenceTd'>67419 – 67430</td> <td class='confluenceTd'>90</td> <td class='confluenceTd'>+180 ~ -150 </td> <td class='confluenceTd'>-30</td> <td class='confluenceTd'> </td> </tr> <tr> <td class='confluenceTd'> </td> <td class='confluenceTd'>67447 – 67458</td> <td class='confluenceTd'>60</td> <td class='confluenceTd'>+180 ~ -150</td> <td class='confluenceTd'>-30</td> <td class='confluenceTd'>ADC=0</td> </tr> <tr> <td class='confluenceTd'> </td> <td class='confluenceTd'>68290 – 68301</td> <td class='confluenceTd'>60</td> <td class='confluenceTd'>-150 ~ +180</td> <td class='confluenceTd'>+30</td> <td class='confluenceTd'>ADC=7.32</td> </tr> <tr> <td class='confluenceTd'> </td> <td class='confluenceTd'>67459 – 67470</td> <td class='confluenceTd'>30</td> <td class='confluenceTd'>-150 ~ +180</td> <td class='confluenceTd'>+30</td> <td class='confluenceTd'>ADC=0</td> </tr> <tr> <td class='confluenceTd'> </td> <td class='confluenceTd'>68278 – 68289</td> <td class='confluenceTd'>30</td> <td class='confluenceTd'>+180 ~ -150</td> <td class='confluenceTd'>-30</td> <td class='confluenceTd'>ADC=22</td> </tr> <tr> <td class='confluenceTd'>2021.11</td> <td class='confluenceTd'>69959</td> <td class='confluenceTd'>90</td> <td class='confluenceTd'>-165 ~ +165</td> <td class='confluenceTd'>+30</td> <td class='confluenceTd'>Hexapod position was incorrect</td> </tr> <tr> <td class='confluenceTd'> </td> <td class='confluenceTd'>69963</td> <td class='confluenceTd'>75</td> <td class='confluenceTd'>-165 ~ +165</td> <td class='confluenceTd'>+30</td> <td class='confluenceTd'>Hexapod position was incorrect</td> </tr> <tr> <td class='confluenceTd'> </td> <td class='confluenceTd'>69960</td> <td class='confluenceTd'>60</td> <td class='confluenceTd'>+165 ~ -165</td> <td class='confluenceTd'>-30</td> <td class='confluenceTd'>Hexapod position was incorrect</td> </tr> <tr> <td class='confluenceTd'> </td> <td class='confluenceTd'>69962</td> <td class='confluenceTd'>45</td> <td class='confluenceTd'>+165 ~ -165</td> <td class='confluenceTd'>-30</td> <td class='confluenceTd'>Hexapod position was incorrect</td> </tr> <tr> <td class='confluenceTd'> </td> <td class='confluenceTd'>69961</td> <td class='confluenceTd'>30</td> <td class='confluenceTd'>-165 ~ +165</td> <td class='confluenceTd'>+30</td> <td class='confluenceTd'>Hexapod position was incorrect</td> </tr> <tr> <td class='confluenceTd'>2022.06</td> <td class='confluenceTd'>77490 – 77495</td> <td class='confluenceTd'>90</td> <td class='confluenceTd'>-150 ~ +150</td> <td class='confluenceTd'>+60</td> <td class='confluenceTd'> </td> </tr> <tr> <td class='confluenceTd'>2022.11</td> <td class='confluenceTd'>82410</td> <td class='confluenceTd'>90</td> <td class='confluenceTd'>-165 ~ +165</td> <td class='confluenceTd'>+30</td> <td class='confluenceTd'> </td> </tr> </tbody></table> </div> <p>  Note that  Hexapod position was set at different position (1.8mm in X_pfi, -0.1mm in Y_pfi) from position we usually use. So, this offset should be taken into account.</p> <p>Jennifer and I talked about this. In the 2023 April/May run, we have updated MCS boresight , and found that it was shifted. <br/> <span class="nobr"><a href="https://pfspipe.ipmu.jp/jira/secure/attachment/15636/15636_mcs_boresight_comp.py" title="mcs_boresight_comp.py attached to INSTRM-1792">mcs_boresight_comp.py^{<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>If the slope is stable, we could use database to get boresight by reading the latest measurement at a given EL (e.g., EL=90) and the EL at the observation. Jennifer will check the stability of the slope.</p> <p>I found that the attachment was wrong the above comment. This figure compares boresight position used in pfs_utils and  that measured in April 2023. Since it, we didn't measure boresight at different EL, so stability of the slope is to be checked (in particular X).</p> <p><span class="image-wrap" style=""><img src="https://pfspipe.ipmu.jp/jira/secure/attachment/17037/17037_image-2024-01-18-12-25-20-174.png" height="301" width="254" style="border: 0px solid black" /></span></p> Development Rank 0|02qpjd:00r300r