Data Format Used in the 2020 run (commissioning & production)

1) CbmTofStarSubevent2019

One subevent sent by the full eTOF wheel for each STAR trigger.
The packed version sent to the STAR DAQ systems is made of a 256b header (4 long unsigned integers) followed by a buffer of gdpb::FullMessage (128b each).
The data from each sector are inserted in a continuous block, starting from sector 13.
The maximal size of the eTOF subevent is 131072 bytes, corresponding to 8190 FullMessages. Subevents with bigger size will be truncated and the corresponding flag set in the Subevent header.
If the insertion of status messages was enabled in the Event Builder, the first 8 FullMessages of each sector block will be the latest update of the status mask before the trigger time.
In the status mask, a 1 indicates an ASIC curretnly having problems (disabled, off-sync in time or currently undergoing recovery).

The class definition with accessor and setter methods can be found at:
redmine.cbm.gsi.de/projects/cbmroot/repository/entry/trunk/fles/star2019/eventbuilder/CbmTofStarData2019.h
redmine.cbm.gsi.de/projects/cbmroot/repository/entry/trunk/fles/star2019/eventbuilder/CbmTofStarData2019.cxx

WARNING: the 'n' FullMessages in the graphical representation include in the first case the Status messages of Sectors 14 to 24!

2) gdpbv100::FullMessage and gdpbv100::Message data format

gdpbv100::Message = 64 bit message as received from the eTOF gDPB boards
gdpbv100::FullMessage = 128 bit message, obtained by combining a 64b extended epoch (bits 127-64) with a gdpbv100::Message (bits 63-0)

Compared to the format used during the 2019 run, the only change is the addition of a 4th type of pattern messages, which is only generated by the eTOF event builder (not present in raw data on the "CBM" side).
This new pattern is generated by a bitwise OR of the 3 original patterns (sync missmatch, disable and reconfig).

The class definition with accessor and setter methods can be found at:
https://lxcbmredmine01.gsi.de/projects/cbmroot/repository/entry/trunk/fles/mcbm2018/dataformat/gDpbMessv100.h
https://lxcbmredmine01.gsi.de/projects/cbmroot/repository/entry/trunk/fles/mcbm2018/dataformat/gDpbMessv100.cxx

Data Format Used in the 2019 run (commissioning & production)

1) CbmTofStarSubevent2018

One subevent sent by the full eTOF wheel for each STAR trigger.
The packed version sent to the STAR DAQ systems is made of 256b header (4 long unsigned integers) followed by a buffer of gdpb::FullMessage (128b each).
The data from each sector are inserted in a continuous block, starting from sector 13.
The maximal size of the eTOF subevent is 131072 bytes, corresponding to 8190 FullMessages. Subevents with bigger size will be truncated and the corresponding flag set in the Subevent header.

The class definition with accessor and setter methods can be found at:
redmine.cbm.gsi.de/projects/cbmroot/repository/entry/trunk/fles/star2018/unpacker/CbmTofStarData2018.h
redmine.cbm.gsi.de/projects/cbmroot/repository/entry/trunk/fles/star2018/unpacker/CbmTofStarData2018.cxx

2) gdpbv100::FullMessage and gdpbv100::Message data format

gdpbv100::Message = 64 bit message as received from the eTOF gDPB boards
gdpbv100::FullMessage = 128 bit message, obtained by combining a 64b extended epoch (bits 127-64) with a gdpbv100::Message (bits 63-0)

The class definition with accessor and setter methods can be found at:
https://lxcbmredmine01.gsi.de/projects/cbmroot/repository/entry/trunk/fles/mcbm2018/dataformat/gDpbMessv100.h
https://lxcbmredmine01.gsi.de/projects/cbmroot/repository/entry/trunk/fles/mcbm2018/dataformat/gDpbMessv100.cxx

gdpbv100::Message data format for all defined types, as in memory:

Only the 32b Hits are used in the eTOF system in normal operation. 24b Hits are a debug option which is not planned at the moment to be used with this system.

The time of a hit is calculated as:

ClockCycleNs = 6.25
EpochNs = 25600
FtBins = 112

HitTime = (Extended)Epoch * EpochNs + ClockCycleNs * FullTs / FtBins

For monitoring and eventual calibration, one can obtain the FineTime by

FineTime = FullTs % FtBins

For more information on the GET4 v2.00 used in eTOF, its performances and its timestamps, please refer to the GET4 manual which can be found at:
To be added when publicly released

Data Format Used in the 2018 run (prototyping/commissioning)

1) CbmTofStarSubevent2018

One subevent sent by the eTOF sector 16 for each STAR trigger.
The packed version sent to the STAR DAQ systems is made of 256b header (4 long unsigned integers) followed by a buffer of gdpb::FullMessage (128b each).

The event size field is filled only for data sets started after 24/04/2018 at 11:10 EDT. For older runs the field is filled with 0.

The event status flags are (in bit order):
0x0001 => Bad Event
0x0002 => Overlap Event = Event with trigger window overlapping the previous/next event, not possible in 2018 run
0x0004 => Empty Event
0x0008 => Start Border Event = Event with a trigger window overlapping the Start border of the timeslice (may have data in previous timeslice), data from previous timeslice are not added to the event in 2018 run!
0x0010 => End Border Event = Event with a trigger window overlapping the End border of the timeslice (may have data in next timeslice), in run 2018 only possible if the trigger message for at least one gDPB was in the current timeslice

The class definition with accessor and setter methods can be found at:
lxcbmredmine01.gsi.de/projects/cbmroot/repository/entry/trunk/fles/star2018/unpacker/CbmTofStarData2018.h
lxcbmredmine01.gsi.de/projects/cbmroot/repository/entry/trunk/fles/star2018/unpacker/CbmTofStarData2018.cxx

CbmTofStarSubevent2018 data format as in memory:

2) gdpb::FullMessage and gdpb::Message data format

gdpb::Message = 64 bit message as received from the eTOF gDPB boards
gdpb::FullMessage = 128 bit message, obtained by combining a 64b extended epoch (bits 127-64) with a gdpb::Messaged (bits 63-0)

The class definition with accessor and setter methods can be found at:
lxcbmredmine01.gsi.de/projects/cbmroot/repository/entry/trunk/fles/star2018/unpacker/rocMess_wGet4v2.h
lxcbmredmine01.gsi.de/projects/cbmroot/repository/entry/trunk/fles/star2018/unpacker/rocMess_wGet4v2.cxx

gdpb::Message data format for all defined types, as in memory:

Only the 32b Hits are used in the eTOF system in normal operation. 24b Hits are a debug option which is not planned at the moment to be used with this system.

The time of a hit is calculated as:

ClockCycleNs = 6.25
EpochNs = 25600
FtBins = 112

HitTime = (Extended)Epoch * EpochNs + ClockCycleNs * FullTs / FtBins

For monitoring and eventual calibration, one can obtain the FineTime by

FineTime = FullTs % FtBins

For more information on the GET4 v2.00 used in eTOF, its performances and its timestamps, please refer to the GET4 manual which can be found at:
To be added when publicly released