-
Notifications
You must be signed in to change notification settings - Fork 70
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
sophiaevent: theta < -1 #85
Comments
Line 16822 in https://github.com/CRPropa/CRPropa3/blob/master/libs/sophia/sophia_interface.f ; Doesn't the fix by Gero already prevent the crash ? |
I cannot reproduce this in a large simulation, so I assume that this is fixed by now. |
I'm actually still running into this crash. Although it doesn't actually crash the simulation, it does say:
This is an example script that, at least sometimes, gives this crash:
|
Hi Tobias,
|
Thank you for the infos. You can enable the storage of the random seeds in TextOutput using
The textoutput will then contain lines such as
To ease reproducibility and debugging it is best to disable multi threading with |
I can reproduce the issue with Saikat's code. The issue appears to be related to particles created in a large distance. Using |
Hi Tobias, You are very much right. I checked and too found that with increased source distances, the message shows up more frequently. Thank you for pointing this out. Does this affect the simulation output in any way? On using |
This error still appears with CRPropa v3.1.6. My sources are up to 215 Mpc and I'm generating 4,000,000 nitrogen particles. This is the end of the output of my log file. It appears that the simulation does not finish according to the progress bar though the number of nucleons and neutrinos in my output file might be about what I would expect? The code itself does not crash as the DintElecaPropagation code runs afterwards. I am not sure if all 4,000,000 are being simulated.
This is the CRPropa component of my code: `
` |
Sophia occasionally crashes with
sophiaevent: theta < -1.D0: -1.0000067840120266
reported by @davidwit
The text was updated successfully, but these errors were encountered: