Difference: MakeNtuple (1 vs. 15)

Introduction

Variable desciption

General

• • There are valid values in the event info values if valid==0.

• • The run number

• • The event eumber

• • The unix time recorded in JMDC.

• • The livetime of the event.

• • The maximum cutoff calculated with Stormer model. The first index for 25, 30, 35, 40 degree FOV, and then index of 0, 1 for negative and positive events.

• • The maximum cutoff calculated with IGRF model. The index follow the same rule with info_maxcf.

• • The

• • The

• • The Stormer cutoff of the given particle direction.

• • The other Stormer cutoff stored in the event.

• • The back tracing result of IGRF model: the higher bits(info_btres>>8) is back tracing status (1: under cutoff, 2: above cutoff, 3: trapped, other: error); the lower 8bits(info_bres&256) is the back tracking result showing which position and time infomation are used in the calculation. For detail see AMSEventR::DoBacktracing();

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • Whether the particle pass through solar array on space station.

• • The

• • The id of selected particle object.

• • The generated momentum of MC particle. For data it's 0.

• • The theta of MC generated particle.

• • The phi of MC generated particle.

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The simulated external tracker misalignment on layer1(0) and layer9(1): the x(0) and y(1) value.

• • The level1 trigger variables is valid (==0).

• • The detailed trigger pattern. See Level1R::JMembPatt

• • The physics trigger pattern recorded. See Level1R::PhysBPatt

• • The

• • The

• • The

• • The

ECAL

• • The selected shower id.

• • The number of showers in the event.

• • The

• • The

• • The

• • The shower status bit 25, or -1 if no shower.

• • The reconstructed energy <nop>EnergyE.

• • The simple center of gravity for the shower.

• • The entry position of the shower, Z at the center of the first ECAL layer.

• • The old version based on simple COG.

• • The exit position of the shower, Z at the center of the last ECAL layer.

• • The deposited energy for each cell.

• • The ADC value from low gain channel for each cell.

• • The ADC value from high gain channel for each cell.

• • The orphan energy in ECAL.

• • The product of Energy3C [0] [1] and [2] (3cm, 5cm, 7cm).

• • The energy deposition within 3cm of shower axis (Energy3C [0])

• • The energy deposition within 5cm of shower axis (Energy3C [1])

• • The

• • The

• • The

• • The most recent Pisa BDT value (currently version 7)

• • The version 5 Pisa BDT value.

• • The

• • The

• • The

• • The

• • The

• • The

• • The

Tracker

• • The

• • The number of tracker track in the event.

• • The number of 2D(xy)-hits in the track.

• • The number of hits in the track.

• • The tracker hits pattern in the track. Bit 0~8: layer1 to layer9

• • The 2D hit pattern in the track. Bit 0~8: layer1 to layer9

• • The

• • The

• • The

• • The

• • The

• • The reconstructed regidity for different tracker hit pattern: 0: inner, 1: maxspan, 2:inner+L1, 3:inner+L9, 4:inner upper half, 5: inner lower half. The rigidities are obtained from fitid returned from TrTrackR::iTrTrackPar() with fit pattern 3, 0, 5, 6, 1, 2.

• • The error of rigidity fitting. Index convention is the same as trk_rig[]

• • The rigidity calculated with Alcaraz method.

• • The tracker fitting chi2 on x projection

• • The tracker fitting chi2 on y projection

• • The chi2 given opposite rigidity sign in fitting.

• • The tracker fitting residual on layer 1 with different fitting pattern, on x and y.

• • The tracker fitting residual on layer 1 with different fitting pattern, on x and y.

• • The tracker charge calculated from inner tracker.

• • The RMS of inner tracker charge.

• • The tracker charge using layer 2 to layer 4

• • The tracker charge using layer 5 to layer 8

• • The tracker charge on each layer.

• • The coordinate of tracker extrapolate to ECAL entry (Z=-143.2cm)

• • The coordinate of tracker extrapolate to ECAL exit (Z=-158.92cm)

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The (external) alignment difference on layer 1 and 9, with x, y, z value in centimeter.

• • The same as above, but this is the average value in one second (from RTI)

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

TOF

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The BetaH reconstruction pattern. In short, 4444 means very good reconstruction. See BetaHR::GetBetaPattern().

• • The number of layers used in tof_qh reconstruction.

• • The

• • The

• • The

• • The TOF charge

• • The

• • The

• • The TOF betaH coordinate fitting Chi2.

• • The TOF BetaH time fitting Chi2.

• • The

• • The

• • The

• • The

• • The

TRD

• • The selected TrdTrack id

• • The selected TrdHTrack id

• • The

• • The number of total TRD hits

• • The number of TRD segments

• • The charge estimated from TRD track

• • The number of recorded trd hits.

• • The amplitude of recorded (max 300) trd hits.

• • The tube id of recorded (max 300) hits.

• • The (historical) combined number of TRD tracks: trd_nhtrd/100: number of TrdTrack. trd_nhtrd%100: number of TrdHTrack.

