Overview, Context
Currently the controls-specific concept of operations (ConOps) lacks definition. In order to develop a clear picture of what subsystems the shot sequencer is expected to coordinate, we also need a clear picture of what these subsystems are and what their scope is supposed to be. We have been tasked with organizing a workshop to help define the shot sequencing flowchart, which has brought this gap to the forefront.
Developing a controls-specific ConOps will require an understanding of all the partner lab laser system and their respective ConOps.
Approach
I am currently of the opinion that it is best for LCLS to have an established vision for sequencing that the partner labs then conform to. This can and should be informed by the partner lab laser system ConOps, but they should not be dictated by them.
Is the focus of this assuming everything is aligned? From parameter set to post-shot?
Background research
A landing spot for resources I find as I gather them
MEC-U (LCLS)
- MECU-FR-0015.doc: gives overview conops, but nothing controls related
- Details: facility layout, standard configurations (which laseres), port locations, laser maintenance, experimental operations (mock schedules), personnel requirements
- Subsystems:
- Rough Sequence:
- Details: facility layout, standard configurations (which laseres), port locations, laser maintenance, experimental operations (mock schedules), personnel requirements
- A drawing (with a few tabs)...
- subdivides tasks into broad categories (But does not enumerate them all):
- Operation modes { Phases { Macrosteps { Steps { Microsteps
- simplified swim-lane-type chart. probably good to replicate at a high level (notice this has no Controls system entries... )
- subdivides tasks into broad categories (But does not enumerate them all):
Rochester (HELP)
- 2w Cal Shot Cycle and ConOps: Give a good idea of what we expect HELP to do
- Subsystems:
- Shot Executive (Master): Configures system, sends instructions to clients and waits for return statuses
- Sub system executives....?: Configures subsystems for shot (what these subsystems are is unclear. Is it different from the below two?)
- Power Condition Executives: Coordinates PCUs, records charge time, ...
- Facility Interlock Executive: coordinates access, monitors interlocks
- States: Active, Preshot, Charge, Fire_AtVolt, Fired, Postshot
- Rough Sequence / Events:
- Build shot template from Shot Executive
- Approve/pre-shot template
- Build Power Conditioning Template
- Approve Power Conditioning Template
- Download Power Conditioning Template
- Load/set-up pulse shape
- Load latest Wavefront Control Correction
- Configure system for 1w alignment
- Align injection table to 2w Diagnostic Package
- Perform wavefront correction w/o PID
- Align main cavity pinholes
- Set up apodizers
- Set timing
- Sweep Bays
- Run wavefront correction with PID
- Enable SSD Bandwidth
- Set beam energy
- Configure devices for shot and confirm
- Ensure Calorimeter software ready
- Start PEPC
- Start charging
- Monitor systems during shot cycle
- Resume normal access in bays
- Review shot data
- Subsystems:
LLNL (RRSP/LP)
- Barry passed along a large, possibly too detailed flowchart via email (To be parsed / summarized...)
MECU-LLNL-143 20231211 Experiment Model - Shot Sequence.pdf- Subsystems:
- NIF Collaboration Manager
- Target Area Collaboration Manager
- Bundle Collaboration Manager
- Bu35 Bundle Collaboration Manager
- Rough Sequence:
- Begin Shot
- Populate Plan
- Implement Plan
- Ready
- Sequential Rod Shot Pre-Countdown
- Sequential Rod Shot Countdown
- <<Rod Shot>>
- Sequential Rod Shot Post-Countdown
- Sequential Rod Shot Analyze Shot
- Ready
- System Shot Pre-Countdown
- System Shot Countdown
- << System Shot >>
- System Shot Post-Countdown
- Analyze System Shot
- End Shot Cycle
https://nifuserguide.llnl.gov/home/4-laser-system/41-laser-configuration