[INSTRM-425] Implement state engine in ccdActor Created: 23/Jul/18 Updated: 23/Oct/19 |
|
| Status: | Open |
| Project: | Instrument control development |
| Component/s: | ics_ccdActor |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | cloomis |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | SM1, SPS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Story Points: | 1 | ||||||||
| Sprint: | SM1-2019 G, SM1-2019 K, SM1-2019 L, SM1-2019 N | ||||||||
| Comments |
| Comment by arnaud.lefur [ 25/Feb/19 ] |
|
ccdActor have the exposureState keyword, which is nice, if by analogy with the enu state machine engine, it's what I call the substate: It reflects what's the device is currently doing. What's missing is the operational state machine, which tells whether the device is ready to be operated nominally or not (should be "ONLINE"). But in the ccdActor, there is not much requirement I guess. To be able to take an exposure you need just ccd and fee controllers connected right ? INSTRM-426, I could have a CU state as the logical and of xcu state and ccd state. |
| Comment by hassan [ 23/May/19 ] |
|
cloomis and arnaud.lefur will have a dedicated discussion to address this. |
| Comment by hassan [ 04/Jul/19 ] |
|
Needs a dedicated telecon with @cloomis and @arnaud. |
| Comment by hassan [ 11/Jul/19 ] |
|
arnaud.lefur to create a separate ticket for SM1 purposes only, using only the core essential commands. This ticket will be moved to the SPS label (ie not needed for SM1). |
| Comment by hassan [ 25/Jul/19 ] |
|
To discuss before Arnaud goes on leave. |
| Comment by arnaud.lefur [ 25/Jul/19 ] |
|
I have a ccdActor simulator on my machine, I will add the state engine, so you can glance at it. |