• • The number of hits used in likelihood calculation for inner(0), maxspan(1) and trd refit(2)

• • Then umber of off-track(nearby) hits used in likelihood for inner(0), maxspan(1) and trd refit(2)

• • The (tracker) fit code used in likelihood calcluation for inner(0) and maxspan(1) .

• • The TRD likelihood from inner(0), maxspan(1) and trd refit(2) track position (1st dimension) and for electron(0), proton(1) and helium(2) particle (2nd dimension), calculated from rigidity.

• • The TRD likelihood ratio from inner(0), maxspan(1) and trd refit(2) track postion (1st dimension) and for e/p(0), e/He(1), p/He(2) ratios (2nd dimension), calculated from rigidity.

• • The likelihood ratio calculated from ECAL energy estimation.

• • The theta of TRD track.

• • The

• • The

• • The

• • The

• • The trds likelihood estimation (Aachen version) for e/p, e/He, p/He ratios.

• • The

• • The

RICH

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

• • The

Comments:

Introduction

• Int_t info_evvalid
  • There are valid values in the event info values if valid==0.
• UInt_t info_run

• • The
• Float_t lvl1_ftrate
  • The

• Int_t ecal_ish
  • The selected shower id.
• Int_t ecal_nsh

• • The
• Float_t ecal_nchi2
  • The

• Int_t trk_itrk
  • The
• Int_t trk_ntrk

• • The
• Float_t trk_layresy[9][2]
  • The

• Int_t tof_ibeta
  • The
• Int_t tof_ibetah

• • The
• Int_t tof_nclslay_2nd[4]
  • The

• Int_t trd_itrd
  • The selected TrdTrack id
• Int_t trd_ihtrd

• Int_t trd_nhtrd
  • The (historical) combined number of TRD tracks: trd_nhtrd/100: number of TrdTrack. trd_nhtrd%100: number of TrdHTrack.
• Int_t trd_nhits[3]

• Int_t trd_offhits[3]

• Int_t trd_fitcode[3]

• Float_t trd_kraw[3][3]

• Float_t trd_klkhd[3][3]

• Float_t trd_klkhd_e[3][3]
  • The likelihood ratio calculated from ECAL energy estimation.
• Float_t trd_theta

• • The
• Float_t trd_asye
  • The

• Int_t rich_inv
  • The
• Int_t rich_jjok

• Float_t rich_empnt[3]
  • The

Introduction

• • The number of recorded trd hits.
• Float_t trd_hitamp[300] //[td_nhitsR]
  • The amplitude of recorded (max 300) trd hits.

• • The tube id of recorded (max 300) hits.
• Int_t trd_nhtrd
  • The (historical) combined number of TRD tracks: trd_nhtrd/100: number of TrdTrack. trd_nhtrd%100: number of TrdHTrack.

• • The
• Int_t trd_fitcode[3]
  • The

• Float_t trd_klkhd[3][3]
  • The TRD likelihood ratio from inner(0), maxspan(1) and trd refit(2) track postion (1st dimension) and for e/p(0), e/He(1), p/He(2) ratios (2nd dimension).

• Float_t trd_klkhd_e[3][3]

• Float_t trd_theta
  • The theta of TRD track.
• Float_t trd_phi

Introduction

The "mn" version of ntuple is designed for keeping as a general ntuple for AMS analysis, therefore it is keeping as much information as possible. The anverage size for a typical run would be about 300MiB, and total size for 5 year data would be 40TiB.

• bit 0(0x1): fullspan only
• bit 1(0x2): above 30GeV
• bit 2(0x4): positive prescale
• bit 3(0x8): shower event only

Now The data is stored on NAS at

Variable desciption

• Float_t info_cf
  • The other Stormer cutoff stored in the event.
• Int_t info_btres

• Float_t info_theta
  • The
• Float_t info_phi

• Int_t lvl1_valid
  • The level1 trigger variables is valid (==0).
• Int_t lvl1_JMembPatt

• Int_t lvl1_PhysBPatt

• Int_t lvl1_JMembPattMC
  • The
• Int_t lvl1_PhysBPattMC

• Int_t trk_b_corrflag[6]
  • The
• Float_t trk_rig[6]

• Float_t trk_rigerr[6]
  • The error of rigidity fitting. Index convention is the same as trk_rig[]
• Float_t trk_rig_al[6]

• Int_t tof_match
  • The
• Int_t tof_patth

• Int_t tof_nlay
  • The number of layers used in tof_qh reconstruction.
• Int_t tof_nclus

• Short_t trd_tubeid[300]//[td_nhitsR]
  • The tube id of recorded (max 300) hits.
• Int_t trd_nhtrd

• Int_t trd_nhits[3]
  • The
• Int_t trd_offhits[3]

Introduction

The "mn" version of ntuple is designed for keeping as a general ntuple for AMS analysis, therefore it is keeping as much information as possible. The anverage size for a typical run would be about 300MiB, and total size for 5 year data would be 40TiB.

Introduction

Variable desciption