- 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
new IST code
I run the bfc chain with the new version of StiIstDetectorBuilder from Willie.
library : starnew
bfc chain : trs,ssd,upgr15,pixFastSim,Idst,IAna,l0,tpcI,fcf,Tree,logger,ITTF,Sti,StiRnd,PixelIT,IstIT,StiPulls,genvtx,NoSvtIt,SsdIt,MakeEvent,McEvent,geant,evout,IdTruth,bbcSim,emcY2,EEfs,big,-dstout,fzin,-McEvOut,clearmem,MiniMcMk,McAss,McAna
file :/star/institutions/emn/bouchet/newGeom/100Ev_800pionsplus.fzd
It has 800 pions + per event with :
- 0.1 < pT < 5.0
- |eta| <1
- 0< phi <2*pi
- |z| <30 cm
- vertex at 0.0.0.
section 1 :
I used a StAnalysisMaker to fill the events characteristics, such as number of TPC,SSD,pixel and IST hits, good globals and primaries.
It has minimal cuts :
- |z_vertex| < 10 cm
- NTpcFit >15
From this, I plotted next the r/phi vs Z positions of hits used in tracking
I have, after cuts, 69176 tracks.
The following table describes the tracks population (per detector)
ssd | ist | pixel | percentage |
0 | 0 | 0 | 0.0699 |
0 | 1 | 0 | 0 |
0 | 0 | 1 | 0.0037 |
0 | 0 | 2 | 0.0013 |
0 | 1 | 1 | 0.0108 |
0 | 1 | 2 | 0.1151 |
1 | 0 | 0 | 0.0016 |
1 | 1 | 0 | 0.0022 |
1 | 0 | 2 | 0.0013 |
1 | 0 | 1 | 0.0064 |
1 | 1 | 1 | 0.0363 |
1 | 1 | 2 | 0.7543 |
Section 2 :
From the output of the job, i used the MuDst.root file.
I modified the macro from Yuri (MuSvt) to run over this file : basically, it loops over primary tracks (after cuts selection) and we can plot some properties of the StMuTrack class, such as the number of possible, fitted hits.
I also used this macro to plot the dca resolution (in xy and Z) vs 1/P.
The possible and fitted hits are accessible via :
- Int_t NoFIstHits = (mNHitsFitInner[k] & 0x7);
- Int_t NoFSsdHits = ((mNHitsFitInner[k] >> 3) & 0x3);
- Int_t NoPIstHits = (mNHitsPossInner[k] & 0x7);
- Int_t NoPSsdHits = ((mNHitsPossInner[k] >> 3) & 0x3);
- Int_t NoFPxlHits = ((mNHitsFitInner[k] >> 5) & 0x7);
- Int_t NoPPxlHits = ((mNHitsPossInner[k] >> 5) & 0x7);
Fig 3 : pixel
An estimation for each detector consists to take the ratio of tracks having NPossible = NFitted over all tracks for NPossible_expected to respect with this detector
ssd | ist | pixel | |
NPossible_expected | 1 | 1 | 2 |
NPossible = NFitted | 49904 | 62132 | 60662 |
All tracks for NPossible_expected | 59035 | 65517 | 65291 |
Efficiency (%) | 84.5 | 94.8 | 92.9 |
Remember that I used the slow simulator for the SSD, it may explain the lower efficiency compared to the ist and pixel.
Finally, I plotted the dca resolution in XY and Z direction
Fig 4 : sigma_dca_xy vs 1/p
Fig 5 : sigma_dca_z vs 1/P
At P = 1 GeV/c, the dca resolution is XY and Z is less than 25 um for tracks having 1 ssd hit + 1 ist hit + 2 pixel hits.
section 3 :
I tried to run with the latest library (SL08e)
The following plots are the number of Possible hits vs. the number of fitted hits for ssd, ist and pixel detectors.
I used the same macros (then same cuts) as in section 2 (where it was with SL08d)
Fig. 6 : ssd
Fig. 7 : ist
Fig. 8 : pixel
The differences between SL08e and SL08d are :
- number of tracks with SL08d : 70035
- number of tracks with SL08e : 70022
However, the distribution look the same
- bouchet's blog
- Login or register to post comments