GSI Forum: Meetings » Minutes of PandaRoot Meeting May 27 are posted.

Home » PANDA » PandaRoot » Meetings » Minutes of PandaRoot Meeting May 27 are posted.

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

Minutes of PandaRoot Meeting May 27 are posted. [message #6923]

Sun, 15 June 2008 14:46

Jens Sören Lange
Messages: 193
Registered: June 2005

first-grade participant

From: *web.vodafone.de

http://panda-wiki.gsi.de/cgi-bin/view/Computing/Minutes27May2008

Please note that the track object proposal is preliminary.

We will vote about it on the next PandaRoot EVO Meeting, June 17, 2008.

Report message to a moderator

Re: Minutes of PandaRoot Meeting May 27 are posted. [message #6928 is a reply to message #6923]

Mon, 16 June 2008 09:31

Klaus Götzen
Messages: 293
Registered: June 2006
Location: GSI

first-grade participant

From: *gsi.de

Hi all,

just wanted to give an early commment on the track proposal:
Be aware, that the TCandidate originally is not a tracking but a analysis object, so therefore I wouldn't recommend to derive the TTrack from it.
To have some representation for the basic parameters you perhaps could think about deriving from TFitParams.

Concerning the storage of hit indices I implemented now the class PndMicroCandidate in RhoBase. This now is intended to contain all the measured information of a track and it also has some members of type TArrayI (one for each tracking subdetector) forseen to contain the hit indices.
It also has members for PID information like dE/dx and theta_C for the various detectors.
The idea is to create a TCandidate at analysis time on the fly, which has a backpointer to this MicroCandidate giving access to all these info at analysis time.
Of course we can put everything we want to this PndMicroCandiate which then serves as the primary candidate object.

Cheers and hear you tomorrow,
Klaus

Report message to a moderator

Re: Minutes of PandaRoot Meeting May 27 are posted. [message #6930 is a reply to message #6928]

Mon, 16 June 2008 10:34

Sebastian Neubert
Messages: 282
Registered: March 2006
Location: Munich

first-grade participant

From: *dip.t-dialin.net

Hi!

I will be at CERN tomorrow so I am not sure wether I will be able to take part in the meeting. Here are my comments concerning the track objects:

1) For tracking tasks (e.g. Vertexing, Refitting, ...) the full covariances are needed. I did not understand from the proposal how this will be handled. It is vital that we also keep the correlations between the space and momentum components of the track parameters!
If we store momentum and position (6 parameters) the system is over-determined. I still do not understand what would be the consequences for the covariances. Probably it is no big problem to transform this into the usual 5-parameter form needed for tracking (refitting, constraint fitting..)

A short list of requirements (which data is needed):
++ For Kinematic Fits: Paramters + covariances at Vertex
++ Extrapolation without errors: Parameters at some point
++ Extrapolation with errors: Parameters, Covariances + Hits

2) How do we want to organize the data when we perform several fits on the same set of hits? (e.g. different particle hypothesis) Will this resut in several tracks each containing a copy of the hits?

Best Regards,
Sebastian.

PS: From the design point of view I.M.H.O _inheritance_ of a new object should be motivated by more than just reuse of member variables. Usefull Question: Will we ever put the objects that derive from the base class into the same container?
If you answer no or maybe to this question the code will get clearer if we do not se inheritance.

Sebastian Neubert
Technische Universität München
Department Physik E18
sneubert@e18.physik.tu-muenchen.de
tel: +49-8928912592

Report message to a moderator

Previous Topic:	PandaRoot EVO Meeting, TUE June 17, 2008, 10-12
Next Topic:	Next PandaRoot EVO Meeting

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Apr 23 13:13:36 CEST 2024

Total time taken to generate the page: 0.00828 seconds