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.

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:

Rochester (HELP)

• 2w Cal Shot Cycle and ConOps: Give a good idea of what we expect HELP to do
  
  • Subsystems:
  • Rough Sequence:

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:
  • 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
    • ... on to other shot?

Resources

MEC-U Sharepoint Con-ops folder