Checking different tracking algorithms with a di m sample

12
Checking different tracking algorithms with a di sample Start with sample of p11.11 data on SAM recoA_reco_dimuon_third_merged%tk-p11.11-%.root Look at the six different algorithms: (gtr,htf,gtrela,htfela,gtrhtf,aa) Sample has ~30K events / algorithm (gtrela has 21K, htfela has 28K) Ran each algorithm sample through the exact same analysis macros Do fits and compare to known values Observations Ryan J. Hooper (University of Notre Dame: Ryan J. Hooper (University of Notre Dame: 25 25 , , UofM: UofM: 23 23 ) )

description

Checking different tracking algorithms with a di m sample. Ryan J. Hooper (University of Notre Dame: 25 , UofM: 23 ). Start with sample of p11.11 data on SAM recoA_reco_dimuon_third_merged%tk-p11.11-%.root Look at the six different algorithms: ( gtr,htf,gtrela,htfela,gtrhtf,aa ) - PowerPoint PPT Presentation

Transcript of Checking different tracking algorithms with a di m sample

Checking different tracking algorithms with a di sample

Start with sample of p11.11 data on SAM

recoA_reco_dimuon_third_merged%tk-p11.11-%.root

Look at the six different algorithms: (gtr,htf,gtrela,htfela,gtrhtf,aa)

Sample has ~30K events / algorithm (gtrela has 21K, htfela has 28K)

Ran each algorithm sample through the exact same analysis macros

Do fits and compare to known values

Observations

Ryan J. Hooper (University of Notre Dame: Ryan J. Hooper (University of Notre Dame: 2525, , UofM: UofM:

2323))

J/Psi eV

= 5 keV

gtr htf gtrela htfela gtrhtf aa# Events 2913 3038 2879 4067 4029 2853Mass (MeV) 3067 ±± 5 3072 ±± 4 3135 ±± 7 3091 ±± 5 3071 ±± 4 3204 ±± 6

eV 109 ±± 33 105 ±± 33 155 ±± 5 121 ±± 3 102 ±± 3 135 ±± 4

“Tight” Muons matched ( to Gtr401@DCA tracks (“Gavin’s” Matching)

Matching requires both tracks to have pT > 2.5 GeV

Track nhits > 11

Fit peak with Gaussian + Linear BK

J/Psi

J/Psi

Upsilon 1SeV

1S) = 1.3 keV

gtr htf gtrela htfela gtrhtf aa# Events 2913 3038 2879 4067 4029 2853Mass (MeV) 9375 ±± 53 9381 ±± 50 9514 ±± 50 9472 ±± 43 9374 ±± 44 9748 ±± 64

MeV 454 ±± 3377 454 ±± 3399 453 ±± 36 400 ±± 34 402 ±± 36 459 ±± 50

“Tight” Muons matched ( to Gtr401@DCA tracks (“Gavin’s” Matching)

Require both tracks to have pT > 2.5 GeV

Track nhits > 11 (SAME CUTS AS J/PSI !)

Fit peak with Gaussian + Linear BK

Upsilon

Upsilon

Z GeV

= 84 MeV

gtr htf gtrela htfela gtrhtf aaTotal#Events

43 33 30 46 52 32# Events inmass window(72-112 GeV)

24 20 18 29 31 21Mass (GeV) 93.1 ±± 3.5 90.9 ±± 3.3 90.2 ±± 6.3 92.2 ±± 2.1 93.1 ±± 2.2 92.6 ±± 4.0

GeV 9.4 ±± 33..00 6.0 ±± 22..11 11.4 ±± 4.8 6.3 ±± 1.5 6.8 ±± 1.7 6.5 ±± 0.07

“Tight” Muons matched ( to Gtr401@DCA tracks (“Gavin’s” Matching)

Match requiring both tracks to have pT > 2.5 GeV

Track nhits > 11…...Then require both tracks to have pT > 15 GeV!!!

Fit peak to a Gaussian + Linear BK

Z

Z

ObservationsThree different resonances were look at J/Psi, Upsilon and Z

Saw a few events that might have some duplication of tracks or some other strange behavior ???

Run: 152415 152420

Event: 532207 1033338

gtr htf gtrela htfela gtrhtf aaFor J/Psi: from PDG

7.5 6.25 5.4 1.2 6.5 17.8For Upsilon: from PDG

1.6 1.6 1.1 0.3 2.0 4.5For Z: from PDG

0.55 0.09 0.15 0.48 0.87 0.35

Observations (cont.)

At lower masses the aa and gtrela algos seemed to over measure the mass while gtrhtf, htf and gtr appears to under measure!

Overall the htfela algorithm looked to perform the best over all the mass scales !