System behaving unexpectedly when there are no triggers
A message from Roland Sipos on the protoDUNE DAQ Slack channel:
I was running on Partition2, without enabling any triggers. After 10 minutes, the BoardReader's trigger matching mechanism activated, meaning that I receive trigger requests on our ZMQ connection out configuration in np04_WibsFake_Ssps00010. I don't think, this is the expected thing
I'm not sure that I fully understand what Roland is describing, and I haven't taken time to look at the log files, but I wanted to capture this trouble report for later follow-up.
#1 Updated by Kurt Biery about 1 year ago
This may not be related to artdaq.
It may be caused by partition cross-talk in the ZeroMQ trigger messages sent out by the Timing FragGen.
It sounds like there have been changes in Run Control and DAQInterface to help prevent cross-talk between partitions in this area.