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-1276 Instrument control development <p>Update the mcsActor with database integration, and full sequence of commands.</p> INSTRM-1276

Update mcsActor with fibreID routine and database interation

Task Normal Done Done karr karr EngRun PFI Mon, 17 May 2021 03:05:19 +0000 Fri, 15 Oct 2021 12:01:29 +0000 Fri, 15 Oct 2021 12:01:29 +0000 ics_mcsActor spt_operational_database 0 3 <p>The current code now runs on the ASRD computer using simulated images. </p> <p>Thank you for the update! A couple of questions:</p> <ul> <li>The values seem to be in pix. Is this fixed once the coordinate transformation issue is resolved?</li> <li>`pfi_nominal_x/y_mm` changes with iteration, but I thought it was the final destination after all iterations so didn't change, instead `pfi_target_x/y_mm` increases with iteration. Am I mis-understanding? Maybe naming of the column is bad.</li> <li>Are other columns such as step size and on-time also going to be populated?</li> <li>In `cobra_match` table, there seem to be records for only interation=1, are you also going to pupulate it for other iteration?</li> </ul> <p>Thanks for the comments. In answer,</p> <ul> <li>I added a switch for fibre input methods, which will toggle between asrd (pixels, no transforms, XML file geometry), commissioning data (full transformations, fake fiducial fibres, no cobra movement), and the real case. For the last case, we need the transformations, geometry files and FF coordinates in mm and FF exposures. The switch itself can probably be removed once everything is in place.</li> <li>that will be my mistake, I'll change the variable names</li> <li>yes, but by the fps actor. For testing, I made fake database entries for the pfs_visit (and fiducial_fiber tables when needed), and manually populated the mcs_exposure table. In full operation the former will be populated before the mcs actor is called, and the mcs_exposure will be populated when the exposure is taken. I don't know the status of those parts.</li> <li>yes, the current population was for testing purposes, and I was writing/deleting entries repeatedly as I ran the tests.  </li> </ul> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=karr" class="user-hover" rel="karr">karr</a>: what's the status of this ticket? Are you using the opDB now for your interactions?</p> <p>During a ticket review 2021-10-14 @jkarr reports this has being complete.</p> Blocks INSTRM-1322 Development Rank 0|02qpuc:i6001gr068fhw9qo4o0rr Sprint EngRun03 Story Points 2.0