Attendees: Ken Lauer Vinod Gopalan Barry Fishler Alex Wallace Peregrine McGehee Zachary L Lentz Mitchell Cabral Nate Landis Robert S. Tang-Kong
Summary of Last Meeting:
LLNL Requirements:
- Setpoint tool shall be able to write to multiple devices store various configurations of these values.
- The RRL devices shall have the ability to move through multiple configurations throughout the entire shot cycle, but does not require reconfiguration when shots are being taken.
- The tool shall provide the operator to check configurations on-demand.
- There is no need for an atomic system as the time requirement to reach set configurations are in the hours range.
LLNL NIF System:
- At NIF setpoints can be created on-demand.
- Ability to continuously monitor the state/value/parameters of the device and setpoint.
- Can write to multiple devices at once.
- NIF has an Oracle database that is used to maintain setpoints and configurations.
- Other systems have configuration files that live on local controllers.
ATEF (Work In Progress):
- SLAC-developed tool for testing that can be used to verify and check configurations.
- Moving towards setting configurations as well.
- Configuration control has not been planned yet.
- ATEF is a work in progress and is not complete yet.
Goals:
- Have device-level configuration and management pattern for all of MECU.
- Find where we want to store configurations.
- LLNL needs a very convenient means to verify configurations before firing.
Lingering Questions:
- How are other large-scale EPICS systems managing this problem? The challenge being configuration management.
- Device-obstruction layer that sat on the client layer.
- SLAC can reach out to other teams to see how they are running this. SLAC's AD division is doing something similar (SCORE).
2/8/2023 Notes: