| 
		
			| Updates in PndTrack - PndTrackCand [message #11095] | Wed, 13 October 2010 19:41  |  
			| 
				
				
					|  StefanoSpataro Messages: 2736
 Registered: June 2005
 Location: Torino
 | first-grade participant |  From: *180-80-r.retail.telecomitalia.it
 
 |  |  
	| Dear all, after the EVO session of this morning, we have decided to apply the following scheme to the tracking code:
 
 
 
 PndTrackCand will store ONLY hit informations (no momentum anymore)
 PndTrack will store only the track informations (i.e. track parameters at the first and last hit), and an index of the corresponding PndTrackCand
 each tracking algorithm will register two separated TClonesArray, one for PndTrack objects, the other for PndTrackCand 
 the link between PndTrack and PndTrackCand will be done using FairLink code
 
 We have decided to apply the changes in three steps:
 
 
 
 Each tracking algorithm will write both PndTrack and PndTrackCand TClonesArray
 The momentum information will be removed from PndTrackCand
 The PndTrackCand object will be removed from PndTrack, leaving only the TCA index
 
 We will proceed step by step, so that we will always be able to use track informations for analysis and tests.
 Let's start with step 1.
 
 The people involved should be:
 
 MVD: Tobias/Ralf
 STT: Gianluigi/Lia
 TPC: Felix/Sebastian(?)/Christian(?)
 GEM: Radek
 LHE: Stefano
 STT+MVD: Gianluigi
 Global: Radex
 
 I hope I have forgotten nobody.
 When the first step change (i.e. writing two different TClonesArray made of PndTrack and PndTrackCand) will be applied, we cpuld move to the second step.
 
 I would like to ask to developers to write in this forum the "OK" once the change will be done in the trunk, so that we could go on. It would be nice to have step 1 ready before next evo meeting (3rd november).
 
 
 
 
 |  
	|  |  |