You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible this was fixed a while ago (maybe in #917 or a different one), since both problems now detect almost the same crossing time (there's a bit of precision loss, but much smaller and likely due to loss of absolute precision with the cubic power) and I'm not seeing the Double callback crossing floating pointer reducer errored. Report this issue error reported with the dtmax setting.
When replacing the condition of the
ContinuousCallback
used in the bouncing/free falling ball example https://diffeq.sciml.ai/stable/features/callback_functions/#Example-1:-Bouncing-Ball byu[1]^3=0
, one expects to get the same event timet
for both callbacks. However, one finds:u[1]=0
u[1]^3=0
.MWE:
when
dt_max=0.1
is set, the second callback results in an error:The final
zero_func(Θ)
in https://github.com/SciML/DiffEqBase.jl/blob/master/src/callbacks.jl#L700 looks relatively stable:The text was updated successfully, but these errors were encountered: