You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Date

Discussion Items

  • Collect walk-ins
  • EPICS focus discussion
    • What kinds of things do you want to know?
    • LCLS is slated to deliver a control system seminar on EPICS in a few months.
  • LCLS controls roadmap
  • Review and collectively understand the MEC-U operations vision/story and subsequently the requirements for the control systems
    • For next time, I'd like each of us to pick something we think is important, critical, or should be a thing to focus on about the control system to share in this meeting.
      • Consider your experience in building control systems, and what you think needs to be a focus in MEC-U. 
      • These are all roughly paraphrased:
      • Kenneth Terzi
        • paraphrase: Interface designs, standards for how to design controls for new components for SLAC in the RRL
        • making sure the designs are extensible
      • Vinod Gopalan
        • how does python perform in our production environments
      • Jing Yin
        • building for long term support, maintainability
      • Barry Fishler
        • need to develop the conops to really make the functional requirements
      • Jessica Jimenez
        • agree with the conops, need to make sure the conops is 
      • Alex Wallace
        • test driven development, 
      • Jason Bender
        • interface definition between all the three control systems
          • "if I am working on the vacuum system, where should I interface with other vacuum systems? which layer of the stack?"
        • Data collection for the control system and science daq
      • Jana Thayer
        • Clean and clear interfaces, robustness and maintainability.
        • A good interface also provides a way to trace problems more accurately.
      • Robert Plummer
        • early conops definition → frs → arch specification
        • picking hardware that long-term-support

Action items


Past meeting AI

DescriptionDue dateAssigneeTask appears on
  • Require concept for toggling power on/off to small motors (CosyLab contacted)
 MEC-U Collective Team Meetings
  • Seeking existing SLAC solution for closed loop pointing stability loop (vision/motor)
 MEC-U Collective Team Meetings
  • Require concept for toggling power on/off to GigE cameras (CosyLab contacted)
 MEC-U Collective Team Meetings
Eric M GaltierNotes on Experimental Diagnostics
  • Omar Quijano To work on documenting SLAC's IT infrastructure design including hardware specs and key information.
 Omar Quijano2023-02-21 MEC-U Project Controls and Data Systems Team Meetings
  • Terzi, Ken To adjust some items on the presentation then send out to the group and Omar. Mitchell Cabral Will upload this to the Sharepoint.
 Terzi, Ken2023-02-21 MEC-U Project Controls and Data Systems Team Meetings
Barry FishlerSet Point API WG pt.2
  • Jing Yin TPR Card Specification Stub (Specific question from Ken: Number of outputs for TTL? LVTTL or TTL? Both?)
 Jing Yin2023-02-07 MEC-U Project Controls and Data Systems Team Meetings
  • General ICD, Jama - High Priority
 2022-11-16 Meeting notes
  • Jira Tickets for MECU
 2022-11-16 Meeting notes
  • Capture Discussion
 2022-11-16 Meeting notes
  • Create Resource Allocation
 2022-11-16 Meeting notes
Tyler Johnson2022-11-14 MEC-U Project Controls and Data Systems Team Meetings
  • SLAC to provide GUI standards for laser systems (standards in development.). Follow up. Mitchell Cabral 
 Mitchell Cabral2022-11-03 MECU LLNL/SLAC Meeting
  • LLNL to share C++ standards for SLAC review. Follow up. Vinod Gopalan
 Vinod Gopalan2022-11-03 MECU LLNL/SLAC Meeting
  • AD, how ACR operates the machine using high-level applications (Matlab and Python), Alex Wallace ping Greg White, et al for someone to talk to the collective about it.
 Alex Wallace2022-4-5 MEC-U Project Controls and Data Systems Team Meeting

  • No labels