Difference between revisions of "Mattione Update 08212013"

From GlueXWiki
Jump to: navigation, search
(Accuracy)
(Multiplicity)
Line 35: Line 35:
 
*** In theory this improves things, because with better guesses for the track momentum and position, you should be able to better select the hits along that trajectory.  
 
*** In theory this improves things, because with better guesses for the track momentum and position, you should be able to better select the hits along that trajectory.  
 
*** In practice, this can pick up many extra, unwanted hits for spiraling tracks
 
*** In practice, this can pick up many extra, unwanted hits for spiraling tracks
 +
*** Recommendation: Test with the hit selector set to ONLY reject hits, NOT to acquire new ones.
 
{| class="wikitable"
 
{| class="wikitable"
 
| [[Image:Mattione_Update_08202013_NumTimeBased_Current_NoSelector.png|thumb|left|500px|Current (08/20/13) Code, No Hit Selector]]
 
| [[Image:Mattione_Update_08202013_NumTimeBased_Current_NoSelector.png|thumb|left|500px|Current (08/20/13) Code, No Hit Selector]]

Revision as of 00:12, 21 August 2013

Track Candidate Reconstruction Sampling

  • All events have one π+ thrown at p = 150 MeV/c, θ = 90 degrees, φ = random.
Event # Truth Hits Reconstructed Hits Current (08/20/13) Code Track Candidates Spiral Code Track Candidates
Event 1
Mattione Update 08202013 SlowPiPlus Event1 TruthHits.png
Mattione Update 08202013 SlowPiPlus Event1 ReconHits.png
Mattione Update 08202013 SlowPiPlus Event1 Current.png
Mattione Update 08202013 SlowPiPlus Event1 Spiral.png


Performance

  • 1000 events, all with one π+ thrown at p = 150 MeV/c, θ = 90 degrees, φ = random.

Multiplicity

  • # Track Candidates
Current (08/20/13) Code
Spiral Code
  • # Time-Based Tracks (with PID = π+)
Current (08/20/13) Code
Spiral Code
  • # Time-Based Tracks (with PID = π+) with Hit Selector DISABLED
    • Hit Selector:
      • Runs just prior wire-based & time-based tracking.
      • Re-selects which hits to use for track fitting.
      • In theory this improves things, because with better guesses for the track momentum and position, you should be able to better select the hits along that trajectory.
      • In practice, this can pick up many extra, unwanted hits for spiraling tracks
      • Recommendation: Test with the hit selector set to ONLY reject hits, NOT to acquire new ones.
Current (08/20/13) Code, No Hit Selector
Spiral Code, No Hit Selector
  • Average Event Reconstruction Rate:
    • Current (08/20/13) Code: 7.5Hz
    • Spiral Code: 17.5Hz

Accuracy

  •  % of events with at least one track that is "roughly close" to the thrown parameters:
    • "Roughly Close": p within 20%, θ within 15 degrees, φ within 30 degrees, Vertex-Z within 10cm
Stage Current (08/20/13) Code Spiral Code Current (08/20/13) Code, No Hit Selector Spiral Code, No Hit Selector
Track Candidates 28.9% 33.0% NA NA
Time-Based Tracks 5.7% 5.8% 11.3% 7.5%