- 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
run14 simulation
TEST :
- look at the tracking efficiency with PXL, using code in CVSROOT (StiPxl)
- sample : 1 muon /event, fixed Pt and phi ~ pi (even with misaligned PXL, 1 track per event should allow the PXL hits to be taken most of the time)
- loop over global track and plot the # of PXL hits on track via
-
gTrack->fitTraits().numberOfFitPoints(kPxlId);
detp geometry y2014 gexec $STAR_LIB/xgeometry.so make gstar gclose all myPID = 5 utime=$SHELL('date +%s') Rndm [utime] [myPID] user/vxyz 0.01 0.01 0.1 user/vsig 0.01 5 gfile o test_muon.fz aguser/gkine 1 5 1.0 1.0 -1.0 1.0 1.3 1.6 trig 1000
BFC chain :
"tpcRS ry2014 AgML MakeEvent ITTF VFMCE pxlFastSim pxlDb pxlUtil PixelIt NoSsdIt NoSvtIt Idst BAna l0 Tree logger Sti tpcDB TpcHitMover TpxClu bbcSim btofsim tags emcY2 EEfs evout -dstout IdTruth geantout big fzin MiniMcMk clearmem"note :
the BFC chain has been updated friday (April 11th) with a dedicated option : StiLibsHft ; this option calls StiPxl.
I used PixelIT in this chain : PixelIT calls PxlIT which calls StiPxl, so it should be fine.
Results (over 100 events) :
Fig 1 : PXL hits from PxlHitCollection (all hits, no tracking here)
Fig 2 : TPC hits in tracking distribution : over 100 tracks, 92 are passed after cuts ; distribution looks ok
Fig 3 : PXL hits in tracking distribution : most of the tracks have 0 PXL hits, only 2 tracks have 1 PXL hit, 1 track with 2 PXL hits
Previous Simulation :
similar study with y2013 geometry and StiRnD code : here
update :
backtracked to the version where StiVolumes are build per ladder :
- when sensor !=1, do not build the volume
- Set the length in Z of the Sti Volumes to 10*TGeoBBox->GetDZ()
- Set the position in Z at 0
- old numbering : inner ladders from 0 to 9, outer ladders from 0 to 30
- same numbering in StiPxlHitLoader
modif 1 : with 1) and 2)
modif 2 : with 1), 2) and 3) from the above list
# of PXL hits / track | 0 | 1 | 2 | 3 |
CVSROOT | 16 | 1 | 0 | 0 |
modif 1 | 7 | 5 | 5 | 0 |
modif 2 | 2 | 3 | 11 | 2 |
update (2)
Simulation is :
detp geometry y2014 gexec $STAR_LIB/xgeometry.so make gstar gclose all myPID = 8 utime=$SHELL('date +%s') Rndm [utime] [myPID] user/vxyz 0.01 0.01 0.1 user/vsig 0.01 5 gfile o test_pion.fz aguser/gkine 20 8 0.1 5.0 -1.0 1.0 0 6.28 trig 100
Fig 4 : (# of tracks with PXL >0) / (# of all tracks) vs pt
efficiency -> .8 (both numerator and denominator have a cut TPC>15)
Fig 5 : same of as Fig 4 but both numerator and denominator have a cut |eta|<.5
efficiency -> .85
efficiency -> .8 (both numerator and denominator have a cut TPC>15)
Fig 5 : same of as Fig 4 but both numerator and denominator have a cut |eta|<.5
efficiency -> .85
Groups:
- bouchet's blog
- Login or register to post comments