Project

General

Profile

Bug #24053

Nonsending boardreader FHiCL broken

Added by John Freeman about 2 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/13/2020
Due date:
% Done:

100%

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

Description

In $ARTDAQ_DAQINTERFACE_DIR/simple_test_config/subconfigs, there are FHiCL documents meant to configure ToySimulators which don't send fragments. They contain the line:

generated_fragments_per_event: 0

...which is how to communicate to DAQInterface that it should expect a number of fragments other that "1" per event from a boardreader.

It also used to be the case that setting this parameter would actually cause artdaq-demo's ToySimulator to send as many fragments as were specified. However, with artdaq-demo commit 9de984abba56e0b80e72717783dc811f0bc47cd0 from November 30, 2018, this no longer appears to be the case. The nonsending boardreader FHiCL documents should be changed accordingly.

Associated revisions

Revision 9a0f0afe (diff)
Added by John Freeman about 2 months ago

JCF: Issue #24053: Fix the FHiCL for the nonsending boardreaders

History

#1 Updated by John Freeman about 2 months ago

  • % Done changed from 0 to 100
  • Status changed from New to Resolved

Resolved with commit 9a0f0afe32f3c6baf7680dcb435a56fa842a1621 on feature/issue24053_nonsending_boardreaders. The change is quite simple; since ToySimulator no longer uses generated_fragments_per_event to determine how many fragments to send but instead uses the fragment_ids list, I've added "fragment_ids: []" to the FHiCL.

In order to test this, before launching DAQInterface but after setting up the DAQInterface environment you'll want to set

export DAQINTERFACE_KNOWN_BOARDREADERS_LIST=$ARTDAQ_DAQINTERFACE_DIR/simple_test_config/subconfigs/known_boardreaders_list_example.mu2edaq

and then you'll want to make sure that "subconfigs/component_special" is part of your subconfig list (see Issue #21226 for more on subconfig lists). E.g., I ran
just_do_it.sh ./boot.txt 0 --config "subconfigs/component_nonsending subconfigs/component_push subconfigs/component_special subconfigs/dataloggers subconfigs/dispatchers subconfigs/eventbuilders subconfigs/metrics_disabled subconfigs/routingmaster_disabled" --comps "component01 component02 component03 component04 component05 component06 component2001 component2002 component2003"

Also available in: Atom PDF