Adding gamma-nuclear interaction. #113
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The gamma-nucler cross section is available now in HepEm. Not copied to the device yet and not used on the CPU in the step limit yet. This is the next step, i.e. including the gamma-nuclear in the stepping loop (on the CPU).
…ing the Geant4 process.
The gamma-nuclear cross sections are used now in the HepEm step
limit (HowFar).
But HepEm itself do not perform the gamma-nuclear interaction in
its Perform method. So when gamma-nuclear limits the step, HepEm
leaves the primary track the same in its Perform interaction. This
should let all previous usage work fine (just some additional step
limits that does nothing).
However, the G4HepEmTrackingManager handles now gamma-nuclear
interaction by:
- obtaining the pointer to the Geant4 gamma nuclear process
at initialisation (if the user attached any to gamma)
- this native Geant4 process is used then to perform the gamma-
nuclear interaction, whenever gamma-nuclear limits the step,
(i.e. HepEm Perform is not invoked in this case).
Removing unnecesary options while adding now the G4EmExtraPhysics that adds the Geant4 gamma-nuclear and lepton-nuclear processes. (The later, i.e. electron and positron nuclear, is still deactivated as long we don't have them in HepEm.)
…HepEmGammaData (cross section) changes.
…t selector is needed).
…ics for gamma-nuclear.
…set properly needed for DoIt.
… as no muon produced.
…amma-nuclear cross sections.
…ell (both on host/device).
…nuclear cross section related changes).
Only the new gamma cross section array, that contains the gamma-nuclear as well, is used now everywhere.
… before G4-v-11.2.0. The G4GammaNuclearXS data are uploaded in its constructor from G4-v-11.2.0 while it is done in the BuildPhysicsTable interface before G4-v-11.2.0. This modification works fine with all G4 versions (from 11.0.0).
…ed only from 11.0.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gamma-nuclear cross sections are available now and used in the HepEm physics during the step limit calculations for gamma photons. The interaction itself is performed using the corresponding native Geant4
photonNuclear,G4HadronInelasticProcessin the HepEm tracking manager: thePostStepDoItof this process is invoked whenever gamma-nuclear limited the step but only if thephotonNuclearprocess was attached to gamma in the physics list.The HepEm tracking manager tries to find the
photonNuclearprocess at initialisation by checking the processes attached to the gamma process manager. If it is found, the pointer to this process is stored locally in the tracking manager such that the process is available during the gamma tracking. If it is not found (i.e. no gamma-nuclear process attached to gamma), then this field staysnullptr. The process is obviously not invoked in this case but everything still works fine, i.e. the step might be limited by gamma-nuclear but delta interaction happens (no change, the original gamma keeps on going). The same happens when theG4HepEmGammaManager::Performmethod is invoked for the interaction, i.e. no interaction happens when gamma-nuclear limited the step. So everything works fine even when gamma-nuclear process is not attached to theG4Gammaor when using HepEm also to perform the interaction: no interaction happens in this case.