EVIO: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 20: | Line 20: | ||
* 'EVIO BANK' (not 'EVIO SEGMENT' or 'EVIO TAGSEGMENT' will be used for data banks; bank header has 2 words, first one is exclusive bank length in words, second one contains 3 fields: tag[31:16], contentType[15:8] and num[7:0] | * 'EVIO BANK' (not 'EVIO SEGMENT' or 'EVIO TAGSEGMENT' will be used for data banks; bank header has 2 words, first one is exclusive bank length in words, second one contains 3 fields: tag[31:16], contentType[15:8] and num[7:0] | ||
* no mixed formats (for example 'int' and 'short') will be allowed in the same bank, format is described in 8-bit field ''contentType'' | * no mixed formats (for example 'int' and 'short') will be allowed in the same bank, format is described in 8-bit field ''contentType'' (or use type=0 and do custom swap ?) | ||
* BOS bank name will be replaced with 16-bit field ''tag'', BOS bank number will be replaced with 8-bit field ''num'' | * BOS bank name will be replaced with 16-bit field ''tag'', BOS bank number will be replaced with 8-bit field ''num'' | ||
| Line 26: | Line 26: | ||
* banks dictionary (former DDL replacement) will be provided in some form (ASCII ?) and will contains a 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 and can be used by evio viewers; will be written at least in the beginning of every file | * banks dictionary (former DDL replacement) will be provided in some form (ASCII ?) and will contains a 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 and can be used by evio viewers; will be written at least in the beginning of every file | ||
* raw data banks | * all raw data banks will be in 'unsigned short' format; first 16 bits will be ID ('slot<<8+channel' without translation, 'layer<<8+wire' or similar with translation) | ||
* some bank examples: | |||
tdc version 1: ID, TDC_HIT | |||
tdc version 2: ID, N_HITS, HIT_1, ... , HIT_N | |||
adc version 1: ID, | |||
Revision as of 21:31, 28 September 2011
EVIO is data format and corresponding software used at JLAB.
EVIO Manual version 2.0: pdf doc.
Event Building EVIO Scheme: pdf ppt pptx.
Not in the manual yet: 8-word EVIO block(record) header:
1. block length 2. block number 3. header length=8 4. event count (# of banks, without dictionary if it is inserted) 5. not used 6. bit info[31-8] version [7-0]; if dectionary is therer, bit 8 (starting from 0) will be set 7. unused 8. magic int = 0xc0da0100
CLAS12 guidelines:
- 'EVIO BANK' (not 'EVIO SEGMENT' or 'EVIO TAGSEGMENT' will be used for data banks; bank header has 2 words, first one is exclusive bank length in words, second one contains 3 fields: tag[31:16], contentType[15:8] and num[7:0]
- no mixed formats (for example 'int' and 'short') will be allowed in the same bank, format is described in 8-bit field contentType (or use type=0 and do custom swap ?)
- BOS bank name will be replaced with 16-bit field tag, BOS bank number will be replaced with 8-bit field num
- banks dictionary (former DDL replacement) will be provided in some form (ASCII ?) and will contains a 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 and can be used by evio viewers; will be written at least in the beginning of every file
- all raw data banks will be in 'unsigned short' format; first 16 bits will be ID ('slot<<8+channel' without translation, 'layer<<8+wire' or similar with translation)
- some bank examples:
tdc version 1: ID, TDC_HIT tdc version 2: ID, N_HITS, HIT_1, ... , HIT_N adc version 1: ID,