Project

General

Profile

Bug #23045

Confusing error from event builder when too many fragments are returned

Added by Philip Rodrigues about 2 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
08/02/2019
Due date:
% Done:

0%

Estimated time:
Experiment:
DUNE
Co-Assignees:
Duration:

Description

Running on ProtoDUNE SP with artdaq version v2019_07_17_protoDFO_pduneHacks, I inadvertently set generated_fragments_per_event in one of the fragment generators to 1 when it should have been 2. There are 10 instances of this board reader in my configuration.

The event builders timed out waiting for the correct number of fragments for each event, and printed the following slightly confusing message:

Active event 87 is stale. Scheduling release of incomplete event (missing 18446744073709551606 Fragments) to art

After a while, I realised that 18446744073709551606 is -10 interpreted as a uint64_t, but it would be nice to have the error message indicate a bit more clearly what has gone wrong.



Also available in: Atom PDF