April 1, 2020 online meeting minutes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
1. Streaming DAQ/Trigger: L3 implementation | 1. Streaming DAQ/Trigger: L3 implementation | ||
* we had useful discussion on offline reconstruction usage in L3 and streaming project; Sergey suggested to start implementing offline reconstruction code into L3 right now and get some results/experience before writing Taskforce | * we had useful discussion on offline reconstruction usage in L3 and streaming project; Sergey suggested to start implementing offline reconstruction code into L3 right now and get some results/experience before writing Taskforce report in July; Graham and Gagik pointed out that we do not have to do actual implementation as part of Taskforce, only prepare recommendations and plan; we agree that Gagik and Nathan will prepare section describing how offline reconstruction (and new technologies like IA) can be implemented in both L3 and future streaming daq | ||
* Stepan pointed out that physics motivation is the important starting point for the DAQ/Trigger improving plans; Valery Kubarovsky is working on such requirements preparation | * Stepan pointed out that physics motivation is the important starting point for the DAQ/Trigger improving plans; Valery Kubarovsky is working on such requirements preparation | ||
| Line 15: | Line 15: | ||
* Ben and Sergey will continue to work to fix remaining VTP issues; goal is to make streaming VTP-based front-end solution completely ready | * Ben and Sergey will continue to work to fix remaining VTP issues; goal is to make streaming VTP-based front-end solution completely ready | ||
* DAQ in FT test setup (adcft1/adcft2 VTPs) is running and can be used for streaming back-end development for both TriDAS and new jlab framework | * DAQ in FT test setup (adcft1/adcft2 VTPs) is running and can be used for streaming back-end development for both TriDAS and new jlab framework, Sergey passed needed information to TriDAS team and Vardan, work in progress | ||
Latest revision as of 10:54, 1 April 2020
present: Sergey Boyarinov, Chris, Gagik, Nathan, Stepan, Graham, Rafo, Raffaella, Vardan, Ben
1. Streaming DAQ/Trigger: L3 implementation
- we had useful discussion on offline reconstruction usage in L3 and streaming project; Sergey suggested to start implementing offline reconstruction code into L3 right now and get some results/experience before writing Taskforce report in July; Graham and Gagik pointed out that we do not have to do actual implementation as part of Taskforce, only prepare recommendations and plan; we agree that Gagik and Nathan will prepare section describing how offline reconstruction (and new technologies like IA) can be implemented in both L3 and future streaming daq
- Stepan pointed out that physics motivation is the important starting point for the DAQ/Trigger improving plans; Valery Kubarovsky is working on such requirements preparation
- Sergey and others will look at existing L1 algorithms to see how they can be reused in L3 and streaming daq, keeping in mind physics requirements to improve events selection in forward calorimeter and drift chamber
2. Other related issues
- Ben and Sergey will continue to work to fix remaining VTP issues; goal is to make streaming VTP-based front-end solution completely ready
- DAQ in FT test setup (adcft1/adcft2 VTPs) is running and can be used for streaming back-end development for both TriDAS and new jlab framework, Sergey passed needed information to TriDAS team and Vardan, work in progress