Difference between revisions of "EPSCI SRO Meeting Nov. 8 2021"
| (3 intermediate revisions by the same user not shown) | |||
| Line 32: | Line 32: | ||
=== Agenda: === | === Agenda: === | ||
| − | |||
# Announcements | # Announcements | ||
#* The 9th Streaming Readout workshop held from December 8 - 10 will be hosted by ORNL (https://indico.phy.ornl.gov/e/SRO_workshop_9). | #* The 9th Streaming Readout workshop held from December 8 - 10 will be hosted by ORNL (https://indico.phy.ornl.gov/e/SRO_workshop_9). | ||
| Line 71: | Line 70: | ||
=== Minutes: === | === Minutes: === | ||
| + | Attendees: David L., David A., Carl T., Mike G., Jie C., Vardan G. | ||
| + | |||
| + | • Ben is working on the VTP firmware that will combine functions of the triggered and streaming DAQ. Updating of the VTP firmware to switch between two modes of data acquisition will not be required. So, in a new CODA the VTP will become so called “hardware ROC”, and will require control and monitoring by the CODA run-control system. | ||
| + | |||
| + | • David A. led the discussion for the streaming CODA state machine. We discussed differences between current CODA state machine. It was agreed that first we need to define states and state-transitions for the streaming CODA before we will decide if AFECS can be adopted to configure and control streaming DAQ. It was mentioned that COOL language will most likely be used to described the new state machine. | ||
| + | |||
| + | • We also discussed the role of the ET system in a way to inject user events into a data stream. Since data stream quantum is defined by its time stamp, a user event injected into the data stream must have a time stamp. In order to prevent time-stamp discrepancies the user will not provide a time for the event, allowing streaming DAQ systems to deliver it. For that a dedicated component in the streaming pipeline will be responsible to provide a UNIX time for all user events. | ||
| + | |||
| + | • Reports on the current statuses for the ERSAP framework development, as well as the ERSAP based data processing pipelines on multiple test setups were presented. | ||
Latest revision as of 16:00, 9 November 2021
Connection Info:
The meeting time is 2:00pm.
You can connect using BlueJeans Video conferencing (ID: 680 566 960). (Click "Expand" to the right for details -->):
Meeting URL https://bluejeans.com/680566960?src=join_info
Meeting ID 680 566 960
Want to dial in from a phone?
Dial one of the following numbers: +1.888.240.2560 (US Toll Free) (see all numbers - https://www.bluejeans.com/premium-numbers)
Enter the meeting ID and passcode followed by #
Connecting from a room system? Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode
Agenda:
- Announcements
- The 9th Streaming Readout workshop held from December 8 - 10 will be hosted by ORNL (https://indico.phy.ornl.gov/e/SRO_workshop_9).
- CERN EP RD day (November 11-12). Dedicated session on EIC and talks on EIC DAQ/chips (https://indico.cern.ch/event/1063927/).
- Streaming CODA
- Streaming EMU
- VTP firmware
- Streaming CODA state machine and the role of the AFECS
- Configuration and the role of the JCEdit
- Monitoring
- ERSAP stream unit level workflow manager as a streaming CODA run-control
- The role of the ET in the streaming CODA
- Standard data transport. Use of the common transport for both DAQ and data-processing.
- Standard data format used for entire data pipeline
- ERSAP framework development
- C++ binding
- Data lake as an ERSAP engine
- ERSAP prototype applications
- INDRA VTP setup
- INDRA SAMPA setup
- Hall-D calorimeter prototype SRO
- ERSAP TriDAS integration
- Hall-B upcoming beam tests
- AOT
Useful References
- SRO Meetings
- CLAS12 SRO page
- ERSAP Document
- Vardan's WMS draft
- Vardan's SRO sketch
- Graham's Paper describing SRO
- Dave Abbott's slides on data format
Minutes:
Attendees: David L., David A., Carl T., Mike G., Jie C., Vardan G.
• Ben is working on the VTP firmware that will combine functions of the triggered and streaming DAQ. Updating of the VTP firmware to switch between two modes of data acquisition will not be required. So, in a new CODA the VTP will become so called “hardware ROC”, and will require control and monitoring by the CODA run-control system.
• David A. led the discussion for the streaming CODA state machine. We discussed differences between current CODA state machine. It was agreed that first we need to define states and state-transitions for the streaming CODA before we will decide if AFECS can be adopted to configure and control streaming DAQ. It was mentioned that COOL language will most likely be used to described the new state machine.
• We also discussed the role of the ET system in a way to inject user events into a data stream. Since data stream quantum is defined by its time stamp, a user event injected into the data stream must have a time stamp. In order to prevent time-stamp discrepancies the user will not provide a time for the event, allowing streaming DAQ systems to deliver it. For that a dedicated component in the streaming pipeline will be responsible to provide a UNIX time for all user events.
• Reports on the current statuses for the ERSAP framework development, as well as the ERSAP based data processing pipelines on multiple test setups were presented.