|Message: Re: Getting parent particle Name||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Determining a parent particle requires some additional overhead. You will most likely need to customize the G4VUserTrackInformation and/or G4VTrajectory. This allows you to store transient information from your tracks which, as you know, is lost as each track is destroyed. This can include parent particles, originating processes, etc.
Propagation to child particles takes place in the EndOfTrackingAction within TrackingAction. You can use the GimmeSecondaries method to get a track's child tracks before they are actually tracked. This allows you to set their G4VUserTrackInformation according to a) the parent's track info or b) a new track info in the case of the track's id = 0.
To store this info in your hits, you would either retrieve it from a trajectory container during EndOfEventAction or get your G4VUserTrackInformation object in ProcessHits and cast to the correct child class.
These SLAC event tips should be enough to get you started:
BTW, you can retrieve the id of a track's parent, but the actual track is usually unaccessible (i.e. transient) unless you've taken special actions such as keeping it on the stack using StackingAction.
Hope that helps.
|Inline Depth:||Outline Depth:||Add message:|