From solidwiki
Revision as of 10:24, 4 December 2020 by Saw (Talk | contribs) (Created 06/09/11(Riordan), Last modified 05/31/20(Zwzhao))

Jump to: navigation, search


Weizhi's note in 2018

Weizhi's result with SAMPA



input for tracking, closely related

see details in the link


The call function and resolution files are at

see "readme" for details

Xin Qian's input

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

  • Algorithms to try
    • [1]
      • 3D (present)
      • 2D (track x,y separately and combine)
    • Tree search
    • Mindy's code
    • Others
  • Condiderations
    • With and without magnetic fields
    • With field, is there p dependence
    • GEM clustering dependence
    • Calorimeter and other detector information
    • Potential improvements
    • Dead areas in GEMs
  • 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

Tracking Roadmap

  • Input and output
    • Develop GEMC banks output standards
    • Create implement GEM hit <-> banks interface for digitization code
    • Create library for loading banks output, clustering for tracking code
    • For library, interface with Hall A analyzer, ROOT output
  • Can be done in parallel:
    • Implement other algorithms
    • Evaluate benchmarks


Resolution update

Xin's comment on 2011/09/21

Calibration and resolution from GEM hits