Search/Navigation:
Related:
SLAC/EPP
/HPS Public
Jefferson Lab/Hall B
/HPS Run Wiki
S30XL-LESA/LDMX
EVIO (Event IO) is the raw data format used by the DAQ event builder. The structure of an EVIO file is a tree of banks, each of which has a header and a data payload.
Each EVIO bank has a data type a tag and a num. The type corresponds to the contents of the bank.
data_type | Size | content | notes |
---|---|---|---|
0x0c,0x0d,0x0e,0x10,0x20,0x40 | N | container | this is a bank that contains other banks |
0x00, 0x01 | 4 | uint32_t | unsigned integers |
0x02 | 4 | float | |
0x0b | 4 | int | signed integers |
0x0f | N | compound type | FADC (or other!) compound format. |
0x03 | 1 | char | char |
0x06 | 1 | int8_t = char | char |
0x07 | 1 | uint8_t | unsigned char |
0x04 | 2 | int16_t | short |
0x05 | 2 | uint16_t | unsigned short |
0x08 | 8 | double | |
0x09 | 8 | int64_t | long |
0x0a | 8 | uint64_t | unsigned long |
Source: EVIO C++ code data parser.
Note: The 0x0f compound type data contains a string that tells you what the layout of the data is. See EVIO documentation.
On the CLON machines, you in the directory pointed to by $CLON_PARMS is a file, clonbanks.xml that is supposed to be the "dictionary" for the EVIO contents.