View source for ERSAP Meeting Feb. 4, 2021

=== Connection Info: ===
This meeting scheduled via Zoom. Join link should be in your calendar.


<!------------------------------------------------------------------------------------------------------------>

=== Agenda: ===
# Announcements
# Streaming readout and streaming data processing design requirements
# TriDAS and ERSAP integration possible scenarios
# ERSAP-TriDAS template project proposal
# AOT

==== Useful References ====
<small>
* [https://jeffersonlab.sharepoint.com/:w:/s/SciComp/EQxPpI6h8VRFtlSKLHeLWusBYCOQUySVpEBKCIlR09u5wA?email=davidl%40jlab.org&e=NCC22f ERSAP Document]
* [https://jeffersonlab.sharepoint.com/:b:/r/sites/SciComp/Shared%20Documents/EPSCI/SRO/Streaming/20191217%20Streaming%20Paper/20200302%20JLab%20Streaming%20Readout.pdf?csf=1&e=kDX7yr Graham's Paper describing SRO]
</small>

<hr>

=== Minutes: ===



Attendees: Tommaso C., Carmelo P., Benjamin R., Sergey B., David A., Carl T., Chris L., Vardan G.

#* Announcements
#** We all agree to go with biweekly meeting format, scheduled every other Thursday at 9AM Eastern Time (US and Canada).
#* Streaming readout and streaming data processing design requirements 
#** An e-mail exchange between Carmelo and Vardan was mentioned, where they discussed possibility to deploy and operate HM and TCPU in a single run-time, thus preparing it to function as a component within the ERSAP ecosystem.
#** We discussed known back-end processing systems, namely batch processing, stream processing and micro-batch processing. 
#** Lengthy discussion on the data handling requirements. Questions such as: Can we write/store data efficiently? Can we correlate streams and build events fast enough not to introduce blind spots in the stream? 
#** Partial event building and processing with possible data reduction in a sub-detector streams was also discussed. This might be useful to achieve data transfer optimizations, as well as optimize a resource utilization.
#* TriDAS and ERSAP integration possible scenarios
#** The decision was made to perform tests and benchmark measurements for TriDAS and ERSAP components on a more controlled testing environments (e.g. Hall-B and Indra lab VTP setups), where we can configure data streams, and measure parameters, such as event/data and lost-frame rates. 
#** Later optimized components with their suggested compositions (e.g. HM, TCPU, or HM+TCPU, etc.) will be integrated into the ERSAP.
#* ERSAP-TriDAS template project proposal
#** Vardan mentioned a new project that he started for the TriDAS integration (here is the git repository for the [https://github.com/JeffersonLab/ersap-tridas.git project]). Work is still in progress, and will be discussed in more details during the upcoming meetings. 
Vardan presented [https://userweb.jlab.org/~gurjyan/presentations/ersap_02.04.pptx slides] that was used during the discussion.