Abbottd-info-needed-31-aug-2011
Generating "RAW" CODA events from Monte Carlo Data
Conversion of Monte Carlo events into raw CODA events can be accomplished assuming certain information about the experimental setup is provided. There are several additional levels of complexity of the raw CODA event that can be constructed, including blocking of multiple events within a single CODA event as well as "entangling" hits from multiple events within the blocks.
The simplest approach involves creating single event blocks, in which data from all modules in a given crate were read out with a single block read (and hence are contained in a single CODA block bank for each ROC) Regardless of the ultimate complexity of the CODA raw event created, the following information would be required - at a minimum - for the simplest case. It is broken down into "generic" info for the event, and digitizing module specific information.
The currently defined digitizing modules include:
Hit specific information (independent of Module type)
4) Crate ID (or ROC ID) - value between 0 and 255 (inclusive)
5) Slot ID - value between 2-21 for a general VME crate (slots 11,12 are
not allowed in a VXS crates)
6) Detector ID - 8 bit value uniquely identifying the detector
system
Hit specific information (for 250 MHz FADC)
7) Channel ID - value between 0 and 15
8) Hit/Pulse Integral - 19 bits Max (12 bit value X up to 128 samples)
9) Hit/Pulse Time - 17 bit value - 62.5ps resolution relative to
trigger timestamp. Low six bits
define the high resolution
component.
Hit specific information (for 125 MHz FADC)
7) Channel ID - value between 0 and 71
Hit/Pulse Info TBD
Hit specific information (for 32 Channel F1TDC)
7) Channel ID - value between 0 and 31
Hit/Pulse Info TBD (16 bit - 62.5 ps resolution)
Hit specific information (for 48 Channel F1TDC)
7) Channel ID - value between 0 and 47
Hit/Pulse Info TBD (16 bit - 125 ps resolution)
