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-1155 Instrument control development <p>The fpsActor commands the mcsActor to acquire images and generate spot lists. The cobraCharmer library has a tree of classes which allow commanding one of several local camera to generate spot lists. The two interfaces are similar but not identical, and the cobraCharmer library also handles some desirable per-run (convergence test, motor map generation, etc) book-keeping.</p> <p>Merge the two. I'll add an mcsActor "camera" subclass to the cobraCharmer/cobraCoach library and have the fpsActor call that. It would have been cleaner to have put all the local cameras into mcsActor at the start, but that was always going to make other development clumsier.</p> <p>Correctly factoring out spot assignment functionality so that can easily be split between fps and mcs is not part of this, but that will be kept in mind.</p> INSTRM-1155

Merge FPS-over-MCS and cobraCharmer camera logic

Task Normal Done Done cloomis cloomis PFI Fri, 8 Jan 2021 18:29:04 +0000 Fri, 13 Aug 2021 16:35:30 +0000 Fri, 13 Aug 2021 16:35:30 +0000 ics_cobraCharmer ics_fpsActor 0 3 <p>I have establish a ticket branch tickets/<a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1155" title="Merge FPS-over-MCS and cobraCharmer camera logic" class="issue-link" data-issue-key="INSTRM-1155"><del>INSTRM-1155</del></a> for fpsActor. This ticket branch is used for the transition of this functionality. </p> <p>PR has been merged. Can we close this ticket?</p> <p>The work as described in the ticket was mostly done in the ics_cobraCharmer work for the closed <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1333" title="add mcsActorCam for using only mcsActor to read cameras" class="issue-link" data-issue-key="INSTRM-1333"><del>INSTRM-1333</del></a>. The ics_fpsActor work in <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-1155" title="Merge FPS-over-MCS and cobraCharmer camera logic" class="issue-link" data-issue-key="INSTRM-1155"><del>INSTRM-1155</del></a> ended up being a grab bag of db/coordinate/command integration work.</p> Development Rank 0|zzs3pk: Story Points 2.0