Difference between revisions of "SAMPA SRO"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | |||
− | |||
<div class="toccolours mw-collapsible mw-collapsed"> | <div class="toccolours mw-collapsible mw-collapsed"> | ||
− | |||
− | |||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
+ | === Project dependencies === | ||
# [https://github.com/JeffersonLab/ersap-java ersap-java] | # [https://github.com/JeffersonLab/ersap-java ersap-java] | ||
# [https://github.com/JeffersonLab/ersap-cpp ersap-cpp] | # [https://github.com/JeffersonLab/ersap-cpp ersap-cpp] |
Revision as of 19:34, 8 September 2021
Project dependencies
Installation
- Previous Meeting
- Announcements
- Abstract submission is open for CHEP 2022. Deadline is October 19th
- ERSAP prototype applications
- INDRA VTP setup
- Streaming Data Format
- The FPGA-based ROC for the VTP
- INDRA VTP setup
- INDRA SAMPA setup
- ERSAP SAMPA source engine (DAS data format)
- Endless stream of GBT frames
- Engine tests on the setup
- SAMPA data processing pipe composition and running within the ERSAP
- INDRA VTP setup
- AOT
Minutes:
Attendees: David L., Carl T., Mike G., Jie C., Vardan G.
- Announcements
- Abstract submission deadline for CHEP2022 is October 19th
- ERSAP
- Discussed active future ERSAP framework projects, such as ersap-cpp, ersap-orchestrator, ersap-python, ersap-ui.
- ERSAP prototypes
- INDRA VTP
- Discussed plans and actions implementing David's EVIO data format.
- Disconnect with the TriDAS group that decided to introduce a custom data representation based on the old VTP data format. David suggested to organize a re-sync meeting with the TriDAS group to discuss concerning issues.
- Ongoing effort to build a data processing pipeline to be tested at DESY
- INDRA SAMPA
- Carl completed SAMPA DAS decoder ERSAP engines development. Ready to be tested within the GEM detector data processing ERSAP data processing pipeline.
- INDRA VTP