Tracking

From solidwiki
Revision as of 12:30, 23 March 2021 by Zwzhao (Talk | contribs)

Jump to: navigation, search

Digitization

input for tracking, closely related

see details in the link

document

Weizhi's note with APV in 2018 https://solid.jlab.org/cgi-bin/public/ShowDocument?docid=96

Weizhi's result with SAMPA in 2018/05 https://solid.jlab.org/cgi-bin/private/ShowDocument?docid=95

Weizhi's result with VMM 2021/03 link ?

Weizhi's result for field precision requirement 2021/02 link ?

resolution

Read tracking resolution for various SoLID experimental setup by using resolution file from summary of tracking studies

The call function and resolution files are at https://github.com/JeffersonLab/solid_gemc/blob/master/analysis/tracking_resolution

code

repo https://github.com/xweizhi/SoLIDTracking

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

slide

Resolution update https://hallaweb.jlab.org/dvcslog/SoLID/22

Xin's comment on 2011/09/21 http://hallaweb.jlab.org/12GeV/SoLID/download/tracking/for_Nilanga.pdf

Calibration and resolution from GEM hits