Difference between revisions of "EPSCI SRO Meeting Jul. 12, 2021"

From epsciwiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 58: Line 58:
  
 
=== Minutes: ===
 
=== Minutes: ===
 +
Attendees: David L., Carl T., Mike G., David A., Jie C., Chris L., Vardan G.
 +
 +
* ersap-java project alpha release is scheduled on 07.19.21
 +
* ersap-cpp project development is started.
 +
* First attempt to integrate JANA based (c++) engine within the ERSAP application. Facing a few issues due to the fact that ersap-cpp project is still in active development stage.
 +
* Presented the list of ERSAP related active projects.
 +
* Chris L. mentions that data-lake project source code is available, so we can start developing data-lake engine.
 +
* Chris L. brought up to our attention the importance of having lab-wide maven repository. This will encourage collaboration (package sharing) and will prevent unnecessary software installations.
 +
* David A. suggested to present ERSAP VTP receiver and aggregator engines as a CODA DC component. This component will play the role of the stream access point (or stream source) for the  ERSAP real-time stream processing back-end. Possible back-end processor engines that can be used during the DESY beam test are:
 +
** Software trigger
 +
** Histogram
 +
* We will start developing the  suggested ERSAP data-pipeline services, as well as CODA DC component to be ready for upcoming beam tests.
 +
* EVIO 6 is expected to be streaming DAQ, as well as streaming data processing data format.
 +
* Discussed TriDAS group development and testing activities.
 +
* SAMPA DAS and DSP mode decoder engines development is in progress (Carl T.).

Latest revision as of 20:49, 12 July 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:

  1. Previous Meeting
  2. Announcements
  3. ERSAP development
    • TriDAS ERSAP integration
    • ERSAP active projects and their stats
    • INDRA VTP setup
      • TriDAS group request
    • INDRA SAMPA setup
      • DSP and DAS mode decoder engines
  4. VTP Data Format
  5. AOT

Useful References


Minutes:

Attendees: David L., Carl T., Mike G., David A., Jie C., Chris L., Vardan G.

  • ersap-java project alpha release is scheduled on 07.19.21
  • ersap-cpp project development is started.
  • First attempt to integrate JANA based (c++) engine within the ERSAP application. Facing a few issues due to the fact that ersap-cpp project is still in active development stage.
  • Presented the list of ERSAP related active projects.
  • Chris L. mentions that data-lake project source code is available, so we can start developing data-lake engine.
  • Chris L. brought up to our attention the importance of having lab-wide maven repository. This will encourage collaboration (package sharing) and will prevent unnecessary software installations.
  • David A. suggested to present ERSAP VTP receiver and aggregator engines as a CODA DC component. This component will play the role of the stream access point (or stream source) for the ERSAP real-time stream processing back-end. Possible back-end processor engines that can be used during the DESY beam test are:
    • Software trigger
    • Histogram
  • We will start developing the suggested ERSAP data-pipeline services, as well as CODA DC component to be ready for upcoming beam tests.
  • EVIO 6 is expected to be streaming DAQ, as well as streaming data processing data format.
  • Discussed TriDAS group development and testing activities.
  • SAMPA DAS and DSP mode decoder engines development is in progress (Carl T.).