You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 31, 2022. It is now read-only.
Brief summary of issue (work in progress...)
Certain applications require a proper sequence of operations
GEMSupervisor
/hardware managers/etc.)LPMController
/ICIController
/PIController
)EVM
/BU/
FerolController`)Initialize
Only GEM applications are currently set up to expect this, and at the moment the order doesn't matter, though a future could be envisioned where
GEMSupervisor
is firstAMC13Manager
is next (or)AMCManager
OptoHybridManager
is nextHalt
/Stop
/Pause
These all can share a similar ordering, as when running, we want to stop the thing furthest from our system first, e.g., TCDS, then move closer
Halted
when GEM applications areInitialized
Configure
Need to configure TCDS first, to ensure that clocks are coming
Start
/Resume
/Enable
Start applications closest to our system first, and then move away, e.g., TCDS should be last to start
EVM
must be enabled before theBU
(but after anRU
andTA
, if present)Reset
Probably quite similar to
Halt
would be sufficientThe text was updated successfully, but these errors were encountered: