dMuiFEM

struct dMuiFEM

Table produced by mMuiRawToFEM_ which turns input dMuiRaw data into the data content sent from the FEM to the DCM

unsigned short CAV1: Beginning of packet 0xFFFF
unsigned short DetectorId: Detector ID = 0x0C00 (South Arm) = 0x0C01 (North Arm)
unsigned short EventNumber: Event number (0x0000 for now)
unsigned short ModuleId: Module: 0x0000(S horiz) 0x0010(S vert) 0x1000(N horiz) 0x1010(N vert)
unsigned short Flag: Flag word (0x0000 for now)
unsigned short BeamClock: Beam clock counter (0x0000 for now)
unsigned short data[120]: FEM data
unsigned short user[8]: User words (up to 8 available)
unsigned short parity: Parity word
unsigned short CAV2: End of packet 0x0000

Documentation

Table produced by mMuiRawToFEM_ which turns input dMuiRaw data into the data content sent from the FEM to the DCM.
There will be 4 of these structure in each real PHENIX event

one for all of the North Horizontal Tubes,
one for all of the North Vertical Tubes,
one for all of the South Horizontal Tubes,
one for all of the South Vertical Tubes
The packet contains first some header information (http://www.nevis.columbia.edu/~nagle/PHENIX/Data_Formats/PHENIX_Formats/header_words_pub.htm) which contains among other things, the FEM hardware address which should contain the information:

arm - (0-1) = 1 bit
Orientation - (0-1) = 1 bit
Following the header are the data words (http://www.nevis.columbia.edu/~nagle/PHENIX/Data_Formats/PHENIX_Formats/muid_format_pub.htm), with 16 bits available for data information.
In all, we have

6 header words
120 data words
8 User words
2 Trailer words
= 136 2-byte words/FEM packet
For information on numbering conventions, see http://www.phenix.bnl.gov/WWW/muon/muid_fee/numbering/numbering.htm
June 29, 1998 Soren Sorensen