Attendees: Alex Wallace Jing Yin Jessica Jimenez Terzi, Ken Vinod Gopalan Hill, Elizabeth Mitchell Cabral Gregory Brent Jason Bender Nate Landis,  Robert Plummer Tyler Johnson 

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

Topics:

Common TopicsAgenda Item
Key Takeaways from LLE Visit - CosyLab Support
-Testing Environments - Servers, timing, etc. 

MECU RRL Plan
SLAC TopicsAgenda Item
Laser Naming Convention Update
LLNL high-level ICD update.
-Jama - LLNL Requirements 
-LLE Requirements

Next meeting topics
Moved OfflineAgenda Item
-Syslog in EPICS
-User Privileges for EPICS

Minutes:

Testing Environment Plan:

  • What test environment can SLAC provide to LLNL/LLE.
  • Performance Testing in test environment. 
    • Can still functionally test interfaces, but should have real capable hardware and networking to support this.  

Timing:

  • A stand-alone RF signal can be used to simulate an input into the timing system (Clock input).
  • Large discussion on timing. LLNL and LLE would like to have a lower-level timing presentation from SLAC.
    • Previous timing presentation was given by Charlie, but was high-level.
    • Aiming in advance of LLNL CDR (beginning of January)  
      • Target timeline will be week of (Tyler, feel free to adjust this date).
      • Tyler Johnson is working on organizing this presentation with hardware timing team.



        Discussion Topics for this presentation:
        Event (Course) Timing (LLE/LLNL)
        • Overall easier and minimal hardware
        • ~8 nanosecond triggers
        • ~10+ picosecond jitters 
        • Delivered optically over fiber (TPR - Timing Pattern Receiver directly outputs trigger)
        • High Precision Timing (LLNL)
          • Locking laser to RF
          • Custom supporting hardware
          • ~1 nanosecond trigger*
          • ~10 femtosecond jitter*
            • *In principle, system is still in development
        • Interface between timing and various systems.
        • Wiring and signals required.



      • See resources below to links to SLAC Laser/Timing confluence pages. 

        Interface between laser system and timing system.

IT/Servers:

  • Omar to put together an IT supported device list for Barry
    • EPICS environment needs to run services such as logging system and achiever. 
    • SLAC may provide a rack for LLNL, but this is still being worked out.
      • Half a rack dedicated to the core.
      • For event timing systems, there are various small PCIE cards scattered around.
      • Precision timing system is ~half rack. 
        • For precision timing we may need to consider optical timing as well.

SLAC Laser Naming Convention:

Controls Requirements:

  • As we review requirements, we should think of who will be responsible and begin assigning roles.

LLNL: 

  • LLNL controls requirements inputted into Jama. 
  • Requirements are out to review for LLNL/SLAC.
  • Mitchell Cabral To ensure LLNL and LLE teams have Jama accounts/access.

LLE:

  • Still working on hardware list which will lead into system requirements. 
  • LLE will attempt to write requirements from a narrower view of the system. 

Resources:

Dated Resources

The following laser and timing resources are reflective of LCLS-I systems. LCLS-II upgrades are ongoing and not complete. Please view these sources with this information in mind. 

Action Items: 


  • No labels