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
Cost of implicit solver goes up with length(u)^3 (or ~length(u)^2 with sparsity), while cost of explicit solvers are O(n). This should be factored into the analysis of which solver will be better.
Take into account order difference between nonstiff and stiff solver.
If nonstiff solver is higher order (which is common), the nonstiff solver can be stability constrained,
but switching to a stiff solver won't help since it will be order constrained to a smaller timestep.
Track how close dt is to dtmin to avoid aborting even if stiffness not found This will allow using the nonstiff algorithm more often as long as it isn't at risk of segfaulting.
Track dt for stiff and explicit alg separately and only use the implicit alg if it is maintaining enough higher dt. Similarly, when we switch from the explicit to implicit solver, it's probably better to use the implicit solver's last dt rather than a multiple of the explicit solvers dt since the whole point of having both is that they will want to timestep at different rates.
The text was updated successfully, but these errors were encountered:
If nonstiff solver is higher order (which is common), the nonstiff solver can be stability constrained,
but switching to a stiff solver won't help since it will be order constrained to a smaller timestep.
The text was updated successfully, but these errors were encountered: