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-1394 Instrument control development <p>In relation to <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1393" title="PfiTransform should write updated transformation coefficients to opDB" class="issue-link" data-issue-key="INSTRM-1393"><del>INSTRM-1393</del></a>, (re)design the tables that store the PFI-MCS transformation information.</p> <p>This ticket should be addressed once we know the degrees of freedom of the needed transformation updates.</p> INSTRM-1394

Update PFI-MCS transformation tables on opDB

Task Normal Done Done karr hassan EngRun Mon, 11 Oct 2021 17:06:46 +0000 Thu, 15 Sep 2022 15:59:21 +0000 Thu, 15 Sep 2022 04:29:41 +0000 spt_operational_database 0 4 <p>I just reported another issue to Robert in the meeting last time.  There are inconsistency between the matched table location and location transformed from pixel coordinated.  I guess there are some book keeping issue and I would need Robert's advice.  </p> <p>There is a upgrade of pfs_utils to 6.1.5. We should test this to see if the problem solved.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=chyan" class="user-hover" rel="chyan">chyan</a> what is the status of this work?</p> <p>Transformations seem to be working well. <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=karr" class="user-hover" rel="karr">karr</a> to confirm with RHL whether the PFI-MCS transformations are sufficiently stable, so need to firm down the definitions of the coefficients.</p> <p>Robert has confirmed that the transformation is stable, so I can proceed with this. </p> <p>Updated write statements have been added to ics_mcsActor, and a matching scheme to a branch in spt_operation_database. The necessary parameters are passed back as part of the transform object, so the transform code doesn't need any modifications.  </p> <p>I am confirming the format with Robert (so I haven't missed anything that should be written). </p> <p>OK, so after you confirm that the format is OK, please make a pull request. I'll review that and merge. Thanks.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=karr" class="user-hover" rel="karr">karr</a> Any update on confirming the format?</p> <p>I've created the pull request. Once the database schema is updated, I can merge the ics_mcsActor part of the code. </p> <p>Thank you, <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=karr" class="user-hover" rel="karr">karr</a> !</p> <p>One small thing is that I guess we use `camera_name` to distinguish MCS and 71M for the past data, but we already have `mcs_camera_name` in `mcs_camera` table and `mcs_camera_id` is in `mcs_exposure` table. Do we still need a similar column in this table?</p> <p>This was merged and closed.</p> <p>ics_mcsActor changes pushed to master as well. </p> <p>Oh, I closed the ticket before mcsActor changes are merged. Apologies...</p> Blocks INSTRM-1588 Relates INSTRM-1393 Development Rank 0|zzsui6:y Sprint PreEngRun05 F preEngRun07Sep Story Points 2.0