| Data Structure of GeoTracks/MCTracks [message #20279] |
Mon, 13 February 2017 09:46  |
PaulinaM
Messages: 6
Registered: February 2017
Location: Darmstadt
|
occasional visitor |
From: *084.058.pools.vodafone-ip.de
|
|
Hello everyone,
I tried around with extracting data out of r3bsim-simulated files. I found that in GeoTracks daughters are always "0" and ParentIDs are always "-1", so I assume those information not get saved. In my MCTracks ParentIDs get saved, but the UniqueID appears to be always "0", too, so I can't find the ParentTrack. Am I using the wrong attributes to reconstruct particle hierachy? What is the way to get hierachy information?
If I collect the last points of every GeoTrack are those the last points of the trajectories (in the cave) of single particles or do I miss something, maybe due to a linked structure, GeoTracks inside of GeoTracks?
Thanks a lot and best regards,
Paulina
|
|
|
|
| Re: Data Structure of GeoTracks/MCTracks [message #20281 is a reply to message #20279] |
Tue, 14 February 2017 07:25  |
Dmytro Kresan
Messages: 166
Registered: June 2004
|
first-grade participant |
From: *gsi.de
|
|
Hello Paulina,
GeoTracks: they are stored in order to draw the trajectories in the event display. This structure does not contain hierarchy information. It is a full trajectory, so end of it is either inside of cave, if particle was stopped (disappeared), or at the edge of the cave if particle leaves it. Normally, we do not use the GeoTracks to analyse simulated data quantitatively.
MCTracks: Contain mother / daughter information and vertex (start) position and momentum. Also PDG code. If you have a track, GetMotherId() method will give you index of the parent track in the same array. So you can access it directly by this index and there is no need for unique id. If mother id is -1 - it is a primary track.
Hope this helps. Best regards,
Dima
|
|
|
|
GSI Forum
Search
Help
Members
Login
Home
