- 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
minimc analysis
subject : Use StMiniMcTree from the bfc chain (mixed D0/D0bar + hijing, or single D0 ) to look at the differences btw true D0's and all other pairs (fake)
In particular, we want to look at the DCA of tracks to PV for true D0's and for fakes.
- true D0 are selected with :
- geant_id (track1)=8 and geant_id (track2) =12
- parentgeant_id (track1)=37 and parentgeant_id (track2) =37
- parentKey (track1) = parentKey (track2)
Some initial plots are here
- update (5/15)
Use the completed sample of Joe to make dca vs. InvPt plots
Fig1 : dcaXYGl vs 1/PtGl
from this plot, I used FitSlices to get the rms and mean
Fig2 : resolution vs 1/PtGl
Fig3 : same as Fig2 but zoomed
Fig4 : mean DCA vs 1/PtGl
Fig5 : pT distribution of true D0's and fake
- minimc files also filled the reconstructed, the primary and the MC version of kinematics variables (pt, dca,eta ...)
For example :
Float_t mMatchedPairs_mDcaXYPr[kMaxmMatchedPairs]; //[mMatchedPairs_] Float_t mMatchedPairs_mDcaZPr[kMaxmMatchedPairs]; //[mMatchedPairs_] Float_t mMatchedPairs_mDcaXYPrMcV[kMaxmMatchedPairs]; //[mMatchedPairs_] Float_t mMatchedPairs_mDcaZPrMcV[kMaxmMatchedPairs]; //[mMatchedPairs_]
which refers to :
StMiniMcMaker/StMiniMcMaker.cxx: tinyRcTrack->setDcaXYGl(computeXY(mRcVertexPos,glTrack)); StMiniMcMaker/StMiniMcMaker.cxx: tinyRcTrack->setDcaXYGlMcV(computeXY(mMcVertexPos,glTrack));
so dcaXYGl (dcaXYGlMcv) is the dca in XY with respect the reco. (MC) vertex
Fig 6 : dcaXYGlMcV vs 1/PtMc
Fig 7 : resolution vs 1/PtMc
comments : there is no obvious difference between the reco and MC branch
- same dca resolution plots but for the Z component
Fig8 : resolution (Z) vs 1/PtMc
Fig9 : comparison of dca resolution (XY) vs 1/PtGl for flat pt D0 and powerlaw pt, random vertex
black : dca resolution of pion from true D0 (in the 5D0/D0bar + hijing sample, power lat pt D0)
red : dca resolution of pion from fake D0 (in the 5D0/D0bar + hijing sample, power law pt D0)
blue : dca resolution of pion from true single D0 (flat pt)
9/25 : note on the umber of hits on minimc
tinyRcTrack->setFitPts(glTrack->fitTraits().numberOfFitPoints(kTpcId));
tinyRcTrack->setFitSvt(glTrack->fitTraits().numberOfFitPoints(kSvtId));
tinyRcTrack->setFitSsd(glTrack->fitTraits().numberOfFitPoints(kSsdId));
- bouchet's blog
- Login or register to post comments