STAR Trigger Data Format
STAR Trigger Data Format:
08/13/98: HjC, EJ - Original proposal
08/14/98: JMN - Added header information
10/09/98: EGJ - Changed names of raw data blocks headers slightly and added
count of Npre and Npost raw data blocks
02/01/99: EGJ - Moved 2x2 bytes of Npre/Npost information into event descriptor
so event descriptor length is modulo 8 bytes (useful for SCI)
Defined some of internal structure of Trigger Summary
Moved DSM data from TCU crate out of Raw Data block into
Trigger Summary
09/28/99: HjC,ZM, JMN - removed byte limits
rearranged byte counts and headers
12/06/99: ZM - cleaned up structures and moved ZDC data
12/21/99: zm - fixed length of raw data buffer, trg summary; made into html document.
1/13/00: zm - corrected to agree with trgStructures.h.
DESCRIPTION AND SIZE VALUE
- The first 4 bytes are for "native trigger format" - NOTE - these 4 Bytes are
not passed to DAQ!
- 2 bytes total trigger event byte count
- 2 bytes filler (now = 0)
The following data is passed to DAQ:
- 28 byte Event Descriptor Constructed in level 1 and containing all TCU readout
- 2 bytes byte-count Length of Event Descriptor including this header (28 B)
- 1 bytes header "E" in ASCII for Event Descriptor
- 1 byte version number allows up to 256 separate formats for trigger events
nibble 1 is major version, nibble 2 is minor version number
thus this version is 00010001 binary or ox11
- 4 bytes data MS 32 bits of 64-bit Bunch Crossing Number
- 4 bytes data LS 32 bits of 64-bit Bunch Crossing Number
- 2 bytes data Token
- 2 bytes data Action Word:
- 4 bits TRG Cmd
- 4 bits DAQ Cmd
- 8 bits Detector Bitmask
this bit packing is compiler specific
- 2 bytes data Output from last DSM board, saved on TCU
- 2 bytes data Address of raw data for this crossing in DSM buffers
- 1 byte data Busy bits at start of this Bunch Crossing
- 1 byte data Flag bits: bit 0 = Pileup flag, bit 1 = Priority, bit 7 = Fake Data
- 2 bytes data Trigger Word
- 2 bytes data Number of pre-History raw data blocks - Npre
- 2 bytes data Number of post-History raw data blocks - Npost
- Trigger Summary Level 1 and level 2 results are here, along wih the data from the DSMs in the TCU crate
- 2 bytes byte-count Length of Trigger Summary, including this header (432 B)
- 2 bytes header "TS" in ASCII for Trigger Summary
- 8 bytes L1 Summary descriptor
- 8 bytes L2 summary descriptor
- 2 bytes byte-count byte count for DSMs read out for L1 (l = 144 bytes)
- 2 bytes header "L0" in ASCII
- l bytes data Data from DSMs in TCU crate
- 32 - 2B words of coarse pixel array
- 8 - 2B words of CTB+MWC DSM
- 8 - 2B words last DSM
- 16 - 1B words from ZDC DSM
- 16 - 2B words from the 2 bunch crossing DSMs
- 2 bytes byte-count byte count for L1 results (m = 128)
- 2 bytes header "L1" in ASCII
- m bytes data L1 Results
- 2 bytes byte-count byte count for L2 results (n = 128)
- 2 bytes header "L2" in ASCII
- n bytes data L2 Results
NOTE: the first raw data block is always for the triggered crossing. The data
for the Npre crossings comes immediately after that, and the Npost data blocks
come last
- Raw Data Blocks:
- 2 byte byte-count: Length of RAW data block including this header (408 B)
- 2 byte header: "RD"
- 2 byte byte-count: Length of CTB data block
- 2 byte header: "CT"
- x bytes data Data from DSMs in CTB crate (x = 256)
- 2 byte byte-count: byte count for MWC
- 2 byte header: "MW"
- 4 byte filler: Filler to align data to 8-byte boundary
- y bytes data Data from DSMs in MWC crate (y = 128 )
- 2 byte byte-count: byte count for EMC DSMs
- 2 byte header: "EM"
- 4 byte filler: Filler to align data to 8-byte boundary
------------ below here is just to give an idea
- z bytes data Data from DSMs in EMC crates (z = 0 as of 18 Nov 1999)
the RAW data block is repeated here npre and npost times.