artdaq Release Notes v3_08_00 (23-Mar-2020)


This version of artdaq can be built against art v3_05_00 (s96) (experimental), v3_04_00 (s94), v3_02_06 (s92, use art-v3_02_06c bundle) (experimental), v3_03_00 (s87), v2_13_00 (s85), v3_02_05 (s83), v3_02_04 (s82) (upon request), v2_11_05 (s73) (upon request) or v2_11_01 (s67) (upon request). It can be built with gcc v6_4_0 (e15), gcc v7_3_0 (e17), gcc v8_2_0 (s19), clang v7_0_0 (c7) or clang v5_0_1 (c2).

The default set of qualifiers for this version of artdaq is e17:s85.

This version of artdaq contains a new art service class, ArtdaqFragmentNamingServiceInterface. This results in a new configuration domain; pre-v3_08_00 configurations will not work with v3_08_00 without modification, and vice-versa. Because of this change, as well as other changes made in this version, there is now only one artdaq input source for art: ArtdaqInput. Functionality that was previously implemented in the input sources for Fragment identification should be moved to an implementation of ArtdaqFragmentNamingServiceInterface, see artdaq-demo:source:artdaq-demo/ArtModules/ for an example.

The ArtdaqInput art input source now supports arbitrary combinations of Fragments and serialized art Events.


artdaq version:"v3_08_00"

New features:

  • Feature #22154: Support combining DataFragment (serialized art Event) with other Fragments
  • Feature #24082: Separate Fragment Type <-> Name facility from SharedMemoryReader

Bug fixes and Improvements:

  • Bug #24087: Problems running art process in s94
  • Bug #24088: Python module not available in artdaq release 3_07_02
  • Bug #24183: OTS Error message: "Error: the start message requires the run number as an argument."

Operational changes:

  • none

Dependent Package Notes

  • artdaq_core v3_05_14
  • artdaq_utilities v1_05_05
  • art v3_05_00 (s96), v3_04_00 (s94), v3_02_06 (s92), v3_03_00 (s87), v2_13_00 (s85), v3_02_05 (s83), v3_02_04 (s82), v2_11_05 (s73), v2_11_01 (s67)