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-1229 Instrument control development <p>Update both tables per discussion of the last phonecon. Rename `cobra_movement` to e.g. `cobra_target` which also includes target position in mm and flag for collision etc. Rename `cobra_status` to e.g. `cobra_matched` which includes matched information from mcs data.</p> INSTRM-1229

Sort out current `cobra_status` & `cobra_movement`

Task Major Done Done Kiyoto Yabe Kiyoto Yabe opDB Wed, 7 Apr 2021 02:41:22 +0000 Fri, 16 Apr 2021 07:26:47 +0000 Fri, 16 Apr 2021 07:26:47 +0000 spt_operational_database 0 2 <p>The initial fix can be found in the branch.</p> <p>`cobra_target` (previously `cobra_movement`) includes cobra targeting values such as the target positions and step size of each cobra in each iteration. `cobra_matching` (previously `cobra_status`) covers the matched position of spots on the MCS image. I just revert onto `pfi_nominal_<span class="error">&#91;xy&#93;</span>_mm` as the final cobra destination, which is consistent with the datamodel.</p> <p>Anyway, any feedback regarding structure, naming, additional columns is all welcome. <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=chyan" class="user-hover" rel="chyan">chyan</a> <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=karr" class="user-hover" rel="karr">karr</a> <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a> <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hassan" class="user-hover" rel="hassan">hassan</a> ?</p> <p>Attached below is the zoom-in diagram for the related tables:</p> <p><span class="nobr"><a href="https://pfspipe.ipmu.jp/jira/secure/attachment/13530/13530_opdb_cobra_tables_rev1.pdf" title="opdb_cobra_tables_rev1.pdf attached to INSTRM-1229">opdb_cobra_tables_rev1.pdf^{<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>Some thoughts:</p> <ul class="alternate" type="square"> <li>having cobra_target key on mcs_frame_id bothers me: the cobra_target row will be inserted before the mcs exposure is taken. And the cobra_target table is filled by a completely separate actor (fps) from the mcs_exposure table (mcs).</li> <li>should cobra_matching link to cobra_target and drop the "nominal" fields?</li> <li>the cobra_matching table needs a flags field.</li> <li>the cobra_target table should have target angles as well as (x, y) and (step, ontime).</li> <li>should there be <b>two</b> motor_calib_ids and should they actually be cobra_motor_model_ids?</li> </ul> <ul class="alternate" type="square"> <li>I think I would rename "cobra_matching" to "cobra_match", maybe?</li> </ul> <p>This is the second revision, which is a hasty fix so may be something wrong. Anyway, let's talk about this at the phonecon tomorrow.</p> <p><span class="nobr"><a href="https://pfspipe.ipmu.jp/jira/secure/attachment/13535/13535_opdb_cobra_tables_rev2.pdf" title="opdb_cobra_tables_rev2.pdf attached to INSTRM-1229">opdb_cobra_tables_rev2.pdf^{<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> Development Rank 0|zzs4v4: