Versions Compared

Key

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

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:

Task report
pages363433955
pageSize10

Topics:

Excerpt
Jana B. Thayer Christopher O'Grady Peregrine McGehee Nate Landis Jason Bender Laser System DAQ Requirements Spreadsheet

 

Approx. Time

Agenda ItemLinksNotes
Begin collecting laser system DAQ requirements. 

30 mins

DR Prep - Kickoff SlidesDR Kickoff Slides ; DR Agenda
  • Everyone was in the earlier DR so we recapped briefly and reached for questions.
  • Looked through the review template slides.
    • Traci will upload all cost and schedule portions for everyone, but still review what's entered. 
  • Laydown date is tbd, but most likely will occur Wed. October 4th. Ji is reaching out to schedule. 
  • Alex and Barry have icalepcs conflicts for Dry Runs (10/9-10/13), so we will need to decide how to proceed with this conflict. 
  • Plenaries will drive breakouts, but for the laydown, we can still start slides earlier.
  • Breakout laydowns should have, at a minimum, the slides and a declarative sentence to describe what will be included. 
    • ~50%

10 mins

Review of Laser System Risks added to Risk Board.https://app.smartsheet.com/b/publish?EQBCT=173ec6bd4bb5413aa3cbb8ac687159f9

Minutes:

This was addressed in an earlier meeting. We did not cover this topic.

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.


  • 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


 

  • 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

-

 

  • 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-

...