EF Tracking Study using Cosmics (ESDs)

Analysis Plan

ID Detector Status: (for each run we use)

• Run summary (PIX-SCT-TRT, B-field)
• Check ID DQM
  • Hardware switched off
  • Dead areas in some eta/phi/z0/d0 histograms
• Alignment constants ?

EFID Track Study: (People: ?)

1. Characterise strange tracks
2. Characterise good tracks
   • Differences between EF and offline
3. Hit Efficiency
   • Within a good geometrical region of ID --> "Should have crossed X layers + have y hits ==> hit efficiency"

EFID vs Offline: (Jenna, Stefan)

1. Offline Track Selection
   • Any
   • 3+3 (si hits), abs(d0) < 100 mm, abs(z0) < 400 mm
2. Resolution
   • Offline - EF, all track parameters
3. Track Efficiency
   • Event and Track efficiency, Manchester meeting, 12 dec 08
   • Efficiency as function of matching dR value

EFID Only Performance: (John, Mark)

1. Resolution
   • EF_1 - EF_2, (both B-field ON/OFF) could (perhaps?) give infoamtion about alignment
2. Absolute Track efficiency
   • Measure the EF tracking efficiency without reference to the offline tracks using tag-and-probe style method, Manchester meeting, 12 dec 08

ID vs Muon, EF Tracking: (People: Graham, Jiri)

1. xxx

Other:

1. Comparison with MC

General Info

• The private processed samples are currently available at:
  /castor/cern.ch/user/m/masik/t0
  /castor/cern.ch/user/m/masik/t0/repro
• A package for the offline studies has been created, instructions are available at HLTIDTrackingAna
• Outline of the note: ef_cosmic.tex, ef_cosmic.pdf

Offline Track Selection

• Not much info about other cosmics studies, other than L2 Task Force
• Pt cut: Standard offline perf cut is 1GeV, but L2 task force don't make a Pt cut
• Detector hits: 3+3 Si hits seems reasonable, but could be more stringent, e.g. require a b layer hit, or at least some pixel hits.
• Offline studies on MC also used hit matching, but probably not necessary since we have delta R matching
• Crack region - might be important, still looking at this.

-- StefanAsk - 14 Nov 2008