|Message: Tracking of secondaries after AbortEvent||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 have an application in which I kill events when they reach a certain volume. I do this by calling runManager->AbortEvent() in my UserSteppingAction() method. My question is what happens to secondaries produced prior to the call to AbortEvent? As far as I can understand from the user manuals the stack is supposed to be deleted after AbortEvent() is called, still I get hits from secondaries in the volume where I killed the primaries after AbortEvent() has been called. Can data from these secondaries be trusted or is everything junk that happens in an event after AbortEvent() has been called for that particular event? I'm running GEANT4.8.2.p01.
|Inline Depth:||Outline Depth:||Add message:|