|Message: Re: Untitled||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)|
I would suggest two alternative solutions. 1. This is for the case you want to get output of the particular step where your interested process occurs. Create your own SteppingVerbose class and put an if-statement to check the process. The way how you can create your own SteppingVerbose class is demonstrated in ExampleN03. 2. This is for the case you want to get output of entire steps of a track which causes a process you are interested in. Given it is impossible to predict which process will occur beforehand, SteppingVerbose would not help you. For this case, you should print out a trajectory at your PostUserTrackingAction. If you feel insufficient to the amount of information of the G4Trajectory and G4TrajectoryPoint classes, you are encouraged to create your own trajectory and trajectory point classes. The thread 34 of Event and Tracking will help you to create your own trajectory classes. If you take solution 2, I would suggest the following. It looks like you are shooting big number of primary protons in an event, but you should shoot one proton per event and run big number of events. All trajectories are kept until the end of an event, regardless of you print them out or not. Thus, if you create trajectories, they consume memory.
|Inline Depth:||Outline Depth:||Add message:|