-
Notifications
You must be signed in to change notification settings - Fork 99
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
Mercury crashes after a collision with the central particle #94
Comments
Actually, the particles get removed from the code here (amuse_helpers.for, L951, in routine mal_hcon, which is used for the default integrator=10). After commenting out the line, the particle is not removed and the code gets to an infinite loop (since the particle is identified to hit the central again and again). |
I think the best solution would be to include collision detection - there was some work on this but needs to be restarted... |
A possible workaround is to set the radius of the central body ( |
workaround availalble |
It seems that Mercury crashes after a collision with the central particle occurs. I think this is becuase Mercury (always) removes the particle that hits the central body (mercury6_2.for, L228) and this is not comunicated to amuse. A conflict than appears in the evolve_model of interface.py (L1394). A minimal example follows.
The output info file 'm_info_file.out' has to exist, otherwise the example stalls. I think this is related to the issue #95 (and the earlier #91 where the solution requires calling commit_parameters() to set up the output files).
The text was updated successfully, but these errors were encountered: