Add the ability to configure the enqueue timeouts in AggregatorCore
We've seen issues in the DUNE 35-ton where the online monitoring code occasionally takes a long time processing its data and the enqueuing of the subrun event times out based on the currently hard-coded timeout value of 5 seconds.
It would be nice for this, and other enqueue timeouts, in AggregatorCode to be configurable.
It's not clear to me at the moment, though, whether one timeout value for all of the enqueue operations is sufficient, or whether we should have a couple. We can talk about this more.
#1 Updated by John Freeman over 3 years ago
- Status changed from New to Resolved
With commit e1cb98c0651d7e682cd49bda26fa032321350465 on artdaq's develop branch, users have the option of setting the "enq_timeout" variable in FHiCL; if they don't, it defaults to its previous hardwired value of 5 seconds.