|Message: Re: Passing info to tracks||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)|
There is G4Track::SetUserInformation() which is designed specifically for this.
In PreUserTrackingAction() I do: TrackInfo *info = new TrackInfo(...); ((G4Track *)track)->SetUserInformation(info);
Another possibility is to define a std::map<G4Track*,TrackInfo>, add an entry in PreUserTrackingAction(), and clear it in PostUserTrackingAction() (or wherever makes sense -- you may not need the vector at all as there may only be a single track involved). Note that the Geant4 kernel will delete the track, so be careful about dereferencing its pointer -- it may be better and more useful to define the map using TrackID rather than a pointer to the G4Track (e.g. if it has Event scope then it can be used for ParentID-s also).
What I do is have a Manager class of my own that implements all of the User Actions (plus detector construction, primary event generator, and exception handler). This class can have data independent of the Geant4 code. Because of the way the user action objects are deleted by Geant4 code, I have a helper class for each that provides a separate object that merely re-directs to the singleton Manager object itself.
Be careful if you try to derive your own class from G4Track, because it uses G4Allocator (which implicitly knows the object's size).