Detailed Tracking Task List, October
2003
The main tasks are highlighted in blue. Sub-tasks
are detailed in different colors in the lists below.
Some of the sub-tasks have detailed sub-sub tasks. No names have been
assigned yet!
- Establish corrections for energy loss and magnetic
field in the tracking system
- MC vs. Data study to determine correct material
description for the real detector
- Study rate of photon conversions in Data vs.
phi, r, z
- We already have a file with 1M conversions!
- need to make plots, quantify
- Study V-finding efficiency in Data vs. phi,
r, eta
- Use Kshorts, study lifetime vs phi, r, eta
- need to make plots, quantify (Notre Dame student)
- Study rate of photon conversions in MC vs. phi,
r, z
- run tuple-making code over a large sample of photon
conversions
- need to make plots, quantify
- compare results with what is seen in data to locate
extra material
- modulo tracking efficiency differences, this should
give relative rates of material between Data and MC
- Study V-finding efficiency in Jet MC vs. phi,
r, z
- run tuple-making code over a large sample of p14
QCD MC
- same Kshort study as data, but with MC truth
- compare measured lifetime between Data and MC
- check that tracking efficiency effects are cause
of lifetime shifts
- Study rate of photon conversions in Jet MC vs.
phi, r, z
- use Jet tuples
- need to make plots, quantify
- compare results with what is seen in data
- correct for tracking, V-finding efficiency differences
in MC and Data
- gives absolute rates of material in Data and MC
- Put correct material in Tracking code geometry
description
- use Kshort mass vs. mometum as a diagnostic
- see if the behavior vs. momentum or energy is the
same in MC
- check on J/Psi, other samples
- Write code for TMB Corrections
- needs to work on TMB as well, so parametrized form
needed
- requires check of energy loss corrections vs phi,
p, eta, z, etc.
- Establish Magnetic Field magnitude, and
direction(?) in tracking volume
- Study Kshort mass, after energy loss corrections,
vs. z, phi, eta
- might have to differentiate solenoid polarities
- overall field normaliztation needed in central
region
- look for smoothly varying mass shifts in extrema
of magnetic field
- Modify Magnetic field model to try and simulate
any variance in Ks mass
- can we see radial field components?
- see if shape of variations can be made consistent
with Bfield model
- Implement modified model, if needed
- analytic corrections to calculated one - probably
simplest
- Understand tracking efficiency difference between
MC and Data
- Understand single hit efficiency in CFT
- comparison of ADC spectra for hits on tracks
- comparison of ADC spectra for hits on tracks with
MC+zerobias events to simulate noise
- Study of gains (stereo, axial)/light yield in
MC and Data
- Study of threshold effects/global threshold cut
in MC and Data
- Include effects of dead channels (Database work)
- Tune MC to match what Data efficiency
- should just be matching light yields
- components include attenuation in waveguides,
stereo/axial gains
- Study CFT clustering
- comparison of cluster widths, width distribution
to MC (MC+zerobias)
- look for effects unexplained by single fiber performance
- Study of clustering in general (resolution, size,
etc)
- Understand single hit efficiency in SMT
- comparison of ADC spectra for hits on tracks - is
charge deposition/sharing correct?
- comparison of ADC spectra for hits on tracks with
MC+zerobias events to simulate noise
- Study of clustering in general (resolution, size,
etc)
- Effects of dead channels?
- Implement modifications to SMT MC if needed
- Alignment studies
- check for residual biases/errors in alignment of
tracking detectors
- creation of smeared alignment MC geometry to simulate
residual problems
- study of effects introduced by misalignments
- Study/Improve Tracking in jets
- Detailed study of MC tracking in jets
- where are tracks lost?
- are more fake tracks generated?
- if so, how?
- Will require some digging around in the tracking
code
- Suggest improvements to the tracking algorithms
- track finding parameters based on hit density?
- ?
- Make Code run faster
- profiling to look at execution speed
- memory profiling to look at memory consumption, problems with freeing
memory
- algorithmic changes?
- (pretty technical, expert-oriented)(SSS, Herb)
- Fast Track Re-Fit from DST (say, with new alignment
constants)
- small amount of code to remake GTrack objects including new clusters
- appropriate set of RCP parameters to do this
- fairly technical
- Study/Verify Track errors/pulls for Central
and Extrapolated Tracks
- Study "perfect" tracks in MC with no multiple
scattering, interactions, etc.
- are the track errors and parameters correct?
- if not, find the bug(s)!
- Check track extrapolation as well
- slowly add effects of material and check that
things stay ok
- Will require some digging around in the MC
(experts available for consultation)
- Look at current tracking errors in Data
- do they look at all like the MC errors?
- How big are the non-gaussian tails?
- to what (most likely) can we attribute them?
- should we develop a "smearing" routine for tail
modelling?
- Understand variation of efficiency with particle
type
- pions, electrons, and muons have different tracking efficiencies (?)
- check MC/Data comparison
- investigate if they are very different after all of the above tasks
are finished
- Tracking with H-Disks?
- There are tracks out there with H-Disk hits...
- check residuals, difference in track errors with and without H disks
- check vertexing performance with and without H disks
- should we care about them?
- Tracking using the FPS MiP Layer?
- The FPS could provide an extra tracking point in a region where our
coverage is limited
- extrapolation study to FPS hits (MC)
- extrapolate tracks to the FPS
- study residuals of track extrapolation to FPS hits
- Study improvement (or not) of track parameters
by adding FPS hits
- extrapolation study to FPS hits (Data)
- extrapolate tracks to the FPS
- study efficiency of FPS in data
- study residuals of track extrapolation to
FPS hits
- Study improvement (or not) of track parameters
by adding FPS hits