Run Controllers (1)

State model and hierarchy

• Run controllers make transitions between states:
  • Initial
  • Loaded
  • Configured
  • Running
  • Paused
  • also some superstates and error states
• Controller may have child controllers
• Parent makes transition first, then tells child controllers to do the same
• Synchronisation: either all children asynchronously ``at once'', or one by one in forward or reverse order
• NO private synchronisation or communication between controllers in different crates

L1Calo Hierarchy

• We will sometimes want TTC actions before all other actions in one transition, or after all other actions.
• Implies extra layer in hierarchy for TTC
• Is this enough?