|Message: Re: How to get track length of a primary particle at the end of event in the digitization||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)|
Soman writes: > Thanks a lot for your explanations. It cleared up my mind about the > G4Trajectory capabilities. So I guess you recommend to implement it > through G4VTrajectory in the G4UserTrackingAction. Right? No. If you decide to write your own G4UserTrackingAction subclass, then you will be able to access the G4Track* directly and you won't need to deal with trajectory objects at all. However, you should know that that action is called for _each_ track, during the event, not all at once at the end. So your code should include a way for you to save the information during an event, then save it out as desired at the end. I recommend reading the Developer's Guide to get an overview, and to also look at some of the examples to see how TrackingAction can work for you. -- Mike Kelsey