Attendees:

Mitchell Cabral Gregory Brent Omar Quijano Peregrine McGehee Terzi, Ken Jason Bender Nate Landis Govednik, Janez Jasmine, Nguyen Janos Vamosi Jessica Jimenez Vinod Gopalan 

Action Items:

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

Topics:


Agenda Item

Terzi, Ken Omar Quijano 

IT Infrastructure

Mitchell Cabral 

Naming Convention Documentation Update

Jama Requirements

Minutes:

LLNL IT:

  • Omar thinks the topology and layout looks good, but is curious about LLNL throughput requirements. 
  • SLAC's infrastructure is quite scalable so the throughput is not too much of a concern, but it still is good to know.
  • Currently, SLAC has most things at 100Gb but are trying to establish 200Gb.
  • IT hardware is not too critical as it will have minimal to no effect on how SLAC interfaces with them. 
    • SLAC uses Ruckus servers downstream of the Cisco servers.
      • Looking at various vendors to possibly replace Ruckus
  • Terzi, Ken to share presentation information for Omar's reference.  
  • Omar Quijano is working on documentation for SLAC IT Infrastructure/designs including resiliency. 
  • Peregrine McGehee mentioned that laser timing is listening to EVR. Both short pulse and long pulse are running off of facility timing. 

Action Items:

  • 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.
  • Omar Quijano To work on documenting SLAC's IT infrastructure design including hardware specs and key information.





  • No labels