Daq-decode Documentation¶
Author: Torsten Schmidt
Decoding the DAQ event format and filling the dataclasses structures is the job of a DAQ decoder service.
Overview¶
Decoding the DAQ event format and filling the dataclasses structures
is the job of a DAQ decoder service. Several older decoders have been
retired, and only the I3PayloadParsingEventDecoderFactory
is supported.
The I3PayloadParsingEventDecoderFactory
is supplied by the payload-parsing project,
which is new approach to directly decode the DAQ
event format directly from C++.
Both services support eleven parameters
Year defines the year the data to decode is from (default:
2006
)HeaderID defines the name of the
I3EventHeader
added to a frame (default:I3DefaultName<I3EventHeader>::value()
)TriggerID defines the name of the
I3TriggerHierarchy
added to a frame (default:I3DefaultName<I3TriggerHierarchy>::value()
)SpecialDataOMs defines optical modules whose DOM launches are not assigned to any IceCube or IceTop
I3DOMLaunchSeriesMap
, but to the special dataI3DOMLaunchSeriesMap
insteadSpecialDataID defines the name of the special data
I3DOMLaunchSeriesMap
added to a frameInIceID defines the name affix that is pre-appended to the name of any IceCube
I3DOMLaunchSeriesMap
added to a frame (default:InIce
)IceTopID defines the name affix that is pre-appended to the name of any IceTop
I3DOMLaunchSeriesMap
added to a frame (default:IceTop
)SPEDataID defines the name of an
I3DOMLaunchSeriesMap
that holds DOM launches with trigger modeSPE_DISCRIMINATOR_TRIGGER
(default:RawData
)FlasherDataID defines the name of an
I3DOMLaunchSeriesMap
that holds DOM launches with trigger modeFLASHER_BOARD_TRIGGER
CPUDataID defines the name of an
I3DOMLaunchSeriesMap
that holds DOM launches with trigger modeCPU_REQUESTED
andTestDataID defines the name of an
I3DOMLaunchSeriesMap
that holds DOM launches with trigger modeTEST_PATTER
And into a given frame might create, fill and insert:
upto nine
I3DOMLaunchSeriesMaps