Attendees: Ken Lauer Vinod Gopalan Barry Fishler Alex Wallace Peregrine McGehee Zachary L Lentz Mitchell Cabral 

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.
  • Operators set a value for the device and tell it to go to that value.
    • This is done through GUI and settings can be saved and stored for future use.
    • Saved configurations are used to verify diagnostics and that the devices are in their expected configuration before shots.
  • Reconfiguration occurs during alignment and tweaking diagnostics to ensure the environment is optimal for shots. 
    • There is no substantial time restriction for devices reaching their setpoint
  • NIF has an Oracle database that is used to maintain setpoints and configurations. 
    • Other systems have configuration files that live on local controllers.
  • Bulk of code is at the device and controller layer such as saving, storing, and doing. 
  • Setpoint checks are different than alarm thresholds. 

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. SLAC will provide existing presentation(s) on it to give a high-level description on what we plan to use it for/it's planned capabilities. Robert S. Tang-Kong 


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). Ken Lauer 
      • Will also check out other facilities. 

Action items:

  • Robert S. Tang-Kong Accumulate existing ATEF presentations and documentation so we can share with LLNL and LLE. 
  • Ken Lauer Check in with other facilities using EPICS on how they manage configurations. AD may be doing things we're interested in.
  • Mitchell Cabral Set up WG pt.2. Include LLE.




  • No labels