Difference between revisions of "Mattione Update 09042013"

From GlueXWiki
Jump to: navigation, search
(π+)
(π+)
Line 128: Line 128:
 
|-
 
|-
 
! Track Candidates
 
! Track Candidates
| [[Image:Mattione_Update_09042013_Efficiency_Candidates_n3pi_PiPlus_Current.png|left|350px]] || [[Image:Mattione_Update_09042013_Efficiency_Candidates_n3pi_PiPlus_Spiral.png|left|350px]] || [[Image:Mattione_Update_09042013_EfficiencyDiff_Candidates_n3pi_PiPlus.png|left|350px]] ||  
+
| [[Image:Mattione_Update_09042013_Efficiency_Candidates_n3pi_PiPlus_Current.png|left|300px]] || [[Image:Mattione_Update_09042013_Efficiency_Candidates_n3pi_PiPlus_Spiral.png|left|300px]] || [[Image:Mattione_Update_09042013_EfficiencyDiff_Candidates_n3pi_PiPlus.png|left|300px]] ||  
[[Image:Mattione_Update_09042013_EfficiencyDiffZoomed_Candidates_n3pi_PiPlus.png|left|350px]]
+
[[Image:Mattione_Update_09042013_EfficiencyDiffZoomed_Candidates_n3pi_PiPlus.png|left|300px]]
 
|-
 
|-
 
! Time-Based Tracks
 
! Time-Based Tracks
| [[Image:Mattione_Update_09042013_Efficiency_TimeBased_n3pi_PiPlus_Current.png|left|350px]] || [[Image:Mattione_Update_09042013_Efficiency_TimeBased_n3pi_PiPlus_Spiral.png|left|350px]] || [[Image:Mattione_Update_09042013_EfficiencyDiff_TimeBased_n3pi_PiPlus.png|left|350px]] ||  
+
| [[Image:Mattione_Update_09042013_Efficiency_TimeBased_n3pi_PiPlus_Current.png|left|300px]] || [[Image:Mattione_Update_09042013_Efficiency_TimeBased_n3pi_PiPlus_Spiral.png|left|300px]] || [[Image:Mattione_Update_09042013_EfficiencyDiff_TimeBased_n3pi_PiPlus.png|left|300px]] ||  
[[Image:Mattione_Update_09042013_EfficiencyDiffZoomed_TimeBased_n3pi_PiPlus.png|left|350px]]
+
[[Image:Mattione_Update_09042013_EfficiencyDiffZoomed_TimeBased_n3pi_PiPlus.png|left|300px]]
 
|}
 
|}
 
<br style="clear:both;"/>
 
<br style="clear:both;"/>

Revision as of 21:03, 3 September 2013

CDC Track Finding

Single π+ Track

Single π+ Reconstruction: Current (Trunk) Code, trackeff_hists plugin

  • The below plots show the track reconstruction efficiency and resolution for the trunk using the single-track scripts plugin (trackeff_hists).
  • However, this efficiency is extremely misleading:
    • If a track is reconstructed using any of the hits that were on the thrown track it is considered "found."
    • This is regardless of whether the reconstructed track momentum is anywhere close to the thrown values.
Current Code: Time-Based Tracks (trackeff_hists plugin)
Current Code: Momentum Resolution (trackeff_hists plugin)

Single π+ Reconstruction: Current (Trunk) Code, NEW trackeffv2 plugin

  • The below plots show the track candidate and time-based track reconstruction efficiency for the trunk using a new plugin (trackeff_hists).
  • This plugin compares matches all of the thrown and reconstructed particles in the event, and requires that their momentum be "close."
    • "Close" for track candidates is defined as: Δp/p < 20%, Δθ < 40 degrees, Δφ < 40 degrees, ΔVertex-Z < 1 km
      • For thrown tracks with θ < 5 degrees, there is no cut on the candidate Δφ
    • "Close" for time-based tracks is defined as: Δp/p < 10%, Δθ < 15 degrees, Δφ < 15 degrees, ΔVertex-Z < 10 cm
Current Code: Track Candidates (trackeffv2 plugin)
Current Code: Time-Based Tracks (trackeffv2 plugin)
  • Note that the degradation of the efficiency at forward angles matches the track resolution plot in the previous section.
    • If I expand the requirements for the "Close" window, the efficiency increases, and the chosen parameters were somewhat arbitrary.

Single π+ Reconstruction: NEW Spiral Code

  • The below plots show the track candidate and time-based track reconstruction efficiencies for the new spiral code.
  • Note: The trackeffv2 plugin compares matches all of the thrown and reconstructed particles in the event, and requires that their momentum be "close."
    • "Close" for track candidates is defined as: Δp/p < 20%, Δθ < 40 degrees, Δφ < 40 degrees, ΔVertex-Z < 1 km
      • For thrown tracks with θ < 5 degrees, there is no cut on the candidate Δφ
    • "Close" for time-based tracks is defined as: Δp/p < 10%, Δθ < 15 degrees, Δφ < 15 degrees, ΔVertex-Z < 10 cm
Spiral Code: Track Candidates Efficiency (Spiral Code)
Spiral Code: Time-Based Track Efficiency (Spiral Code)
  • The below plots show the improvements in the track candidate and time-based track reconstruction efficiencies with the new spiral code.
Track Candidate Efficiency Improvement
Zoomed Track Candidate Efficiency Improvement
Time-Based Track Efficiency Improvement
Zoomed Time-Based Track Efficiency Improvement


γp→π+π+π-(n)

  • The below plots show the track candidate and time-based track reconstruction efficiencies for both track finding codes, and the improvement.
  • The definition of closeness is the same as before (see the single-track section).
  • Events were generated at beam energy of 9 GeV and a t-slope of 5.0

π+

Thrown π+'s


Stage Efficiency - Current Code Efficiency - Spiral Code Improvement Improvement - Zoomed
Track Candidates
Mattione Update 09042013 Efficiency Candidates n3pi PiPlus Current.png
Mattione Update 09042013 Efficiency Candidates n3pi PiPlus Spiral.png
Mattione Update 09042013 EfficiencyDiff Candidates n3pi PiPlus.png
Mattione Update 09042013 EfficiencyDiffZoomed Candidates n3pi PiPlus.png
Time-Based Tracks
Mattione Update 09042013 Efficiency TimeBased n3pi PiPlus Current.png
Mattione Update 09042013 Efficiency TimeBased n3pi PiPlus Spiral.png
Mattione Update 09042013 EfficiencyDiff TimeBased n3pi PiPlus.png
Mattione Update 09042013 EfficiencyDiffZoomed TimeBased n3pi PiPlus.png


γp→π+π+π-π-π0(p) (b1pi)

bggen (pythia)

γp→K+K+Ξ-