Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Attendees: Jasmine, Nguyen Mitchell Cabral Jing Yin Barry Fishler Vinod Gopalan Jessica Jimenez 

Action Items:

Task report
pages244915963

Topics:

RequestorAgenda Item
-Revisit trailing action items.
-Questions for SharePoint/Confluence access.
LLNLSLAC naming convention for laser diagnostics and control devices in the beam path.
LLNLSLAC software quality assurance plan.
LLNLSLAC GUI standards.
SLACLLNL high-level ICD update.
SLACLLNL C++ standards.
-Next meeting topics

Minutes:

*These documents are from 2019, so information may be dated. Will need to confirm with SLAC laser SME to ensure most up-to-date naming conventions. 

  • Software Quality Assurance Plan:

...

  • Vinod Gopalan Wants to understand if SLAC has a common interface/API across all devices to configure, see status, view/change setpoints, etc. 
  • Vinod Gopalan SLAC Coding Standards/Guidelines.

Minutes:

Action Items:

    • LLNL developing their own SQAP and will provide to SLAC for review further down the road.
    • Previous meeting covered more specific questions related to this topic.
      • This meeting was held offline from reoccurring meeting. Please see the linked meeting notes for more detailed information.

  • SLAC GUI standards 

    • Currently no SLAC standards for GUI accessibility. 
    • MEC hutch at SLAC has developed some sample color files but it is still a work in progress. The plan, for now, is to create a set of GUI standards from this development for all hutches with class 4 laser experiments at SLAC (specifically for DBY, ML1, and DBD laser modes).
  • LLNL high-level ICD update

    • LLNL ICD is at ~85% completion and will be sent out for review this week.
  • LLNL C++ coding standards

    • Currently scoping out which set of standards would be best to send to SLAC. Revisit further down the line. 
  • SLAC IT Supply Vendor

    • SLAC may be able to provide some SLAC servers for LLNL testing.
      • Will need to contact Omar and LLNL IT to review IT/security requirements.  
    • This topics falls under the testing environment plan that will need further discussion.
      • For example, when testing the front end table, LLNL will need SLAC timing signal.
        • How will we simulate or provide this signal for LLNL testing?
  • Future meeting topics: 

    • Follow up with Alex on trailing action items.
      • Jama vacuum and motion requirements review.
    • Laser device nomenclature follow-up.
    • Testing environment plan.
      • SLAC servers for factory acceptance testing at LLNL.
      • Timing Tyler Johnson .
      • Requires Tyler and Alex's availability.
    • Logging framework in EPICS (for debugging, console, syslog)**
    • User privileges for EPICS**

** These agenda items will move to an email correspondence per Ken Lauer 's request. If further discussion is needed, then will move these topics to a meeting setting with Ken.  

Action Items:

  •  Barry Fishler To send LLNL high-level interface document out for review.
  •   Mitchell Cabral To sequester Tyler Johnson for next week's meeting to discuss laser and timing involvement in testing environment plan and laser device nomenclature.