artdaq_demo_hdf5  v1_01_02
Class Hierarchy
This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 12]
oCartdaq::hdf5::FragmentDatasetBase class that defines methods for reading and writing to HDF5 files via various implementation plugins
|oCartdaq::hdf5::FragmentNtupleImplemementation of FragmentDataset using hep_hpc Ntuples
|oCartdaq::hdf5::HighFiveGeoCmpltPDSPSampleSample ProtoDUNE HDF5 output which writes all data indexed by sequence ID
|oCartdaq::hdf5::HighFiveGeoCmpltPDSPSampleSample ProtoDUNE HDF5 output which writes all data indexed by sequence ID
|oCartdaq::hdf5::HighFiveGeoSplitPDSPSampleSample ProtoDUNE HDF5 writer that only writes certain Fragment types to output
|oCartdaq::hdf5::HighFiveGroupedDatasetA FragmentDataset implementation which produces files where each event is a Group, and each Fragment_id_t within the group is either a dataset or a group if it is a ContainerFragment
|\Cartdaq::hdf5::HighFiveNtupleDatasetAn implementation of FragmentDataset using the HighFive backend to produce files identical to those produced by the hep_hpc backend (FragmentNtuple)
oCartdaq::detail::HDFFileReaderThe HDFFileReader is a class which implements the methods needed by art::Source
oCartdaq::hdf5::HighFiveDatasetHelperHelper class for HighFiveNtupleDataset
oCOutputModule
|\Cart::HDFFileOutputThe HDFFileOutput module streams art Events to a binary file, bypassing ROOT
\Cart::Source_generator< artdaq::detail::HDFFileReader >Specialize an art source trait to tell art that we don't care about source.fileNames and don't want the files services to be used