Problem 2040 - stack management
Summary: stack management
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: event (show other problems)
Version: other
Hardware: All All
: P4 minor
Assignee: asai
URL:
Depends on:
Blocks:
 
Reported: 2018-03-05 18:12 CET by michel.maire
Modified: 2018-05-23 11:32 CEST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description michel.maire 2018-03-05 18:12:45 CET
HI Makoto,

 Here an example, again from radioactive decay.

 In the decay Tc99[142 keV] --> Tc99 -->Ru99, the stack behaves as expected : last_in first_out
 But not if we start from another excited state : Tc99[181 keV]
 
 # macro for rdecay01 example
 #
 /run/verbose 1
 #
 /gun/particle ion
 ##/gun/ion 43 99 0 181.093
 /gun/ion 43 99 0 142.683
 #
 /tracking/verbose 2
 /run/beamOn 1
 /tracking/verbose 0
 #
 ###/run/printProgress 10000
 ###/run/beamOn 100000
Comment 1 Andrea Dotti 2018-03-05 20:31:14 CET
Re-assign to Makoto
Comment 2 asai 2018-05-23 11:32:29 CEST
G4SmartTrackStack was supposed to be optional but due to some misunderstandings it was used by default. It changes the order of popping-out tracks to stay with the same kind of particles as much as possible. Now it becomes back to be optional, and this fix will go with Geant4 10.4-patch02. To fix this for current/earlier version, please remove line #16 in CMakeLists.txt in the geant4/event directory.

http://www-geant4.kek.jp/lxr/source/event/CMakeLists.txt#L16