Skip to content

Ideas for a data container

bieryAtFnal edited this page Aug 30, 2020 · 4 revisions

Start with something simple?

  • a 32-bit header word with the size in bytes
  • class name = dune::RawFragment? or just dune::Fragment?
  • do we want a header field that tells us whether the fragment corresponds to a part of a Trigger Record or part of a Time Slice?
    • if so, what about a header field (or fields) that identify that TR or Time Slice?
  • do we want a header field that tells us something about the (geographic) source of the data?
  • header version
  • marker word

Initial idea:

  • uint16_t version - fragment header version
  • uint16_t marker - marker word
  • uint32_t size - fragment size in bytes, includes size of header
  • uint16_t id - unique value for each fragment in a TR or timeslice; for internal DAQ use only (offline should not use this field as a geographic ID)
  • uint32_t checksum

Clone this wiki locally