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 #10267 is a reply to message #10265]

Tue, 23 February 2010 12:28

Anonymous Poster

From: *e18.physik.tu-muenchen.de

Hi,

the DAF is the Deterministic Annealing Filter I was quoting in my first message in this thread.

I dont know what the order of the problem is. It is a principle problem that pattern reco can never 100% decide only the right hit in a detector plane. I am trying to find a consistent way to treat this problem. It might or might not affect many tracks, however the problem is interesting and real. It will be very interesting to study what happens with realistic MVD pattern reco for instance with different pile-up or noise levels. I think especially pile-up will be an issue as the MVD does not have a zero interation time, I assume. How do different fitting algorithms (such as the DAF) make the situation better/worse, ..?..?.

Christian

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: Thu Apr 25 14:08:37 CEST 2024

Total time taken to generate the page: 0.01095 seconds