Difference: SWGuideIterativeTracking (5 vs. 6)

Revision 62009-08-06 - KevinStenson

Line: 1 to 1
 
META TOPICPARENT name="SWGuideTrackReco"
Changed:
<
<

Iterative Tracking Algorithm

>
>

Iterative Tracking

  Complete: 5

Goal of the page

Changed:
<
<
The reader of the page is expected to get familiar with the iterative tracking approach, and to be able to add tracking steps in the whole tracking chain.
>
>
The reader of the page should become familiar with the iterative tracking approach, and be able to add tracking steps in the whole tracking chain.
 

Contacts

Michele Pioppi: michele.pioppi@cernNOSPAMPLEASE.ch
Changed:
<
<
Kevin Stenson: stenson@fnalNOSPAMPLEASE.gov
>
>
Kevin Stenson: kevin.stenson@coloradoNOSPAMPLEASE.edu
 

Introduction

Changed:
<
<
The approach is based on the selection of first track collection with very tight settings in order to reduce as minimum as possible the fake rate. All the hits attached to the first track collection are removed and a second track reconstruction is applied with the remaining hits. The second collection is obtained loosening all the tracking cuts.
See the following presentations for a detailed description:
>
>
The iterative tracking approach runs the standard CTF tracking algorithm multiple times. At each iteration, the hits used by previous iterations are removed from consideration and the CTF tracking algorithm is run again with progressively looser settings. The presentations below trace the development of the iterative tracking approach:
  Tracking meeting 23 may 2007
PFlow meeting 05 july 2007
Tracking meeting 01 august 2007
Line: 28 to 23
 Tracking meeting 05 february 2008
Tracking meeting 14 february 2008
The results of the iterative tracking are summarized in the internal note 2007/065
Added:
>
>

Summary of the current iterative steps

The current (3_1_X) default tracking in CMS contains 6 iterations, labeled 0 through 5. The main distinction between the iterations is the track seeding algorithm which is shown in the table below.
Iteration Seeding Layers pT cut (GeV) d0 cut (cm) z0 cut (cm)
Zero pixel triplets 0.5 0.2 15.9
1 pixel pairs 0.9 0.2 0.2*
2 pixel triplets 0.075 0.2 17.5
3 pixel pairs 0.35 1.2 7.0
4 TIB1+2 & TID/TEC ring 1+2 0.5 2.0 10.0
5 TOB1+2 & TEC ring 5 0.8 5.0 10.0

In the table, d0 and z0 refer to the transverse and longitudinal impact parameters of seeds with respect to the nominal interaction point. The * indicates the impact parameter with respect to a pixel vertex. Using triplet seeding is much faster and has a lower fake rate than pairs. Therefore, pixel triplet seeding is run first (iteration 0), followed by pixel pairs (iteration 1) for additional efficiency. This is repeated in iterations 2-3 which is optimized to find lower momentum tracks and also tracks which may decay within a couple of cm of the production vertex. Iterations 4 and 5 do not use pixels to seed and are designed to find tracks which are significantly displaced from the beam line or tracks which do not leave sufficient pixel hits to be found in the earlier iterations. Other differences between iterations during track building include the minimum number of hits (3 for iterations 0-2, 4 for iteration 3, and 7 for iterations 4-5), the number of lost hits (1 for iterations 0-2 and 0 for iterations 3-5). The final cleaning stage is also different. The early steps have stricter requirements on tracks originating from the production vertex while the later steps have stricter requirements on the track quality. Details will eventually be found in the tracking note but for now they can be found in the Very Large Impact Parameter Track Reconstruction note or by looking in the configuration steps which are linked in the table above and annotated more below.

 

Usage of the algorithm

In each tracking iteration the user must:
Changed:
<
<
  • Create a new cluster collection by remove the clusters used in the previous track collections
>
>
  • Create a new cluster collection by removing the clusters used in the previous track collections
 e.g.
Added:
>
>
firstfilter = cms.EDFilter("QualityFilter", # Selecting tracks from the previous iteration TrackQuality = cms.string('highPurity'), # Just take the highPurity ones recTracks = cms.InputTag("preMergingFirstStepTracksWithQuality") )
  secClusters = cms.EDFilter("TrackClusterRemover", oldClusterRemovalInfo = cms.InputTag("newClusters"), # clusters used in the previous iteration trajectories = cms.InputTag("firstfilter"), # trajectories of the previous iteration
Line: 104 to 114
 
Reviewer/Editor and Date (copy from screen) Comments
KatiLassilaPerini - 29 Jan 2008 created template page
Changed:
<
<
>
>
KevinStenson - 06 Aug 2009 Added information on current iterative tracking steps
 
<!-- In the following line, be sure to put a blank space AFTER your name; otherwise the Summary doesn't come out right. -->
Changed:
<
<
Responsible: ResponsibleIndividual
>
>
Responsible: KevinStenson
 Last reviewed by: Most recent reviewer
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback