Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • athena athena
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Jira
    • Jira
  • Merge requests 184
    • Merge requests 184
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • atlas
  • athenaathena
  • Merge requests
  • !20642

Merged
Created Jan 25, 2019 by Miha Muskinja@mmuskinjDeveloper

User action that sets G4 looper threshold values

  • Overview 16
  • Commits 2
  • Pipelines 6
  • Changes 9

This user action can configure the looper threshold values in Geant4: http://www-geant4.kek.jp/lxr/source/processes/transportation/src/G4Transportation.cc#L878

The preInclude will set them both to 0 for debugging purposes. By default, Geant4 would only print Exceptions for particles above 100 MeV.

The user action also calls a Geant4 printout method, e.g.:

G4Transportation:  Current values for thresholds related to  the killing of looping tracks:
Warning Energy   = 0 MeV   ( below this tracks are killed without warning )
Important Energy = 0  ( above this tracks are given multiple chances )
Extra Trials     = 10 'important' tracks, i.e. those above 'important' energy
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: master-SetLooperThresholds