GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Tracking » plane id in track candidate
Re: plane id in track candidate [message #10257 is a reply to message #10254] Tue, 23 February 2010 10:47 Go to previous messageGo to previous message
Tobias Stockmanns is currently offline  Tobias Stockmanns
Messages: 489
Registered: May 2007
first-grade participant
From: *ikp.kfa-juelich.de
Dear Christian,

I think the planeId is a good idea to have it in every hit. So this should be part of FairHit/PndHit and not of PndTrackCand.

The problem is how to generate this unique ID. For the MVD we store a string which looks like this: 1_1/202_1/205_4/1024_2/1025_3. This string is an encoding of the full path to a sensor within the geoManager. /[volumeId]_[copyNr]/[next stage in hierarchy]/... . With this information we are able to retrieve the full volume information and the positioning matrix of all our sensors.

If you want to match this information to a unique number you would need two maps: one from stringId to intId and one vis versa.
In addition you need to store this information in the parameter database to ensure that you do not loose the links.

This would mean some work for us but I think could be done.

Cheers,
Tobias
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Momentum resolution and reconstruction efficiency of LHE tracking
Next Topic: [FIXED] Geane for luminosity monitor: TGeant3 not initialized
Goto Forum:
  


Current Time: Thu Apr 25 12:16:04 CEST 2024

Total time taken to generate the page: 0.01128 seconds