GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Tracking » Tracking packages
icon4.gif  Tracking packages [message #5080] Wed, 26 September 2007 13:32 Go to next message
Sebastian Neubert is currently offline  Sebastian Neubert
Messages: 282
Registered: March 2006
Location: Munich
first-grade participant

From: *e18.physik.tu-muenchen.de
Hi everybody!

In the next days I will restucture the tracking packages a little bit. There will be a new package "trackrep" where the track representations will go in order to keep dependencies under control.

This is especially important for those working with genfit and geane! GeaneTrackRep will be moved from genfit to trackrep to keep genfit independent of geane.

In the Wiki you can find a proposed scheme.

Cheers!
Sebastian.


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

[Updated on: Wed, 26 September 2007 13:32]

Report message to a moderator

Re: Tracking packages [message #5091 is a reply to message #5080] Thu, 27 September 2007 10:28 Go to previous messageGo to next message
StefanoSpataro is currently offline  StefanoSpataro
Messages: 2736
Registered: June 2005
Location: Torino
first-grade participant

From: *physik.uni-giessen.de
Hello,
excuse me but I am a bit confused about the last developments in tracking.

In Ferrara we have decided that all our tracks should be inheritated from the track parameter definition inside trackbase.
Now, what should be exactly trackrep? Is it not the same thing?

Which should be so the final object of the tracking for all the algorythms? I mean, the start level for correlation with the rst of the world and for pid?

Thanks
Re: Tracking packages [message #5092 is a reply to message #5091] Thu, 27 September 2007 11:08 Go to previous message
Sebastian Neubert is currently offline  Sebastian Neubert
Messages: 282
Registered: March 2006
Location: Munich
first-grade participant

From: *e18.physik.tu-muenchen.de
Hi Stefano!

The trackbase contains the parameter sets which are used by geane. IMHO this should be hidden from the user. Tracking duties (like extrapolations, fitting, vertexing etc..) should be done with the interfaces in genfit (esp. genfit/Track).

For the analysis we need a particle candidate where the most important info is 4-momentum and production vertex. But how this will look like and how we make the connection to the track and to the pid measurements has yet to be defined.

I hope to find something in the analysis document, prepared by Soeren and Matthias and Diego.


Best Regards,
Sebastian.

PS: I do not think we should discuss this in terms of inheritance! It is a structural problem and we should decide to use inheritance for the solution only if we find an explicit reason for this.


Sebastian Neubert
Technische Universität München
Department Physik E18
sneubert@e18.physik.tu-muenchen.de
tel: +49-8928912592
Previous Topic: Release of GEANE (Fortran code)
Next Topic: GeaneTrackRep
Goto Forum:
  


Current Time: Tue Jun 25 07:37:57 CEST 2024

Total time taken to generate the page: 0.01029 seconds