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-1987 Instrument control development <p>Develop an automatic method for flagging mis-identified cobras from convergence data, for further analysis and fine-tuning the algorithm. </p> INSTRM-1987

Find an analyze mis-identification in the cobra convergence

Task Normal Done Done karr karr EngRun Thu, 1 Jun 2023 06:58:45 +0000 Fri, 13 Oct 2023 17:59:06 +0000 Fri, 13 Oct 2023 17:59:06 +0000 ics_mcsActor 0 3 <p>We were discussing about this during the last ICS-PFI-MCS telecon, have you started to work on this yet ?</p> <p>I'm working on an way of flagging misidentifications automatically, but haven't got results yet. </p> <p>I've got a method for flagging potential misidentification, and am adding some diagnostic plotting routines to keep track of what's happening, and where things go wrong. We are getting cases here and there, and the effect of the misidentification on convergence is very similar to what was predicted by simulations. </p> <p>Please add a comment if you have have favourite misidentifications to contribute. </p> <p>97904: theta<br/> 97909: theta<br/> 97916: phi<br/> 97919: phi</p> <p>We need to look at the column definitions in cobra_target.</p> <p>There are pfi_nominal_x_mm and pfi_target_x_mm. Originally, pfi_target contained the final target postion for the convergence run, and pfi_nominal was supposed to contain the target position for each iteration. The latter took a while to implement, however, it looks like pfi_target was changed to contain the target for each iteration, while pfi_nominal contains the centre position of the patrol region. </p> <p>The cobra identification was using pfi_nominal, rather than pfi_target, which results in misidentifications in some cases. Changing either the table or the identification code will get rid of ~2/3 of the misidentifications in the regular convergence cases. </p> <p>Even with this problem, mis-identification are rare. Of 151 runs analyzed, 36 incidents were flagged.  </p> <p>The code has been tested and merged to master, so I close this ticket.</p> Development Rank 0|02qpjd:00r20060i200186403r7i36k