Update on Secondaries and Backtracking Validation

1
Update on Secondaries and Backtracking Validation
Bruce Schumm UC Santa Cruz February 22, 2008
Inner Detector Software Meeting
2
Keeping Statistics on Secondaries
Nomenclature Particle MC object. Secondaries
are non-prompt particles. Track Reconstructed
pattern in detector, may or may not be clearly
associated with a particle Most reconstructed
tracks are not due to secondary particles ?
generally doesnt make sense to calculate
fraction of tracks due to secondaries It is
useful to ask what fraction of secondaries are
reconstructed, and properties of associated tracks
3
Definition of Secondary Particle
We have defined a secondary as a particle that
originates at a displaced location with
either 25mm lt r lt 360mm 200mm lt z lt
2000mm but also, the secondary must terminate
with r gt 1000mm or z gt 2300 mm We use the usual
? boundaries of Barrel 0 lt ? lt
0.8 Transition 0.8 lt ? lt
1.6 Endcap 1.6 lt ? lt 2.5
4
Sample Secondaries Statistics
Statistics for Secondary Tracks TrackCollection
"ConvertedXKalmanTracks" (TrackAuthors
xKalmanLegacyCnv ), TrackTruthCollection
"ConvertedXKalmanTracksTruth"
...................tracks.....................
........... ................................
......hits/track. n/event
eff. total PIX1 PIX2 PIX3
SCT1 SCT2 SCT3 SCT4 SCT5to9 Straws
total 3.90 0.45 15.5
0.11 0.13 0.24 0.87 0.87
0.84 0.80 0.31 11.36 in
barrel 2.20 0.59 22.6
0.11 0.11 0.35 1.24 1.27
1.27 1.22 0.00 17.03 in
trans. 1.10 0.42 13.8
0.08 0.15 0.19 1.15 0.88
0.69 0.42 0.00 10.23 in
endcap 0.60 0.32 8.3 0.21
0.16 0.16 0.00 0.32 0.42
0.74 1.42 4.84
..................................................
..................................................
....................................
TrackCollection "ConvertedIPatTracks"
(TrackAuthors iPatLegacyCnv iPatLegacyCnvBremFit
), TrackTruthCollection "ConvertedIPatTracksTruth"
...................tracks
................................
......................................hits/track..
n/event eff.
total PIX1 PIX2 PIX3 SCT1 SCT2
SCT3 SCT4 SCT5to9 Straws total
3.60 0.41 15.1 0.06
0.08 0.21 0.85 0.84 0.83
0.76 0.22 11.26 in barrel
2.10 0.57 23.1 0.03 0.08
0.30 1.22 1.27 1.32 1.24
0.00 17.59 in trans. 1.00
0.38 12.4 0.04 0.08 0.15
1.12 0.81 0.65 0.42 0.00
9.12 in endcap 0.50 0.26
7.3 0.16 0.11 0.16 0.00
0.26 0.32 0.47 1.00
4.84 ............................................
..................................................
.........................................
We have yet to include this in the default
InDetRecStat output, but plan to soon.
5

Under Development automated BackTrackRTT package
based on the InDetRecStat ntuple1
1 We will shortly have a discussion about merging
InDetRecStat and TrkValidation
6

• For now, using ResolvedTRTSeededTracks (require
  track parameter fit for residuals, fake rates, so
  cant use more efficiency TRTSeededTracks).
• Developing two validation samples
• Et 20 GeV Gamma Conversions
• Pt 10 GeV KS0 decays
• Initial analysis script is modest
• residuals
• hit distributions
• efficiencies
• fake rates.

7
Defining trackable tracks
For non-prompt tracks, include zexit and rorg
as performance parameters, along with p? and ?.
8
Tracking effic-iency vs. pt and vs. rorg may be
most interesting (use pt cut of 1 GeV/c for all
but pt distribution, and zexit cut of 3000).
9
(No Transcript)
10
P?
P?
All Findable Particles
Missed by Backtracking
?
?
All Findable Particles
Missed by Backtracking
11
Back to validation
As mentioned, need to explore inclusion of TRT
segments in InDetRecStat Thoughts about
Validation Material Current data files single
muon, multi muon, Z ? ?? all probably
useful. Might add 20 GeV photons for monitoring
coversion recovery. Thinking still nascent and
we are open to suggestions.