Difference between revisions of "Solid Tracking"

From Hall A Wiki
Jump to: navigation, search
(New page: =Things to do and learn from tracking= *Need to define input and output data structures for tracking code ** Output from tracking should be standardized so we can easily compare ...)
 
(Things to do and learn from tracking)
Line 6: Line 6:
  
 
*Algorithms to try
 
*Algorithms to try
**        Xin's progressive tracking
+
**        [[Xin's progressive tracking]]
 
***              3D (present)
 
***              3D (present)
 
***                2D (track x,y separately and combine)
 
***                2D (track x,y separately and combine)

Revision as of 15:21, 21 June 2011

Things to do and learn from tracking

  • Need to define input and output data structures for tracking code
    • Output from tracking should be standardized so we can easily compare


  • Condiderations
    • With and without magnetic fields
    • With field, is there p dependence
    • GEM clustering dependence
    • Calorimeter and other detector information
    • Potential improvements
  • Benchmarks
    • Tracking rate
    • Tracking efficiency (#of real tracks reconstructed/# of real tracks)
    • Effect of noise in fits (hits replaced with noise)
    • Pure noise tracks (ghost tracks)
    • Multi-track reconstruction efficiency
    • Helicity dependence of reconstruction (efficiency *and* quality)
    • Noise correlation between planes effects
  • Benchmark conditions to map
    • Background rates 0 - x5
    • Background rate derivatives (for helicity dependence)
    • Uncorrelated - correlated backgrounds
    • Readout strip configuration: x/y vs. r/phi