Embed Size (px)
Citation preview
To make ByteStream DataThere is a plan that the High Level Trigger (HLT) software uses the offline framework (Athena).
HLT group wants to read in ByteStream data, convert them into Athena Objects and run their algorithms.
They want to measure the efficiency of the conversion from ByteStream to Athena objects.
As a result, we need to produce a fraction of the Monte Carlo data in the ByteStream format.
To do so, we need to know the exact mapping between ROD, ROB/ROC etc.
The scheme
Transient Data Store
ByteStream –Raw Data format
HLT/AthenaAlgorithms
header
trailer
ByteStreamCnv
In principle, perhaps, LArRawChannelCollection
should correspond to ROB (?).
At the moment, we have
LArRawChannelCollection
Feedthrough no. in LArHardwareID
ROD and FEB Channel : 11
Data Organization in the offline LArROD
......
LA rR aw C h an n elC o llectio n
LA rR aw C h an n el
LA rR aw C h an n el
LA rR aw C h an n el
......
LA rR aw C h an n elC o llectio n
......
LA rR aw C h an n elC o llectio n
LA rR aw C h an n elC o n tain er
ROD Channel
Data format and the mapping
In order to modify LArRawChannelContainer to what it really should be, we need to know the mappings between FEB channel (feedthrough no./FEB slot/channel no.) and ROD – ROB - ROC.
We do this only because the HLT group and upper management “ask” us to produce the Monte Carlo in the RawData (ByteStream) format. If somebody wants to do this, he/she is more than welcome to take up this job.
The ROD Demo Board has defined the data format which has been used.
It is probably close to what we want but ... Eg. The PU in the RODDemo only holds half a FEB and the final PU in the final ROD probably holds 2 PU’s.
Apart from that, we still need to know how the exact mapping in ROD-ROB-ROC. It will be nice if somebody can give it to us.
ROD Demo Board has defined the data format …
32 31 0
0 Beginning of fragment (0x00000B0F)
Header
1 Start of header marker (0xEEEEEEEE)
1 Header size (0x08)
1 Format version number
1 Source Identifier
1 Level 1 ID
1 Bunch crossing ID
1 Level 1 Trigger Type
1 Detector Event Type
Detector Data
Status word1 No of PU PU Mask Detector Format Version Number
Processing Unit 1
1 Fixed Block #0
1 Fixed Block #1
1 Fixed Block #21 Variable Block #3
1 Variable Block #4
1 Variable Block #5
Processing Unit 2
1 Fixed Block #0
1 Fixed Block #1
1 Fixed Block #2
1 Variable Block #3
![ATHENA - Coordinate System Document...[RD02] ATHENA Mission Requirements Document (MRD), ATHENA-ESA-URD-0010 [RD03] ATHENA Product Tree, ATHENA-ESA-PT-0001 [RD04] Ariane 5 User’s](https://img.pdfslide.us/doc/110x75/5ff23cd84225de2c7f4f21b6/athena-coordinate-system-document-rd02-athena-mission-requirements-document.jpg)
