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-1568 Instrument control development <p>There are bash scripts to move to near the expected dot positions and then cross the dots while taking MCS exposures. One for theta, one for phi.</p> <p>Make iic command for these. Take both by default and allow taking just one?</p> INSTRM-1568

Add iic commands to acquire phi and theta dot crossings

Task Normal Done Done arnaud.lefur cloomis EngRun Fri, 1 Apr 2022 13:20:58 +0000 Wed, 15 Jun 2022 01:28:33 +0000 Wed, 15 Jun 2022 01:28:33 +0000 ics_iicActor 0 5 <p>Sounds good.<br/> Is it clear that two crossings will constrain the model well enough ?</p> <p>It is clear that there will (only) be phi and theta crossings, where only that motor is moved. There <b>might</b> be several starting positions for each, though.</p> <p>The current implementation for each crossing is to converge to a pfsDesign, then step the selected motor across the dot. Having a actor config knob which is a list of one or more pfsConfigIds for each would cover that. The config could also have the step sizes and counts, etc. </p> <p>This ticket covers only data acquisition, but we might want to also automate the new dot position estimation using Neven algorithm.</p> Development Rank 0|zzstqm:zzzi Sprint PreEngRun06June