- 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
Material distribution from GEANT geometry : HFT, run14
Use StarVMC/StarBASE to make plots (1D,2D) of radiation lengths per volume
preliminary check for the parameters with which the geantinos are thrown.
The eta and phi bin, as well as the # of geantinos per bin can be changed.
1) Default parameters.
Geantinos are thrown according :
Explanation of the Y-axis
setup is now
The number of entries makes sense : 4 (bin eta * range eta) * 360 (bin phi * range phi) *4 (# of geantinos) = 5760
Going back to the initial setup :
Fig 4 : deta=0.1 , dphi =1
preliminary check for the parameters with which the geantinos are thrown.
The eta and phi bin, as well as the # of geantinos per bin can be changed.
1) Default parameters.
Geantinos are thrown according :
const Float_t eta_min = -6.0; // min pseudorapidity const Float_t eta_max = +6.0; // max pseudorapidity const Float_t deta = .1; // size of etabin const Float_t phi_min = -180.000; // min phi (in degrees) const Float_t phi_max = +180.000; // max phi (in degrees) const Float_t dphi = 1; // size of phibin (in degrees) const Float_t nsample = 4.0; // number of tracks / bin
Fig 1: rad length vs. phi (degree), z[cm], radius [cm], radius vs phi for PXL (PXMO) volume
Resolution is not good because it depends on the histograms binning too.
Explanation for the left plot of Fig1
Fig 2 : breakdown for PXMO volume
Resolution is not good because it depends on the histograms binning too.
Explanation for the left plot of Fig1
Fig 2 : breakdown for PXMO volume
- left : total radiation length per phi bin (with an eta bin = 0.1)
- middle : # of geantinos per phi bin (with an eta bin = 0.1)
- rigth : ratio left/middle
Explanation of the Y-axis
setup is now
const Float_t eta_min = -6.0; // min pseudorapidity
const Float_t eta_max = +6.0; // max pseudorapidity
const Float_t deta = 3; // size of etabin
const Float_t phi_min = -180.000; // min phi (in degrees)
const Float_t phi_max = +180.000; // max phi (in degrees)
const Float_t dphi = 1; // size of phibin (in degrees)
const Float_t nsample = 4.0; // number of tracks / bin
Fig 3 : deta=3, dphi=1The number of entries makes sense : 4 (bin eta * range eta) * 360 (bin phi * range phi) *4 (# of geantinos) = 5760
Going back to the initial setup :
Fig 4 : deta=0.1 , dphi =1
Groups:
- bouchet's blog
- Login or register to post comments