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

COSIMA Activation - Skips Events and Freezes #98

Open
joshhooker opened this issue Sep 23, 2024 · 3 comments
Open

COSIMA Activation - Skips Events and Freezes #98

joshhooker opened this issue Sep 23, 2024 · 3 comments

Comments

@joshhooker
Copy link

joshhooker commented Sep 23, 2024

On the 11.2 branch, the simulation will run until the event number is skipped and the events stop updating. All of the files do not continue to be updated.

Running COSIMA with 1 thread and the following options:

#Physics parameters:
PhysicsListHD qgsp-bic-hp
PhysicsListEM LivermorePol
DecayMode ActivationBuildup

#Storage parameters
StoreCalibrated true
StoreSimulationInfo all
DiscretizeHits true

#Particle range cuts:
DefaultRangeCut 0.005

#Simulate the primary protons and all secondaries:
Run Step1
Step1.FileName output.Phase1.BuildUp
Step1.Events 200000000
Step1.IsotopeProductionFile output.Phase1.BuildUp.dat

Screenshot 2024-09-23 at 1 06 04 PM

Any ideas on what would cause this?

@zoglauer
Copy link
Owner

Thanks for reporting.

Which branch are you using?
All branches using Geant4 11.2 are early development branches, which just have been tested with COSI. And I know there are still a few bugs left to fix.

Do you want to switch to the main branch which uses Geant4 10.2?

@joshhooker
Copy link
Author

Thank you for the fast reply, Andreas!

I am currently on the feature/geant_11.2 branch.

I am unable to use MEGAlib with Geant4 10.2 because I am using materials with a Z > 92 and Geant4 10.2 appears to have issues with these heavy materials even with the AllowForHeavyElements flag turned on.

@zoglauer
Copy link
Owner

Is there a chance you could either email me or upload a geometry file which reproduces this issue?

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

No branches or pull requests

2 participants