SRO RTDP Oct. 24, 2023

From epsciwiki
Jump to navigation Jump to search

The current weekly meeting time is every other Monday at 10:00 US/Eastern

Connection Info:

You can connect using ZOOM Video conferencing (ID: 160 248 4178). (Click "Expand" to the right for details -->):

One tap mobile: US: +16692545252,,1602484178# or +16468287666,,1602484178#

Meeting URL: https://jlab-org.zoomgov.com/j/1602484178?pwd=UFViZUpyODYrZmsxdkVNbWZTMUR1Zz09&from=addon
Meeting ID: 160 248 4178
Passcode: 104412

Join by Telephone
For higher quality, dial a number based on your current location.
Dial: +1 669 254 5252 US (San Jose)
+1 646 828 7666 US (New York)
+1 646 964 1167 US (US Spanish Line)
+1 551 285 1373 US (New Jersey)
+1 669 216 1590 US (San Jose)
+1 415 449 4000 US (US Spanish Line)
833 568 8864 US Toll-free
Meeting ID: 160 248 4178
International numbers
Join from an H.323/SIP room system
H.323: 161.199.138.10 (US West)
161.199.136.10 (US East)
Meeting ID: 160 248 4178
Passcode: 104412

SIP: 1602484178@sip.zoomgov.com
Passcode: 104412

One tap mobile: US: +16692545252,,1601987443# or +16468287666,,1601987443#

Meeting URL: https://jlab-org.zoomgov.com/j/1601987443?pwd=bUVPV3puTHJPU0Fub2Q2Z1dsV0JjQT09&from=addon
Meeting ID: 160 198 7443
Passcode: 607906

Agenda:

  1. Previous Meeting
  2. Milestone Progress:
    • M01: Create prototype ERSAP configurations for INDRA and CLAS12 test systems (Ayan)
    • M02: Identify or capture SRO formatted data from CLAS12 and INDRA test systems with data tag/filtering capability (output data ready for further offline processing) (Discussion w/ Sergey)
    • M03: Evaluate existing solutions for configuring and launching remote distributed processes (Jeng, Cissie)
      Cissie and Jeng's Doc: MQTT, Ansible, Globus, SuperFacility and Fireworks
    • M04: Establish code repository(s), project site, and method of documentation (Jeng, Ayan)
  3. AOT



Minutes

Attendees: David L., Vardan G., Ayan R., Jeng T., Cissie M., Sergey B., Marco B., Fabio R.

  • M01: Create prototype ERSAP configurations for INDRA and CLAS12 test systems
    • Ayan is working on C++ "Hello World" for ERSAP
    • Following CLARA documentation since ERSAP has a lot of commonality with it
      • Single YAML file for configuration
      • Actor-specific config. parameters can be retrieved as JSON record
  • CLAS12 Data Capture Beam Test
    • Sergey noted that the schedule has shifted and the most likely pass change will now occur in mid-Dec.
      • We should look for short down times prior to the full capture exercise to test the system
      • Sergey noted that the firmware is reloaded at CODA Download time so it is not time consuming to switch firmware versions.
    • New network switch has shipped so will be here soon. Sergey will cable up as time allows over next few weeks.
    • Streaming should be available for:
      1. Forward Tagger
      2. Forward Carriage 2 Calorimeters (6 sectors)
      3. Forward Carriage TOF (6 sectors)
    • There will be a total of 18 VTP modules(crates), each producing 1-4 streams. (Some needing new fiber connections to new switch)
      • Each stream will write to a separate file so up to 4 files per VTP will be produced.
    • CLAS12 has total of ~70 crates.
      • Some are used for trigger system, scalers, or non-stream-capable TDCs
    • DC uses DCRB boards which could stream data with new firmware. This depends on Ben Raydo and his schedule.
  • Sergey mentioned that the new high speed 400Gbps network cards use a new technology/form factor for the transceiver (OSMP vs. QFMP). Two cards requiring these were delivered with the new computer in the Hall-B CH. The FPGA cards ordered with it will be delivered later.
  • M03: Evaluate existing solutions for configuring and launching remote distributed processes
    • Cissie presented results of a survey of potential tools for launching remote processes.
      • Several options were briefly discussed (MQTT, Ansible, Globus, SuperFacility and Fireworks(Jeng))
      • A [document containing the results of the survey was linked to the wiki for others to study.
  • M04: Establish code repository(s), project site, and method of documentation
    • Jeng reported setting up the SRO-RTDP Github Repository
    • A Docs directory was created to hold documentation in markdown format for now.
    • User-focused documentation will come a little later as the project matures


Action Items

  1. Understand how to retrieve ERSAP config. parameters from within actor - Ayan
  2. Ask Chris/Ben about schedule for SRO capable DCRB firmware - David
  3. Update test plan schedule to reflect new accelerator pass change schedule - Fabio
  4. Review [document on distributed process launching technologies - All