Difference between revisions of "Tracking"
From solidwiki
(Created 06/09/11(Riordan), Last modified 05/31/20(Zwzhao)) |
(Created 06/09/11(Riordan), Last modified 05/31/20(Zwzhao)) |
||
| Line 11: | Line 11: | ||
https://github.com/xweizhi/SoLIDTracking | https://github.com/xweizhi/SoLIDTracking | ||
| − | = [[Solid GEM Digitization | Digitization ]] = | + | = [[Solid GEM Digitization| Digitization ]] = |
input for tracking, closely related | input for tracking, closely related | ||
| Line 34: | Line 34: | ||
*Algorithms to try | *Algorithms to try | ||
| − | ** [ | + | ** [https://hallaweb.jlab.org/wiki/index.php/Xin's_progressive_tracking] |
*** 3D (present) | *** 3D (present) | ||
*** 2D (track x,y separately and combine) | *** 2D (track x,y separately and combine) | ||
| Line 86: | Line 86: | ||
= Calibration and resolution from GEM hits = | = Calibration and resolution from GEM hits = | ||
| − | * [ | + | * [[Media:New calibration.pdf|Calibration and resolution with current CLEO field]] by Rich Holmes (3 Feb 2016) |
Revision as of 21:54, 3 December 2020
Contents
document
Weizhi's note in 2018
https://solid.jlab.org/cgi-bin/public/ShowDocument?docid=96
Weizhi's result with SAMPA https://solid.jlab.org/cgi-bin/private/ShowDocument?docid=95
repo https://github.com/xweizhi/SoLIDTracking
Digitization
input for tracking, closely related
see details in the link
resolution
The call function and resolution files are at
https://github.com/JeffersonLab/solid_gemc/blob/master/analysis/tracking_resolution
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
- [1]
- 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
- Calibration and resolution with current CLEO field by Rich Holmes (3 Feb 2016)
