Difference: RadiusDependency (1 vs. 3)

Revision 32009-03-25 - PitVanhoefer

Line: 1 to 1
 
META TOPICPARENT name="SuperBelleOptimization"
Changed:
<
<

Radius Dependency

>
>

Radius Dependency of the Vertex Detector

 
Changed:
<
<
The dependency of the performance of the vertex_detecor on its radius is studied by using the ILC framework modified for BELLE. Therefore several single muon events were generated with Mokka, using a detector model which consists of a beampipe, a Central Drift Chamber and a 6 layer Vertex-detector (two pixel (thickness 0.05mm) and 4 strip(0.3mm; radius[mm] 45, 70, 100, 138) in ladder structure, which distinguish only in their geometrical features) while the radius of the pixel detector (the first two inner layers) was varied.
>
>
The dependency of the performance of the vertex_detecor on its radius is studied by using the ILC framework modified for BELLE. Therefore several single muon events were generated with Mokka, using a detector model (DetectorModels) which consists of a beampipe, a Central Drift Chamber and a 6 layer Vertex-detector (two pixel (thickness 0.05mm) and 4 strip(0.3mm; radius[mm] 45, 70, 100, 138) in ladder structure, which distinguish only in their geometrical features) while the radius of the pixel detector (the first two inner layers) was varied.
 The first radius runs from 12mm to 26mm in 1mm steps, the second is always three mm larger. Other parameters which are varied are: Energy(0.2 GeV - 2 GeV) and shooting angle (theta: 20degree - 80degree; in 20 degree steps; phi:0 - 2pi homogeneous smeared).
Changed:
<
<
The digitization, reconstruction and analysis is done with Marlin using the following processors: MyMaterialDB, VTXDigitizer, TPCDigiProcessor, CurlKillerProcessor, TrackCheater, LEPTrackingProcessor, SiliconTracking, FullLDCTracking, MarlinVertex2.
>
>
The digitization, reconstruction and analysis is done with Marlin using the following processors:
PROCESSORS
MyMaterialDB
VTXDigitizer
TPCDigiProcessor
CurlKillerProcessor
TrackCheater
LEPTrackingProcessor
SiliconTracking
FullLDCTracking
MarlinVertex2
 
Changed:
<
<
We take a look at the resolution of the track-parameter d0 (the point of closest approach in the R-phi plane) of reconstructed tracks as measurement of the performance.
>
>
We take a look at the resolution of the track-parameter d0 (the point of closest approach in the R-phi plane, ImpactParameterResolution) of reconstructed tracks as measurement of the performance.All plots show the rms (from the histogramm, (with a 90% cut)) and/or the sigma (from tha gaussian fit) of d0.
  The result is an improvement of the resolution with a decreasing radius of the vertex detector (and also with a decreasing radius of the beampipe, see mu+diffBPradi.ps). Although the tendency is clear, the statistical error is not yet fully understood as the plot in mu+statERROR.ps indicates.

Changed:
<
<
>
>
  • mu+d0Radius.ps: Radius Dependency of d0 resolution: d0 is plotted against the radius of the inner layer of the VTX-Detector for different energies and thetas (beampipe radius is 10mm)
 
Changed:
<
<
>
>
  • mu+Radi_example.ps: example of the d0 distribution of the reconstructed track with a Gaussian fit (1. plain; 2. with a 90% cut; 3 simulated)
 
Changed:
<
<
>
>
  • mu+Energy.ps: energy dependency of the d0-resolution for different radii with fit, different thetas are merged into one plot (page 2: only the fit functions)
 
Changed:
<
<
>
>
  • mu+statERROR.ps: Error uncertainty (here a 30000 event file was splitted into three parts to compare the d0-parameter of the different parts, the two plots show the same)
 
Changed:
<
<
>
>
  • mu+diffBPradi.ps: the same as mu+d0Radius.ps but with different beampipe radii
 

Revision 22009-03-19 - KoljaProthmann

Line: 1 to 1
 
META TOPICPARENT name="SuperBelleOptimization"

Radius Dependency

Line: 15 to 15
 

Deleted:
<
<

-- PitVanhoefer - 18 Mar 2009

 

Line: 29 to 25
 
Added:
>
>

-- PitVanhoefer - 18 Mar 2009

 
META FILEATTACHMENT attr="" autoattached="1" comment="Error uncertainty" date="1237388190" name="mu+statERROR.ps" path="mu+statERROR.ps" size="17716" user="Main.PitVanhoefer" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="different beampipe radius" date="1237390729" name="mu+diffBPradi.ps" path="mu+diffBPradi.ps" size="31165" user="Main.PitVanhoefer" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Radius Dependency of d0 resolution" date="1237388456" name="mu+d0Radius.ps" path="mu+d0Radius.ps" size="36782" user="Main.PitVanhoefer" version="1"

Revision 12009-03-18 - PitVanhoefer

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="SuperBelleOptimization"

Radius Dependency

The dependency of the performance of the vertex_detecor on its radius is studied by using the ILC framework modified for BELLE. Therefore several single muon events were generated with Mokka, using a detector model which consists of a beampipe, a Central Drift Chamber and a 6 layer Vertex-detector (two pixel (thickness 0.05mm) and 4 strip(0.3mm; radius[mm] 45, 70, 100, 138) in ladder structure, which distinguish only in their geometrical features) while the radius of the pixel detector (the first two inner layers) was varied. The first radius runs from 12mm to 26mm in 1mm steps, the second is always three mm larger. Other parameters which are varied are: Energy(0.2 GeV - 2 GeV) and shooting angle (theta: 20degree - 80degree; in 20 degree steps; phi:0 - 2pi homogeneous smeared).

The digitization, reconstruction and analysis is done with Marlin using the following processors: MyMaterialDB, VTXDigitizer, TPCDigiProcessor, CurlKillerProcessor, TrackCheater, LEPTrackingProcessor, SiliconTracking, FullLDCTracking, MarlinVertex2.

We take a look at the resolution of the track-parameter d0 (the point of closest approach in the R-phi plane) of reconstructed tracks as measurement of the performance.

The result is an improvement of the resolution with a decreasing radius of the vertex detector (and also with a decreasing radius of the beampipe, see mu+diffBPradi.ps). Although the tendency is clear, the statistical error is not yet fully understood as the plot in mu+statERROR.ps indicates.

-- PitVanhoefer - 18 Mar 2009

META FILEATTACHMENT attr="" autoattached="1" comment="Error uncertainty" date="1237388190" name="mu+statERROR.ps" path="mu+statERROR.ps" size="17716" user="Main.PitVanhoefer" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="different beampipe radius" date="1237390729" name="mu+diffBPradi.ps" path="mu+diffBPradi.ps" size="31165" user="Main.PitVanhoefer" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Radius Dependency of d0 resolution" date="1237388456" name="mu+d0Radius.ps" path="mu+d0Radius.ps" size="36782" user="Main.PitVanhoefer" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="example" date="1237388681" name="mu+Radi_example.ps" path="mu+Radi_example.ps" size="27138" user="Main.PitVanhoefer" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="energy dependency for different radii" date="1237388834" name="mu+Energy.ps" path="mu+Energy.ps" size="40705" user="Main.PitVanhoefer" version="1"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback