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
Description
Due date
Assignee
Task appears on
Require concept for toggling power on/off to small motors (CosyLab contacted)
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.