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-1535 Instrument control development <p>Although we discussed the place to store the dot position (e.g. discussion related with <a href="https://pfspipe.ipmu.jp/jira/browse/INFRA-207" title="Create repo(s) for varying instrument characteristics" class="issue-link" data-issue-key="INFRA-207">INFRA-207</a>), we re-visited this topic after the November run.<br/> So far, dot position is stored under <tt>pfs_instdata</tt>, and the latest data contains spotId, x, y position in mm, and dot radius in mm.</p> <p>I personally think the dot position should be stored on <tt>pfs_insdata</tt> for netflow/ETS.<br/> What I think we need to discuss is whether we should store the information on opDB (and its schema). Considering that FF positions are stored on opDB as well as <tt>pfs_insdata</tt>, it should be stored on opDB for cobra movement. </p> <p>The data format on pfs_instdata should also be discussed... By the way, does spotId synchronize with cobraId?</p> INSTRM-1535

Determine (again) the places to store the dot position

Task Normal Done Done Unassigned yuki.moritani EngRun Fri, 25 Feb 2022 10:28:55 +0000 Fri, 8 Jul 2022 07:14:15 +0000 Fri, 8 Jul 2022 07:14:15 +0000 0 2 <p>Following discussions during recent ICS/PFI telecons: We need to establish how stable the dot positions are before moving to {</p> {pfs_instdata} <p>}</p> <p>It has been agreed during today's ICS/PFI telecon that the data should be stored initially in pfs_instdata. If we find during the engineering runs that the data are unstable, they should be moved to opDB.</p> <p>As commented above, the dot position is stored in <tt>pfs_insdata</tt>:</p> <p><a href="https://github.com/Subaru-PFS/pfs_instdata/blob/master/data/pfi/dot/black_dots_mm.csv" class="external-link" rel="nofollow">https://github.com/Subaru-PFS/pfs_instdata/blob/master/data/pfi/dot/black_dots_mm.csv</a></p> <p>Once the position is updated, the table will be stored here. The format is OK, but I'd propose to rename "spotId" to "dotId", because (1) we call the dots "dots", and (2) spotId is used by MCS centroid and might be confusing. </p> <p>And there is a 1-1 mapping between <tt>dotId</tt> and <tt>cobraId</tt>, correct?</p> <p>Correct. Thank you for adding this.</p> <p>Since the latest measured position during the Jun run was uploaded to the above location, I close this ticket. (I defer column name issue... if needed this will be addressed with the new ticket)</p> Development Rank 0|zzstqm:zzzr Sprint PreEngRun06June