Central track matching

1
Central track matchingL3 display for debugging

• L3 Filters Meeting
• Paul Balm
• Aug 30, 2000

2
Outline

• Status of central track matching tool
• Status of L3 display for debugging
• based on d0ve

3
L3TMuoCentralMatch

• Goal To improve the local muon tracks by
  matching them to central tracks
• For the local muon track this will enhance
• momentum resolution
• vertex resolution (!)
• From central trackers point of view
• reduce running time through regional tracking
• tag tracks as muons

4
Matching algorithm

• Currently implemented a straightforward
  algorithm
• Call local tracking tool (muon sys only)
• For all found muon tracks, predict region in
  central tracker
• Do regional tracking in central tracker in each
  region
• For all found central tracks, calculate c2 of the
  match
• Returns only one matched track per muon track

5
Current status

• First version in CVS, incl. integrated test
• Now test it! Debugging tool (display) in
  preparation
• based on d0ve - see rest of talk
• Performance of tool to be measured always comes
  last
• timing
• efficiency
• mismatches (fakes)
• etc

6
L3Display

• Based on d0ve
• d0ve D0 Visualization Environment
• Wireframe display, designed for debugging
  reconstruction code
• Runs as offline framework package
• - but currently not on NT

7
Example of a display
8
Using d0ve

• How to use d0ve
• For displaying offline chunks, run binaries that
  come with d0ve_muon, d0ve_smt, etc.
• Displaying L3 results is a little more
  complicated (no chunks)
• Objects are displayed by adding their
  representation to the display
• a representation is s/th that knows how to draw
  itself
• there exist a TrackRep, MSCHitRep etc

9
The L3Display

• L3 Tools usually tested in an offline package
• package runs all tools, should then display tool
  results
• L3DisplayPackage A base class for offline
  framework packages
• has member L3Display, holding Reps of all
  results
• requires the tool test pkg to implement
  standardized accessors for tool results
• tool test pkg calls display().processEvent(Event,
  this)
• go! but

10
Using L3Display

• There are only few Reps for L3 data types
• L3TrackRep
• MuoTrackRep
• L3ZRegionRep
• If youd want to use the L3Display for other
  data, youll have to write a Rep
• Currently everything in package l3mutest
• Still in debugging stage

11
Conclusions

• Central track matching tool
• will be fully debugged once display is ready
• currently in CVS, integrated test runs
• L3 Display
• currently still being debugged
• limited number of Reps available
• ready for general use in October