Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add possibility of MSC stepping to HepEmTrackingManager #79

Merged
merged 9 commits into from
Jun 17, 2022

Conversation

hahnjo
Copy link
Collaborator

@hahnjo hahnjo commented Jun 15, 2022

If a step is only limited by MSC, the HepEmTrackingManager can re-try the step with the remaining distance to the discrete interaction, without applying energy loss fluctuations and re-computing the cross sections. This option is enabled by default because it provides a small performance benefit, but can be turned off to get results identical to the G4HepEmProcess.

This simplifies the interplay of the two because MSC works on the
mean energy loss. The minor disadvantage is that the check for the
tracking cut happens after MSC, which means that a particle might
scatter only to be killed afterwards. This is very rare and not of
pratical relevance in terms of performance, but leads to minor
changes even in case loss fluctuations are turned off.
Introduce a temporary storage for pre-step kinetic energy in
G4HepEmElectronTrack.
If a step is only limited by MSC, the HepEmTrackingManager can re-try
the step with the remaining distance to the discrete interaction,
without applying energy loss fluctuations and re-computing the cross
sections. This option is enabled by default because it provides a small
performance benefit, but can be turned off to get results identical
to the G4HepEmProcess.
@mnovak42 mnovak42 merged commit bd138e8 into mnovak42:master Jun 17, 2022
@hahnjo hahnjo deleted the msc-stepping branch June 17, 2022 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants