Request for assistance in running the simple_subsystems sample configuration
With an artdaq v3_04_00 -based artdaq-demo system, I tried running the following command:
- sh ./run_demo.sh --config simple_subsystems --bootfile `pwd`/artdaq-utilities-daqinterface/simple_test_config/simple_subsystems/boot.txt --comps component01 component02 component03 --
The system was able to boot, but the following error was reported as the configurations were being prepared:
Obtaining FHiCL documents...done (0.1 seconds).
Bookkeeping the FHiCL documents...Traceback (most recent call last):
File "/home/biery/simpSubTest/artdaq-utilities-daqinterface/rc/control/daqinterface.py", line 1617, in do_config
File "/home/biery/simpSubTest/artdaq-utilities-daqinterface/rc/control/bookkeeping.py", line 184, in bookkeeping_for_fhicl_documents_artdaq_v3_base
expected_fragments_per_event[ss] = calculate_expected_fragments_per_event(ss, subsystem_fragment_count)
File "/home/biery/simpSubTest/artdaq-utilities-daqinterface/rc/control/bookkeeping.py", line 162, in calculate_expected_fragments_per_event
count += calculate_expected_fragments_per_event(self.subsystems[ss].source, subsystem_fragment_count)
TypeError: unsupported operand type(s) for +=: 'NoneType' and 'int'
Is there something in the configuration that I need to customize? Or something in the run_demo command string that I need to change?
Thanks a bunch,
#1 Updated by Eric Flumerfelt over 1 year ago
- Assignee set to Eric Flumerfelt
- Status changed from New to Resolved
If you have a relatively recent version of run_demo.sh, you can add the --brlist `pwd`/artdaq-utilities-daqinterface/simple_test_config/simple_subsystems/known_boardreaders_list_example to your run_demo command line. I have made some changes on branch artdaq-utilities-daqinterface:feature/22236_SimpleSubsystems_Fixes which resolves the error that occurs if there are no BoardReaders in a subsystem. I have also added component_subsystem_2 to the default known_boardreaders_list_example, so that with these changes, the example can be run with
--comps component01 component02 component_subsystem_2 --.
#3 Updated by Kurt Biery over 1 year ago
I have committed two new subsystem-related sample configurations to the "develop" branch of artdaq-utilities-daqinterface and merged these changes into the feature/22236_SimpleSubsystems_Fixes branch.
- pdune_swtrig helps to show how a 2-subsystem system could provide initial DFO functionality for upcoming protoDUNE tests
- dune_sample_system is an attempt to show how a multi-subsystem system might be used to test the use of artdaq processes within the data selection (trigger) part of the DAQ for DUNE
I believe that it is the second config that caused me to realize that the fix that Eric already committed to bookkeeping.py on the feature/22236_SimpleSubsystems_Fixes branch also needs to be present in the function that calculates the max event size. I have made that change and committed it on the same branch.
Thinking about the change that I made... I'm not sure that a default of zero is the right choice, so it would be great if someone who understands the bookkeeping code well will review this change.