April 8, 2020 online meeting minutes: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
* Valery: physics motivation for DAQ/Trigger upgrade | * Valery: physics motivation for DAQ/Trigger upgrade | ||
Valery presented event rates for electron and muon triggers for different experiments, results summarized in []; in general, for double luminosity we can expect reasonable rates below 50kHz; on next meeting Valery will present situation with mesonX triggers which is expected to be higher and less predictable then electron and muon triggers. | |||
Our suggestions in the final report will be based on the worst case event/data rate predictions. Short term and long term plans will be presented, in line with high-lumi task force. | |||
have | Preliminary, following improvements will be needed in FPGA-based L1 trigger: (1) need more clusters in EC for muon trigger (not only max energy electron but also low energy MIP-like for muon); (2) q**2 cut improvement needs better dc roads resolution; (3) need more then one particle in one sector, may do it by counting of the number of the PCALU hits coincided with DC roads; (4) daq reliability issues appeared above 30kHz event rate have to be resolved. | ||
* | * Ben/Sergey: VTP-based streaming front-end in final stage of development, fixing remaining issues, Ben will work this and next week to resolve TCP problem in VTP; VTP-based solution will be included into final report as ready-to-go short term solution; long term may require no-VXS anyway; we keep in mind 100k event rate limit for L1-based daq; new design electronics have to be compatible with streaming day even if built to be used with L1-based system | ||
In close future, we want to have complete FADC250/VTP-based streaming front-end to let back-end and data processing development. As back-end progresses, we will add another electronics into streaming setups (DCRB, VSCM, etc). | |||
* Gagik/Nathan: realtime data processing in current daq L3, and in streaming daq (existing offline algorithms, new IA approach etc) - next time | |||
* Sergey: existing L1 algorithms reuse in L3 | * Sergey: existing L1 algorithms reuse in L3 | ||
Sergey was planing to modify L1 algorithms for not-FPGA processing, but maybe existing L1 improvements (as it discussed above) will be more needed, it will be discussed. | |||
* Rafo assignments | * Rafo assignments - was not discussed today | ||
Latest revision as of 11:26, 8 April 2020
present: Sergey Boyarinov, Ben, Pasyuk, Graham, Valery, Nathan, Rafo, Vardan, Stepan
1. Streaming DAQ/Trigger task force progress
- Valery: physics motivation for DAQ/Trigger upgrade
Valery presented event rates for electron and muon triggers for different experiments, results summarized in []; in general, for double luminosity we can expect reasonable rates below 50kHz; on next meeting Valery will present situation with mesonX triggers which is expected to be higher and less predictable then electron and muon triggers.
Our suggestions in the final report will be based on the worst case event/data rate predictions. Short term and long term plans will be presented, in line with high-lumi task force.
Preliminary, following improvements will be needed in FPGA-based L1 trigger: (1) need more clusters in EC for muon trigger (not only max energy electron but also low energy MIP-like for muon); (2) q**2 cut improvement needs better dc roads resolution; (3) need more then one particle in one sector, may do it by counting of the number of the PCALU hits coincided with DC roads; (4) daq reliability issues appeared above 30kHz event rate have to be resolved.
- Ben/Sergey: VTP-based streaming front-end in final stage of development, fixing remaining issues, Ben will work this and next week to resolve TCP problem in VTP; VTP-based solution will be included into final report as ready-to-go short term solution; long term may require no-VXS anyway; we keep in mind 100k event rate limit for L1-based daq; new design electronics have to be compatible with streaming day even if built to be used with L1-based system
In close future, we want to have complete FADC250/VTP-based streaming front-end to let back-end and data processing development. As back-end progresses, we will add another electronics into streaming setups (DCRB, VSCM, etc).
- Gagik/Nathan: realtime data processing in current daq L3, and in streaming daq (existing offline algorithms, new IA approach etc) - next time
- Sergey: existing L1 algorithms reuse in L3
Sergey was planing to modify L1 algorithms for not-FPGA processing, but maybe existing L1 improvements (as it discussed above) will be more needed, it will be discussed.
- Rafo assignments - was not discussed today