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
using OrdinaryDiffEq
f = function (u, p, t)
-u + sin(-t)
end
prob = ODEProblem(f, 1.0, (0.0, -10.0))
condition(out, u, t, integrator) = out[:] = [-t - 2.95, -t - 2.95]
function affect!(integrator, idx)
@show integrator, idx
integrator.u = integrator.u + 2
end
callback = VectorContinuousCallback(condition, affect!, 2)
sol = solve(prob, Tsit5(), callback = callback)
Of course for trivial cases the answer is "don't do that" but when different components or computations end up with the same event, this causes problems.
I've been looking into it a little bit and it seems that find_callback_time gets a vector of all the callbacks that changed sign, so I imagine it should check if after the rootfinding it can "check off" multiple events and move on, but I don't fully understand the code yet, and maybe it's a lot more complicated than that, judging by all the comment about floating point details.
The text was updated successfully, but these errors were encountered:
MWE:
Of course for trivial cases the answer is "don't do that" but when different components or computations end up with the same event, this causes problems.
I've been looking into it a little bit and it seems that
find_callback_time
gets a vector of all the callbacks that changed sign, so I imagine it should check if after the rootfinding it can "check off" multiple events and move on, but I don't fully understand the code yet, and maybe it's a lot more complicated than that, judging by all the comment about floating point details.The text was updated successfully, but these errors were encountered: