Attendees: Ken Lauer Vinod Gopalan Barry Fishler Alex Wallace Peregrine McGehee Zachary L Lentz Mitchell Cabral Nate Landis Robert S. Tang-Kong 

  • In NIF there is a startup configuration 
    • Active setpoint. Constantly changes. 
  • What are the qualities that we want in these setpoints:
    • Named sets of configurations
    • Need to know if the readbacks match up
      • Q: What is the threshold of comparison between the readback and setpoint?
    • List of PVs and their values
    • Q: Does autosave and restore really need to be apart of this tool?
      • Maybe not
    • Most of HE-LP laser device react quickly, but do not require time critical moves.  
      • They do have time critical items for stopping a shot (This item is more of an MPS topic). 
        • Same for RRL.
  • Storing data: We have not settled on database/configuration store.
  • SCORE: 
    • Article regarding score
    • LCLS implementation of SCORE
    • Java application with relation database (probably Oracle)
    • Elements in tool:
      • Setpoints names (PVs, not groups of elements). 
      • Values
      • Readback Values
    • SCORE is not something that LCLS wants to use because it's so different from what we currently have. Ken proposes we move this behind us. 
    • Ken's understanding that the SCORE application is an apply and verify. 
  • Pheobus: Save-And-Restore
    • Takes snapshots of predefined list of PVs at a certain point in time and writes them back. 
    • May support Oracle.
    • Ken's opinion it is the most advance.
    • ECS tend to move away from control studio so we don't use Pheobus.
  • PyDM:
    • Are we putting configuration tool at this GUI layer
      • Up for discussion
  • We should capture and record the functionality and requirements in the system in Jama. 


  • No labels