|Message: Re: Energy Conservation with G4ParticleChange ProposeTrackStatus||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 am not sure I understand your second paragraph...
G4ParticleChange is a class that allows a G4VProcess to communicate with the G4 kernel. You shouldn't be dealing with G4ParticleChange in UserSteppingAction(?).
and, as you correctly say, add the kinetic energy manually to ensure energy conservation.
Alternatively, you can write a process class, similar to photon absorption, that kills the track when you want. In that case, you register the process with the particle process manager as you do for all the other processes and you fill G4ParticleChange and ProposeTrackStatus as required (including: ProposeEnergy(0.0) and ProposeLocalEnergyDeposit(kinEnergy)).
see for example:
In that case, you don't have to do any accounting additionally in SteppingAction.
Hope this helps, Peter