All the trigger DAQModules do_work threads now have unique names, taken from the module's unique name -- which is in turn set in the daqconf. At the same time, some of the modules unique names had to be renamed as they were more than 16 characters long -- and they must be 16 chars or less, as explained HERE.
This doesn't change how the trigger works in any way, but will enable us to pin threads to specific CPUs if we require this for NP04.
This PR goes together with:
Tested by:
Running the he integration test 3ru_3df_multirun_test.py.
Successfully generating a configuration with --debug to generate .dot files and looking through them.
Running offline with 3 readout units, and seeing triggers as expected.
All the trigger
DAQModulesdo_workthreads now have unique names, taken from the module's unique name -- which is in turn set in thedaqconf. At the same time, some of the modules unique names had to be renamed as they were more than 16 characters long -- and they must be 16 chars or less, as explained HERE. This doesn't change how the trigger works in any way, but will enable us to pin threads to specific CPUs if we require this for NP04.This PR goes together with:
Tested by:
3ru_3df_multirun_test.py.--debugto generate .dot files and looking through them.