Message: Tracking of secondaries after AbortEvent Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Tracking of secondaries after AbortEvent 

Forum: Event and Track Management
Date: 16 Oct, 2007
From: Peter Kimstrand <Peter Kimstrand>

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:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 None: Re: Tracking of secondaries after AbortEvent   (Makoto Asai - 26 Feb, 2008)
 Add Message Add Message
to: "Tracking of secondaries after AbortEvent"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews

[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]