Name: DUNE DAQ Core Software Meeting
Start: 2024-10-02T09:00:00-05:00
End: 2024-10-02T10:00:00-05:00
Location: No location set

DUNE DAQ Core Software Meeting

Wednesday, 2 October 2024 - 09:00

Monday, 30 September 2024
Tuesday, 1 October 2024
Wednesday, 2 October 2024
09:00 fddaq-v5.2.0 topics - Roland Sipos (CERN) Kurt Biery (Fermilab) Eric Flumerfelt (Fermilab)
fddaq-v5.2.0 topics
- Roland Sipos (CERN)
- Kurt Biery (Fermilab)
- Eric Flumerfelt (Fermilab)
09:00 - 09:45
09:45 Policy question about one aspect of system configurations - Pierre Lasorak (Imperial College London) Kurt Biery (Fermilab)
Policy question about one aspect of system configurations
- Pierre Lasorak (Imperial College London)
- Kurt Biery (Fermilab)
09:45 - 10:00
Why are most TC producers connected to the TC DataSubscriberModule (actually data-reader-mlt), but the RandomTriggerCandidateMaker is connected directly to the TriggerDataHandlerModule (def-tc-handler-10000)? (Apologies if this is more of a question for DataSelection folks...) Background: we see the MLT and the ConnectivityService using a lot of CPU when we run the minimal_system_quick_test. Pierre tracked this down to a dangling connection (only one process/module, not two), and to some very fast re-trying to connect to the non-existent other end of the connection. Some notes about the diagrams that are attached to this agenda contribution: * the files are in SVG format, and in my experience, they are straightforwardly displayed by web browsers * the "minsysQT" diagrams show aspects of the configuration that is used in the minimal_system_quick_test automated regression test (in the daqsystemtest package) * the "dstExample" diagrams show aspects of the local-1x1-config example configuration that is provided in the daqsystemtest repo, config/daqsystemtest subdirectory