GSI Forum: Tracking » plane id in track candidate

Home » PANDA » PandaRoot » Tracking » plane id in track candidate

Show: Today's Messages :: Polls :: Message Navigator

Re: plane id in track candidate [message #10263 is a reply to message #10254]

Tue, 23 February 2010 11:51

Lia Lavezzi
Messages: 291
Registered: May 2007
Location: Torino

first-grade participant

From: *pv.infn.it

Hi Christian,

Quote:

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.

if you want to know that two hits are on the same plane in Kalman isn' t it enough to use a check like the one in GeaneTrackRep::getPos or getMom functions if(pl!=fRefPlane)extrapolate(pl,statePred) to determine whether the extrapolation is needed or not?

Ciao,
Lia.

Report message to a moderator

[Message index]

		plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 10:23
		Re: plane id in track candidate By: StefanoSpataro on Tue, 23 February 2010 10:36
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 10:53
		Re: plane id in track candidate By: StefanoSpataro on Tue, 23 February 2010 12:04
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 12:28
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 11:07
		Re: plane id in track candidate By: Tobias Stockmanns on Tue, 23 February 2010 10:47
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 10:57
		Re: plane id in track candidate By: Tobias Stockmanns on Tue, 23 February 2010 11:29
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 11:45
		Re: plane id in track candidate By: Radoslaw Karabowicz on Tue, 23 February 2010 16:45
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 16:48
		Re: plane id in track candidate By: Radoslaw Karabowicz on Tue, 23 February 2010 17:06
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 17:11
		Re: plane id in track candidate By: StefanoSpataro on Tue, 23 February 2010 17:59
		Re: plane id in track candidate By: Radoslaw Karabowicz on Tue, 23 February 2010 18:06
		Re: plane id in track candidate By: StefanoSpataro on Tue, 23 February 2010 18:20
		Re: plane id in track candidate By: Radoslaw Karabowicz on Tue, 23 February 2010 21:28
		Re: plane id in track candidate By: Tobias Stockmanns on Wed, 24 February 2010 08:12
		Re: plane id in track candidate By: Radoslaw Karabowicz on Wed, 24 February 2010 09:59
		Re: plane id in track candidate By: Radoslaw Karabowicz on Tue, 23 February 2010 18:00
		Re: plane id in track candidate By: Tobias Stockmanns on Tue, 23 February 2010 20:48
		Re: plane id in track candidate By: Lia Lavezzi on Wed, 24 February 2010 12:47
		Re: plane id in track candidate By: Lia Lavezzi on Tue, 23 February 2010 17:56
		Re: plane id in track candidate By: Lia Lavezzi on Tue, 23 February 2010 11:51
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 11:58
		Re: plane id in track candidate By: Lia Lavezzi on Tue, 23 February 2010 12:12
		Re: plane id in track candidate By: Gianluigi Boca on Tue, 23 February 2010 15:31
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 15:41
		Re: plane id in track candidate By: Gianluigi Boca on Tue, 23 February 2010 16:03
		Re: plane id in track candidate By: Anonymous Poster on Tue, 23 February 2010 16:15

Previous Topic:	Momentum resolution and reconstruction efficiency of LHE tracking
Next Topic:	[FIXED] Geane for luminosity monitor: TGeant3 not initialized

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Apr 19 03:30:51 CEST 2024

Total time taken to generate the page: 0.01036 seconds