EVIO: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
* BOS bank name will be replaced with 16-bit (12-bit probably) field ''tag'', BOS bank number will be replaced with 8-bit field ''num'' | * BOS bank name will be replaced with 16-bit (12-bit probably) field ''tag'', BOS bank number will be replaced with 8-bit field ''num'' | ||
* banks dictionary will be provided in some form (ASCII, Dadabase ?) which will contain an notation on every bank ''tag'', most important will be the number of 'columns' and the meaning of every column (for example id,tdcl,adcl,tdcr,tdcl), it will help to decode data from the bank | |||
Revision as of 14:54, 27 September 2011
EVIO is data format and corresponding software used at JLAB.
EVIO Manual version 2.0: pdf doc.
Data structure in DAQ chain: pptx.
CLAS12 guidelines:
1. BOS-to-EVIO transition:
- 'EVIO BANK' (not 'EVIO SEGMENT' or 'EVIO TAGSEGMENT' will be used for data banks
- no mixed formats (for example 'int' and 'short') will be allowed in the same bank, format is described in 8-bit field contentType
- BOS bank name will be replaced with 16-bit (12-bit probably) field tag, BOS bank number will be replaced with 8-bit field num
- banks dictionary will be provided in some form (ASCII, Dadabase ?) which will contain an notation on every bank tag, most important will be the number of 'columns' and the meaning of every column (for example id,tdcl,adcl,tdcr,tdcl), it will help to decode data from the bank