Skip to content
This repository has been archived by the owner on Jan 31, 2022. It is now read-only.

Order of operations for state transitions #5

Open
jsturdy opened this issue Aug 21, 2017 · 0 comments
Open

Order of operations for state transitions #5

jsturdy opened this issue Aug 21, 2017 · 0 comments

Comments

@jsturdy
Copy link
Contributor

jsturdy commented Aug 21, 2017

Brief summary of issue (work in progress...)

Certain applications require a proper sequence of operations

  1. GEM applications (GEMSupervisor/hardware managers/etc.)
  2. TCDS applications (LPMController/ICIController/PIController)
  3. uFEDKIT applications (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 first
  • AMC13Manager is next (or)
  • in conjunction with the AMCManager
  • OptoHybridManager is next

Halt/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

  • TCDS should be Halted when GEM applications are Initialized

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

  • For uFEDKIT operations, the EVM must be enabled before the BU (but after an RU and TA, if present)

Reset

Probably quite similar to Halt would be sufficient

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant