February 20, 2019 online meeting minutes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
present: Sergey, vpk, Ben, Nathan, Eugene | present: Sergey, vpk, Ben, Nathan, Eugene, Stepan | ||
Line 15: | Line 15: | ||
* muon (opposite sectors) counts too much, Emax limit on ECAL and PCAL clusters was removed because of suspected inefficiency | * muon (opposite sectors) counts too much, Emax limit on ECAL and PCAL clusters was removed because of suspected inefficiency | ||
* ww have to try to increase beam current from 35nA to 50nA if possible, will try today and then decide on trigger settings, maybe put pack Emax cut at least for ECAL, we may loose 5% or event 10% in worst case | |||
* rg-a starts March 19, trigger will have FT in additional to rg-b trigger logic, the rest (electron and muon) will stay the same; will try high beam current as well (60-65nA) | |||
* in general, we exhausted all trigger improvement options which can be done in reasonable time (days/week), will work to improve daq performance | |||
Latest revision as of 11:00, 20 February 2019
present: Sergey, vpk, Ben, Nathan, Eugene, Stepan
1. Status of trigger changes for rg-b and future plans
- HTCC new version works, waiting on stage1 readout confirmation; if works will change all other stage1 readout the same way as HTCC/CTOF
- segment finder now sorting segment candidates keeping segment with biggest number of hits, it allows much more precise road finding
- new roads were generated using different methods (fast mc, data-based, gems-based) by Raffaella, Silvia and Yordanka) starting from 1GeV electrons, using it in rg-b
- geo match road vs pcal cluster(U only) was implemented
- electron trigger for rg-b is 50% good events, it is good enough
- muon (opposite sectors) counts too much, Emax limit on ECAL and PCAL clusters was removed because of suspected inefficiency
- ww have to try to increase beam current from 35nA to 50nA if possible, will try today and then decide on trigger settings, maybe put pack Emax cut at least for ECAL, we may loose 5% or event 10% in worst case
- rg-a starts March 19, trigger will have FT in additional to rg-b trigger logic, the rest (electron and muon) will stay the same; will try high beam current as well (60-65nA)
- in general, we exhausted all trigger improvement options which can be done in reasonable time (days/week), will work to improve daq performance
2. DAQ problems observed with 50kHz event rate run
- DCRB 'Missing slots" error, Ben will look at possible problems
- tdcftof* etc - "TI event longer then 7 words"
- looks like problems were enforced by backend-induced dead time; suspect that buffer not large enough; in next downtime (or whenever appropriate) we'll try to reproduce it, probably mid April after rg-a, unless rg-a will go for high event rate