Difference between revisions of "Solid Tracking"
From Hall A Wiki
(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 ...) |
(Link to new wiki) |
||
| (35 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | =Things to do and learn from tracking= | + | This page has been moved to [https://solid.jlab.org/wiki/index.php/Tracking https://solid.jlab.org/wiki/index.php/Tracking] in the new [https://solid.jlab.org/wiki SoLID Wiki]. Please do not edit this page. |
| + | |||
| + | = 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 | ||
| + | |||
| + | = [[Solid GEM Digitization | 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 | *Need to define input and output data structures for tracking code | ||
| Line 6: | Line 36: | ||
*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) | ||
| Line 19: | Line 49: | ||
** Calorimeter and other detector information | ** Calorimeter and other detector information | ||
** Potential improvements | ** Potential improvements | ||
| + | ** Dead areas in GEMs | ||
*Benchmarks | *Benchmarks | ||
| Line 34: | Line 65: | ||
** Uncorrelated - correlated backgrounds | ** Uncorrelated - correlated backgrounds | ||
** Readout strip configuration: x/y vs. r/phi | ** 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 = | ||
| + | |||
| + | * [https://hallaweb.jlab.org/wiki/images/a/a5/New_calibration.pdf Calibration and resolution with current CLEO field] by Rich Holmes (3 Feb 2016) | ||
Latest revision as of 15:39, 7 December 2020
This page has been moved to https://solid.jlab.org/wiki/index.php/Tracking in the new SoLID Wiki. Please do not edit this page.
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
- Xin's progressive tracking
- 3D (present)
- 2D (track x,y separately and combine)
- Tree search
- Mindy's code
- Others
- Xin's progressive tracking
- 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)
