Solid Tracking

From Hall A Wiki
Revision as of 15:12, 11 February 2016 by Rsholmes (Talk | contribs) (Calibration and resolution writeup)

Jump to: navigation, search

Digitization

input for tracking, closely related

see details in the link

resolution file to use

From Weizhi on 01/21/2016

Here is my recent result for the resolution. Detector material and process noise are included in the GEMC simulation and reconstruction. In the link below, you will find three folders, each corresponds to a detector configuration. In each folder you will find many pdf files, named as:

<configuration>_<particle>_<vertex variable>_resolution_process_noise.pdf

These show the resolution for each momentum and polar angle bin.

Each folder also has one or two root files, which store the resolution values in a root 2D histogram format. (x and y of the histogram correspond to momentum and theta, and z gives the resolution value, see <configuration>_resolution_2d_histogram.pdf for example)

If you have any question or suggestion, please email me at weizhi.xiong@duke.edu


http://hallaweb.jlab.org/12GeV/SoLID/download/tracking/resolution

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


  • 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