Skip to content

Enlarge BCT timout because of parasitic events

Matteo Ferrari requested to merge fix-parasitic into master

This change fixes https://its.cern.ch/jira/browse/NTOFNEWDAQ-780 but it need some discussion. Is it safe?

From the logs, the parasitic events arrives about 900ms later as you can see here:

ott 20 18:09:27 ntofproxy-1 BCTReader[3014]: 2021-10-20 18:09:27,818 INFO [default] Waiting for bct cycleStamp:1634746167100000000
ott 20 18:09:28 ntofproxy-1 BCTReader[3014]: 2021-10-20 18:09:28,419 ERROR [default] [EventReader]: no event found for 1634746167100000000 buffered:0
ott 20 18:09:28 ntofproxy-1 BCTReader[3014]: 2021-10-20 18:09:28,419 INFO [default] Waiting for event...
ott 20 18:09:28 ntofproxy-1 BCTReader[3014]: 2021-10-20 18:09:28,702 VERBOSE-1 [default] [DIMDataTimedBuffer]: event received timeStamp:1634746167100000000

Maybe this is why originally was done with a conditional wait? (https://gitlab.cern.ch/ntof/daq/bctreader/-/blob/ffffc61ea6802a9b833cab8a68be1af443b78385/src/BCTDevice.cpp#L52)

Edited by Matteo Ferrari

Merge request reports