Figure out the class we are looking at. This parser immediately
resolves possible references returning the name of the object in
this buffer and the associated data. This function needs a
Context, though, which may not be available. If so, have a look
at the classinfo parser.
Figure out the class we are looking at. The data might not be
saved locally but rather in a reference to some other place in the
buffer.This is modeled after ROOT’s TBufferFile::ReadObjectAny and
TBufferFile::ReadClass
Some Double_* values are saved with a custom mantissa… The
number of bytes can be found in the comment string of the
generated YAML code (for ALICE ESD files at least). This function
reconstructs a float from the exponent and mantissa
ESD trigger classes are strings describing a particular
Trigger. Each event (but in reality every run) might have a
different “menu” of available triggers. The trigger menu is saved
as an TObjArray of TNamed objects for each event. This breaks
it down to a simple vector
Same as raw but doesn’t require a Context as input. Panics if
a Context is required to parse the underlying buffer (i.e., the
given buffer contains a reference to some other part of the file.