-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
Add option to specify maximum number of consecutively rejected steps #2229
Comments
A different, but probably more complicated solution could be to add a different kind of |
I believe this was fixed (via different means) in SciML/SciMLBase.jl#693. Specifically, on new SciMLBase, this gives
|
Amazing, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Without default
dtmin
(#2098), automatic time stepping methods reduce the time step beloweps()
at instabilities and reject all steps infinitely.MWE:
As shown by the many x at the end,
f
is still called, but there are no more accepted steps to trigger the callback until we reachmaxiters
.In simulation frameworks, this will cause apparent freezing of the simulation, as suddenly no more output is generated when an instability is reached, but the simulation doesn't terminate.
I suggest adding an option to limit the maximum number of consecutively rejected steps to terminate time integration in these cases where it gets stuck in an infinite loop until
maxiters
is reached (which might take a very long time for large simulations and defaultmaxiters
).Note that setting
dtmin
is not an option, as perfectly stable simulations are terminated when different callbacks happen to add tstops that are very close together (#1616):CC @ranocha
The text was updated successfully, but these errors were encountered: