GSI Forum: Tracking » PndTrack and LheTrack

Home » PANDA » PandaRoot » Tracking » PndTrack and LheTrack

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

PndTrack and LheTrack [message #8909]

Thu, 25 June 2009 01:48

StefanoSpataro
Messages: 2736
Registered: June 2005
Location: Torino

first-grade participant

From: *ihep.ac.cn

Dear all,
I am proud to announce that now the output of lhetrack is stored inside "PndTrack" TClonesArrays.

The old PndTpcLheTrack now is called PndLheCandidate (and "LheCandidate" the corresponding TCA), but the output is also stored inside a TCA called "LheTrack" filled with PndTrack objects. I foreseen the possibility that LheCandidate is not stored anymore inside the output file (when everything will be fixed).
I have also changed names of some classes, removing the "Tpc".

Feel free to use the code. Still the kalmantask and the correlation part should be updated.

I have a comment: I think it would be "good" to have inside FairTrackPar some funtions returning: P Pt Pp Theta Phi in the master frame. Because it is very nasty to write a lot of code simply to know the (q/qp) or the theta (much more complicated)of one PndTrack.
Which are your opinions about?

Report message to a moderator

[Message index]

		PndTrack and LheTrack By: StefanoSpataro on Thu, 25 June 2009 01:48
		Re: PndTrack and LheTrack By: Mohammad Al-Turany on Thu, 25 June 2009 15:36
		Re: PndTrack and LheTrack By: StefanoSpataro on Thu, 25 June 2009 16:02
		Re: PndTrack and LheTrack By: StefanoSpataro on Mon, 29 June 2009 17:02
		Re: PndTrack and LheTrack By: StefanoSpataro on Mon, 29 June 2009 18:35
		PndTrackID By: StefanoSpataro on Wed, 01 July 2009 18:51
		Re: PndTrack and LheTrack By: I. Atar on Tue, 28 July 2009 15:59
		Re: PndTrack and LheTrack By: StefanoSpataro on Tue, 28 July 2009 16:31

Previous Topic:	point of closest approach
Next Topic:	GEM 'realistic' track finding

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Dec 08 07:18:21 CET 2025

Total time taken to generate the page: 0.00836 seconds