GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Tracking » plane id in track candidate
plane id in track candidate [message #10254] Tue, 23 February 2010 10:23 Go to previous message
Anonymous Poster From: *adsl.alicedsl.de
Hi,

I have stumbled upon an interesting problem in track fitting:

If the pattern recognition determines that two hits in the same plane (e.g. MVD) belong to the same track, because a clear distinction is impossible, they are both input to the track fit. Then maybe the fit can determine which is the outlier or simply it has to use both. The question is how to handle that situation, i.e. how does the Kalman filter (or another algorithm) know that two hits are on the same plane. We could compare the complete plane parameters of both planes, but that is a big computational effort and hardly seems necessary. That is why I propose the following:

We should add an (unsigned) integer is called planeId to all hits in the track candidate. This way any tracking algorithm can easily determine if the next hit is in the same plane or in another one that requires an extrapolation.

If there are no objections, I will add the corresponding things to the PndTrackCand. The long term id behind this is that we will in the near future work on a tracking algorithm called "Deterministic Annealing Filter" (R. Fruehwirth, A. Strandlie, Track fitting with ambiguities and noise: a study of elastic tracking and nonlinear filters, Computer Physics Communications 120 (1999) 197–214) which has a dynamic weighting of hits in a fit, especially if there are several of them in the same plane. This will be cool for doing realistic pattern reco track fitting including the MVD & GEMs.

Cheers, Christian
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Momentum resolution and reconstruction efficiency of LHE tracking
Next Topic: [FIXED] Geane for luminosity monitor: TGeant3 not initialized
Goto Forum:
  


Current Time: Fri Mar 29 09:50:38 CET 2024

Total time taken to generate the page: 0.00985 seconds