Message: Re: Range Cuts (via Setcuts) not working in physics list or UI commands Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Feedback Re: Range Cuts (via Setcuts) not working in physics list or UI commands 

Forum: Event and Track Management
Re: Question Range Cuts (via Setcuts) not working in physics list or UI commands (Giuseppe Caporaso)
Date: 07 Aug, 2018
From: Jonathan Madsen <Jonathan Madsen>

Please provide the full log of a run with one event and set the tracking verbose to level 2, e.g.:

    /tracking/verbose 2
    /run/beamOn 1

This should produce a "List of 2ndaries" entry in the tracking log like below when secondaries are being produced:

G4WT0 > *********************************************************************************************************
G4WT0 > * G4Track Information:   Particle = e-,   Track ID = 1,   Parent ID = 0
G4WT0 > *********************************************************************************************************
G4WT0 > 
G4WT0 > Step#    X(mm)    Y(mm)    Z(mm) KinE(MeV)  dE(MeV) StepLeng TrackLeng  NextVolume ProcName
G4WT0 >     0        0        0        0       100        0        0         0 Target_2_2_2 initStep
G4WT0 >     1    -3.95     8.86    -2.42      96.7     3.35       10        10 Target_2_2_2 StepLimiter
G4WT0 >     2     -7.4     16.4    -4.59      93.5     2.85     8.56      18.6 Target_2_2_2 eBrem
G4WT0 >     :----- List of 2ndaries - #SpawnInStep=  1(Rest= 0,Along= 0,Post= 1), #SpawnTotal=  1 ---------------
G4WT0 >     :      -7.4      16.4     -4.59     0.313              gamma
G4WT0 >     :----------------------------------------------------------------- EndOf2ndaries Info ---------------
G4WT0 >     3    -8.33     18.4    -5.14      91.5    0.892     2.27      20.8 Target_2_2_2 eBrem
G4WT0 >     :----- List of 2ndaries - #SpawnInStep=  1(Rest= 0,Along= 0,Post= 1), #SpawnTotal=  2 ---------------
G4WT0 >     :     -8.33      18.4     -5.14      1.11              gamma
G4WT0 >     :----------------------------------------------------------------- EndOf2ndaries Info ---------------
G4WT0 >     4    -12.4     27.1    -7.73      87.6     3.88       10      30.8 Target_2_2_2 StepLimiter

If you are running within a UNIX shell, run:

./[application] [macro] &> run.log e.g. ./exampleB1 run.mac &> run.log

and attach the "run.log" file.

Also, updating your application to run to utilize Geant4 multithreading (MT) will produce far more speed up than changing the physics. Your detector construction should have a ConstructSDandField() overload for your sensitive detector for MT. You can find info on the migration in the user docs and here:

https://twiki.cern.ch/twiki/bin/view/Geant4/QuickMigrationGuideForGeant4V10

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

1 More: Re: Range Cuts (via Setcuts) not working in physics list or UI commands   (Giuseppe Caporaso - 07 Aug, 2018)
(_ Feedback: Re: Range Cuts (via Setcuts) not working in physics list or UI commands   (Jonathan Madsen - 07 Aug, 2018)
(_ Ok: Re: Range Cuts (via Setcuts) not working in physics list or UI commands   (Giuseppe Caporaso - 08 Aug, 2018)
 Add Message Add Message
to: "Re: Range Cuts (via Setcuts) not working in physics list or UI commands"

 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 ]