- bouchet's home page
- Posts
- 2016
- 2015
- December (1)
- November (3)
- October (2)
- September (2)
- August (2)
- June (2)
- April (5)
- March (2)
- February (3)
- January (2)
- 2014
- December (2)
- November (2)
- October (3)
- September (2)
- August (3)
- July (1)
- June (3)
- May (6)
- April (6)
- March (1)
- February (2)
- January (1)
- 2013
- December (2)
- November (3)
- October (3)
- September (4)
- August (1)
- July (1)
- May (4)
- April (6)
- March (4)
- February (3)
- 2012
- 2011
- December (2)
- November (2)
- October (4)
- September (1)
- August (2)
- July (6)
- June (2)
- May (3)
- April (3)
- March (2)
- 2010
- 2009
- December (2)
- November (1)
- October (3)
- September (1)
- August (1)
- July (1)
- June (2)
- April (1)
- March (2)
- February (2)
- January (1)
- 2008
- My blog
- Post new blog entry
- All blogs
PXL : tracking efficiency in overlapping areas
PXL Geometry for Y2013 : 3 sectors.
Example of tracks with more than 2 PXL hits due to the overlap between 2 outers ladders is show below.
a) simulation setup
Example of tracks with more than 2 PXL hits due to the overlap between 2 outers ladders is show below.
- straight lines in red are for vertex Z = 0 cm
- even for a slighly shift in vertex Z, we can never have tracks with 4 PXL hits in that case (should consider curvated tracks)
a) simulation setup
- 400 events
- 50 pions/event
- 0.1<Pt <5.0
- |η|<1
- 0<Φ<2π
detp geom y2013 gexec .$STAR_HOST_SYS/lib/xgeometry.so gclose all user/vxyz 0.001 0.001 0.01 user/vsig 0.01 0.1 gfile o debug66.fz aguser/gkine 50 8 0.1 5.0 -1.0 1.0 0 6.28 trig 400
The numbers of TPC and PXL hits used in fit ( per global track ) is counted via StGlobalTrack :
comments :
tTree.pt = gTrack->geometry()->momentum().perp(); tTree.tpc = gTrack->fitTraits().numberOfFitPoints(kTpcId); tTree.pxl = gTrack->fitTraits().numberOfFitPoints(kPxlId);
The following histograms shows the PXL hits distribution for this sample (21914 global tracks)
The number of tracks with 3 PXL hits (overlap btw ladders) is 226, which makes a ratio of = 226/21914 ~ 1%
The number of tracks with 3 PXL hits (overlap btw ladders) is 226, which makes a ratio of = 226/21914 ~ 1%
2) tracking efficiency for tracks having 3 PXL hits
a) simulation setup
b) results
a) simulation setup
- 5000 events
- 1 muon/event
- Pt =1.0 GeV/c
- |η|<1
- 1.80<Φ<1.82
detp geom y2013 gexec .$STAR_HOST_SYS/lib/xgeometry.so gclose all user/vxyz 0.001 0.001 0.01 user/vsig 0.01 0.1 gfile o singlemuon_overlap.fz aguser/gkine 1 5 1.0 1.0 -1.0 1.0 1.80 1.82 trig 5000
b) results
file : output_Ana.root
# events : 5000
# events with PXL hits =0 or >3 : 104
# events with PXL hits =1 : 114
# events with PXL hits =2 : 2842
# events with PXL hits =3 : 1940
# events with PXL hits used =3 for PXL hits =3 : 1845
root4star [2] 1845./1940
(const double)9.51030927835051498e-01
- the current version of the tracking (Sti) seems to not complain for overlapping areas (issues could have been that the tracker expects 2 PXL hits and sometimes finds more)
- Sti still uses 8microns for the PXL hit resolution (not sure if it's a real issue here given the very low track density)
Groups:
- bouchet's blog
- Login or register to post comments