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-1511 Instrument control development <p>We are trying dot-crossing algorithm on bench from Jan 22. However, we encountered problem that the convergence result seems to be very very bad after some software update. Need to investigating the root cause.</p> INSTRM-1511

Debugging the bad converging issue on test bench

Task Normal Done Done chyan chyan Sat, 22 Jan 2022 16:56:16 +0000 Mon, 24 Jan 2022 17:36:52 +0000 Mon, 24 Jan 2022 17:36:52 +0000 0 1 <p>Ok, there are few issues here. </p> <ul> <li>First, the centroid algorithm was optimized for real MCS spots. When using 71M, the current settings are not suitable for 71M spots. The current MCS optimizations could not detect all 71M spots.</li> </ul> <ul> <li>The pfs_utils 6.1.2 and 6.1.4 are different when transferring spot from pixel to mm. In the plot, we asked cobra to be at home position. As we can see, both versions give different results.<br/> <span class="image-wrap" style=""><a id="15079_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/15079/15079_Figure+1-3.png" title="Figure 1-3.png" file-preview-type="image" file-preview-id="15079" file-preview-title="Figure 1-3.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/15078/_thumb_15078.png" style="border: 0px solid black" /></a></span> </li> </ul> <ul> <li>Using createTrajectory in convergence loop creates funny results. The convergence number increased from ~16 to ~50, two times more. Also, it impacts the convergence speed. This is the convergence without createTrajectory:<br/> <span class="image-wrap" style=""><a id="15081_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/15081/15081_Figure+1-4.png" title="Figure 1-4.png" file-preview-type="image" file-preview-id="15081" file-preview-title="Figure 1-4.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/15079/_thumb_15079.png" style="border: 0px solid black" /></a></span> <br/> This is with createTrajectory<br/> <span class="image-wrap" style=""><a id="15081_thumb" href="https://pfspipe.ipmu.jp/jira/secure/attachment/15081/15081_Figure+1-4.png" title="Figure 1-4.png" file-preview-type="image" file-preview-id="15081" file-preview-title="Figure 1-4.png"><img src="https://pfspipe.ipmu.jp/jira/secure/thumbnail/15081/_thumb_15081.png" style="border: 0px solid black" /></a></span> </li> </ul> <p>After talking to Chih-Yi, we fixed the bug when using createTrajectory. The simulation mode still change the cobra informations. Therefore, one should set the cobra arms to their current location after getting predicted locations from simulator. </p> <p>Since this issue is solved, I am closing this ticket and create related tickets for related issues. </p> Development Rank 0|02qpq3:r3s000000043