[INSTRM-1568] Add iic commands to acquire phi and theta dot crossings Created: 01/Apr/22 Updated: 15/Jun/22 Resolved: 15/Jun/22 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | ics_iicActor |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | arnaud.lefur |
| Resolution: | Done | Votes: | 0 |
| Labels: | EngRun | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | PreEngRun06June |
| Description |
|
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. Make iic command for these. Take both by default and allow taking just one? |
| Comments |
| Comment by arnaud.lefur [ 02/Apr/22 ] |
|
Sounds good. |
| Comment by cloomis [ 02/Apr/22 ] |
|
It is clear that there will (only) be phi and theta crossings, where only that motor is moved. There might be several starting positions for each, though. 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. |
| Comment by arnaud.lefur [ 23/Apr/22 ] |
|
This ticket covers only data acquisition, but we might want to also automate the new dot position estimation using Neven algorithm. |