Recoil ADAMO Tables
 |
This page is considered done. It been reviewed by Sergey. There may be missing elements, but they are all flagged and the text has no errors. |
Page maintainer: Andreas
Intro
The following page describes the structure of the Recoil Detector related ADAMO tables both for HRC/XTC and uDST data.
ADAMO Tables
HRC/XTC
The following flowchart shows all Recoil Detector related ADAMO tables (HRC/XTC) with their interconnections and levels of abstraction.
Track Level
The highest level of XTC output is the Track level. It consists of the tables rdTrack, rdTrackPar and rdSET. rdTrack contains the basic track parameter with links to rdTrackPar depending on the particle type assumed during the reconstruction of a track. In rdTrack iMethod is the method with which the track was reconstructed and iSciFiTDCBits is the TDC bit pattern for the SFT. The bits are assigned in groups of 2 with the lower bit indicating that there was a TDC hit in the correct time window and the higher bit indicating that there was a TDC hit outside the correct TDC window. Up to 6 of those groups are encoded in iSciFiTDCBits. The encoding is the following:
group = 2 bits
bit 0 = hit in correct TDC window
bit 1 = hit outside correct TDC window
layer = 0 (SFI1)
1 (SFI2)
2 (SFI3)
3 (SFI4)
4 (SFO1)
5 (SFO3)
bits = group << (layer*2)
rdTrackPar is used to store the reconstructed track parameter. XTC also provides a table rdSET with Recoil Detector status information. At the moment it holds the status bits of the SSD (iSSDinnerBits and iSSDouterBits. The two data words provide 64 bits each corresponding to one of the 64 front-end chips used in the SSD. If one of the bits is set the encoded chip was not working correctly. The encoding is done as follows:
quadrant = [1;4]
sensor = [1;2]
gain = 0 (low gain)
1 (high gain)
side = 0 (P side)
1 (N side)
bit = ( (quadrant-1) + ( (sensor-1) << 2) )*4 + gain + (side<<1)
rdTrack
- iEvent - Event number
- iMethod - Tracking method
- iSciFiTDCBits - SFT TDC bit pattern
- Pion - Link to the pion hypothesis rdTrackPar row
- Proton - Link to the proton hypothesis rdTrackPar row
- StoppedProton' - Link to the stopped proton hypothesis rdTrackPar row
- Deuteron - Link to the deuteron hypothesis rdTrackPar row
- StoppedDeuteron - Link to the stopped deuteron hypothesis rdTrackPar row
rdTrackPar
- rEnergy - Momentum of particle in GeV/c
- rTheta - Theta angle of track in rad
- rPhi - Phi angle of track in rad
- rVertex[3] - Vertex coordinates (X, Y, Z) in cm
- rCov[10] - Covariant matrix
rdSET
- iSSDinnerBits - Status bits for the inner SSD modules
- iSSDouterBits - Status bits for the outer SSD modules
Spacepoint & Cluster, Hit and Detector Hit Level
For each track XTC provides links to the spacepoints (rdSpacePoints) and clusters (rdCluster) used in the track. As tracks are reconstructed with several different methods, clusters and spacepoints can be shared with more than one track. The links are therefore implemented as Many-To-Many relationships via the intermediate tables rdTr2Sp (spacepoints) and rdTr2Cl (clusters). For tracking studies also the residuals are available for each track hypothesis in rdTrackPar via a the dedicated table rdTr2SpRes. Note that the rdTr2SpRes table is not filled in a regular data production. In order to navigate from a given spacepoints to its clusters or from a cluster to the spacepoints it is used in, the rdSp2Cl table provides Many-To-Many relationships between rdCluster and rdSpacePoint.
Each cluster consists of one or more hits. The primary information of a hit is its energy which is provided in the rdHit ADAMO table. To navigate from a given cluster to its hits, rdHit provides a link to the rdCluster it is used in. The Detector Hit level provides additional information on the hits in the tables rdSiliHit, rdSciFiHit, rdSciTdcHit and rdPhotoHit. The Detector Hit level is also the lowest level of information provided by XTC.
rdSpacePoint
- rX - X position of spacepoint in cm
- rY - Y position of spacepoint in cm
- rZ - Z position of spacepoint in cm
- rPuls - Energy deposit of spacepoint in GeV
- iClusters - Number of clusters forming the spacepoint
rdCluster
- rEnergy - Energy deposit of cluster
- rNumber - Strip (SSD or PD) or Fiber (SFT) number of cluster
- iHits - Number of hits forming the cluster
rdTr2SpRes
- rPhi - Spacepoint residual in phi coordinate in rad
- rZ - Spacepoint residual in Z coordinate in cm
rdHit
- rEnergy - Energy deposit of hit
rdSiliHit
- rCorrAdcH - High gain ADC value after second order common-mode correction
- rCorrAdcH - Low gain ADC value after second order common-mode correction
- rXtCorrAdcH - High gain ADC value after crosstalk correction
- rXtCorrAdcH - Low gain ADC value after crosstalk correction
rdSciFiHit
- iTDCHits - Number of TDC hits
Raw Level
dataSiliRec
- iStrip - Strip number (1-128 corresponds to P-side; 1001-1128 corresponds to N-side)
- iADCHigh - High gain ADC value
- iADCLow - Low gain ADC value
- iCMHigh - High gain common-mode value
- iCMLow - Low gain common-mode value
- rPulsHigh - Calibrated high gain value (not used)
- rPulsLow - Calibrated low gain value (not used)
- iTrailerHigh - High gain trailer value
- iTrailerLow - Low gain trailer value
dataSciRec
- iFiber - Fiber number
- iSlot - PMT slot number
- iChannel - Channel number on the PMT
- iADC - ADC value
- rPuls - Calibrated ADC value (not used)
dataSciDyRec
- iPMT - PMT number
- iTDC - TDC value
dataPhotoRec
- iPMT - PMT number
- iADC - ADC value
- rPuls - Calibrated ADC value (not used)
MC Level
In case one analyzes MC data, XTC also provides links between reconstructed tracks and Monte Carlo tracks (mcTrack) via the ADAMO table rd2mcTrack. The relationship via untracked spacepoints and Monte Carlo tracks is available via the table rdpd2mcTrack.
uDST
The following flowchart shows all Recoil Detector related ADAMO tables for uDST data.
The tables g1RDTrack and g1RDTrackpar are copies of the HRC/XTC tables rdTrack and rdTrackPar. The only difference is the column bHitP and a link from g1RDTrack to g1RDPID. The column bHitP stores the hit bit pattern for a given track. The bits are assigned as follows:
0x00001 inner SSD 0x00002 outer SSD 0x00004 inner SFT 0x00008 outer SFT 0x10000 no SSD/SFT hit <== for internal use from here on (please see following note) 0x20000 no method 7 track 0x40000 no pion hypothesis 0x80000 track energy < 0
Important note: The highest four bits are intendended for internal use. They have to treated with care If one of these bits is set, the state of the following bits is undefined and should not be used.
The table g1RDPID holds the particle identification values for the 6 sensitive layers. The array indices are:
0 inner SSD 1 outer SSD 2 inner SFT parallel 3 inner SFT stereo 4 outer SFT parallel 5 outer SFT stereo
Untracked spacepoints in the Recoil Photon Detector are stored in the table g1PD.
g1RDTrack
- iEvent - Event number
- iMethod - Tracking method
- iSciFiTDCBits - The SFT TDC bit pattern
- bHitP - Track hit pattern
- Pion - Link to the pion hypothesis g1RDTrackPar row
- Proton - Link to the proton hypothesis g1RDTrackPar row
- StoppedProton' - Link to the stopped proton hypothesis g1RDTrackPar row
- Deuteron - Link to the deuteron hypothesis g1RDTrackPar row
- StoppedDeuteron - Link to the stopped deuteron hypothesis g1RDTrackPar row
- g1RDPID - Link to the corresponding g1RDPID table row
g1RDTrackPar
- rEnergy - Particle momentum in GeV/c
- rTheta - Track theta angle
- rPhi - Track phi angle
- rVertex[3] - Vertex position (X, Y and Z) in cm
- rCov[10] - Chi2 (rCoV[0]) and covariant matrix
g1RDPID
- rPID[6] - PID values for the sensitive layers
g1PD
- iEvent - Event Number
- rX - X position of the spacepoint in cm
- rY - Y position of the spacepoint in cm
- rZ - Z position of the spacepoint in cm
- rPuls - Energy deposit of the spacepoint in GeV
- iClusters - Number of clusters forming the spacepoint
More Info
For more information see
- the HannaPlusPlus documentation
Code Repository
- See the examples section of the HannaPlusPlus page.