There are four DUNE DAQ software packages which are used to aid developers in creating packages designed for the DAQ itself:
To learn how to build an existing software package, read the daq-buildtools documentation
To learn how to create a new package or modify the build of an existing one, read the daq-cmake documentation
To learn about the standard development workflow, read the daq-release documentation, in particular this page
To learn about the C++ coding guidelines which DUNE DAQ package developers should follow, read the styleguide
For the other packages, please click on one of the links below. To learn how to edit a package's documentation, click here. Packages marked with an asterix don't yet have any official documentation; please see their Issues page to remedy this.
appfwk home of daq_application and tools for writing DAQModules
cmdlib interfaces for commanded objects
dataformats raw data reinterpretation utilities
dfmessages dataflow messages
dfmodules dataflow applications
ers fork of the ATLAS Error Reporting System
ipm message passing between processes
listrev educational example of DAQModules for new developers
logging contains the functions DUNE DAQ packages use to output text
minidaqapp application to read out Felix data and store it in HDF5 files on disk
nwqueueadapters DAQModules that connect appfwk queues to IPM network connections
opmonlib operational monitoring library
* rcif run control related
readout upstream DAQ readout, DAQModules, CCM interface implementations
restcmd HTTP REST backend based CommandFacility
serialization utilities for C++ object serialization/deserialization
trigemu trigger decision emulator for readout application tests
Mar-11-2021: For software coordinators only: how to make edits to this webpage