Message: Re: low-energy tracks incorrectly stopped Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: low-energy tracks incorrectly stopped 

Forum: Fast Simulation, Transportation & Others
Re: Question low-energy tracks incorrectly stopped (Tom Roberts)
Re: None Re: low-energy tracks incorrectly stopped (Artem Zontikov)
Date: 28 Nov, 2015
From: Tom Roberts <Tom Roberts>

It is true that Vacuum (=G4_Galactic) has non-zero density, but that is not the problem (if it were, high-energy tracks would also do this; they don't). The track is stopped right at the end of the first step (presumably track->status set to fStopButAlive). Stopped mu+ decay, and stopped e+ annihilate.

My code puts a StepLimiter process onto every particle, and no matter what value I give it this happens at the end of the first step. As this happens when the limiting process is either StepLimiter or Transportation (reached a boundary), I conclude this is done somewhere in the stepping code, not in any process.

My code never sets track-status to fStopButAlive, so I need to know where in the Geant4 tracking code that this has been added, and how I can avoid it. Presumably there is a test on kinetic energy or velocity, as higher-energy tracks do not do this.

I would also like to understand why this was done....

Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 None: Re: low-energy tracks incorrectly stopped   (Artem Zontikov - 29 Nov, 2015)
 Add Message Add Message
to: "Re: low-energy tracks incorrectly stopped"

 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 ]