Use sequencer to build up general purpose "aggregates" for things
like beam studies, equipment tests etc.
Some equipment classes (e.g.collimators) have fairly sophisticated state
model (listener/OAC/state function map [2d array] etc.). The sequencer can
initiate state transitions (e.g. initiate halo cleaning). Limits and settings
have to be pre-loaded.
State devices include: Tevatron, mode, Helix, SDA, TevCol etc.
TeVCol: state 1: init, state 2: touch, 3: remove halo, 4: retract. etc
Requisite data downloaded to front-ends (limits etc.)
Clock events play an important role, intelligence is distributed, data
is pre-down loaded (avoiding run time transmission failures) and then play
via clock events. Multiple functions resident in WFGs.
Key parameters going out at 720 Hz - MDA.
Language - verb/object SET FRED ON etc. Qualifiers. Command list here.
Acknowledgement from ops where required.
Essential functionality built on CLIB (load functions etc.)
More sophisticated stuff by invoking scripts
ACL executes a file containing an ACL (Accelerator Command Language) script.
Alternate pathways
Mode - some sort of mode process/listener which can triggered by sequencer
or other device
