Attendees: Alex Wallace Nate Landis Barry Fishler Jing Yin John Cline Randy Sanchez Jason Bender Peregrine McGehee Jasmine, Nguyen Christopher O'Grady Jana B. Thayer Govednik, Janez Ricardo Martinez Martinez Mitchell Cabral 

Action Items:

DescriptionDue dateAssigneeTask appears on
  • Meeting time may change to Thursday at 1pm if it satisfies everyone's schedules. Conflict arose for Bruce (New LLE team member for 10am on Thursday).
 2024-07-11 MEC-U Project Controls and Data Systems Team Meetings
  • 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
  • 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
  • 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
  • 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

Topics:

 

Approx. Time

Agenda ItemLinksNotes

Alex Wallace Nate Landis Barry Fishler Jing Yin 

30 mins

DR Prep - Kickoff Slides DR Prep Site ; DR Kickoff Slides ; DR Agenda ; Schedule Leading to DR
  • Everyone was in the earlier DR so we recapped briefly and reached for questions.
  • Looked through the review template slides and schedule leading to the DR.
    • Traci will add cost and schedule information. This should still be reviewed by presenters. 
  • Alex and Barry have icalepcs conflicts for Dry Runs (10/9-10/13), so we will need to decide how to proceed with this. 
  • Plenaries will drive breakouts, but for the laydown, we can still start slides earlier.
  • We agreed that laydowns should have, at a minimum, the slide tittles and a declarative sentence to describe what will be included. 
    • ~50%
  • We will review laydown slides in our next two meetings before the Laydown scheduled Wed. Oct. 4th.
  • Everyone, try and sit in on as many dry runs and lay downs as possible to get an idea on what's expected and learn from others. 

Jing Yin Barry Fishler Nate Landis Alex Wallace 

10 mins

Review of Laser System Risks added to Risk Board.https://app.smartsheet.com/b/publish?EQBCT=173ec6bd4bb5413aa3cbb8ac687159f9This was addressed in an earlier meeting. We did not cover this topic.

Jana B. Thayer Christopher O'Grady Peregrine McGehee Alex Wallace Barry Fishler Nate Landis Jason Bender Jing Yin 

20 mins

DAQ Discussions + IT Infrastructure Build for Laser Systems Requirements SheetIT Infrastructure Build Requirements Spreadsheet

Chris's Notes

advantages of daq:

  • correlated (timestamped) data-taking across devices
    • will probably be done in MEC-U laser system
  • (automated) live analysis
  • data management (movement, archiving)
  • MHz (10Hz MEC-U doesn't care)
  • integration with elog
  • handles larger data volumes


advantages of epics:

  • simpler (fewer failure modes)
    • shared devices (daq/controls) don't exist: simpler
    • doesn't require timestamping
  • more flexible (e.g. changing configurations)
  • easier to have multiple people work in parallel


NOTE: current hutches (TMO/RIX) use epics-approach for laser system, but do send some timestamped data to hutch-daq (e.g. with a wave8 digitizer).  so something of a hybrid solution.

  • DAQ does utilize LCLS-II timing which is the event timing system. 
  • LLNL's use of the DAQ will drive LLE. If LLNL system needs DAQ, then LLE will likely follow. 
  • Alex wants to think more on if LLNL will need DAQ or if EPICS Achiever+ could be used. 

Next Meeting

Date

Objectives


Alex Wallace Nate Landis Barry Fishler Jing Yin 

 

  • Check in on laydown slides.
  • Expectation to have slides created and at least some of the title slides inputted.  
Presentation Folder: SC-3 Controls and Data Systems

-

Jana B. Thayer Christopher O'Grady Peregrine McGehee Alex Wallace Barry Fishler Nate Landis Jason Bender Jing Yin 

 

  • Continue DAQ discussions.
  • If able, begin writing up some requirements on what the DAQ should provide to the laser systems. 
IT Infrastructure Build Requirements Spreadsheet-




  • No labels