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
When I tried to reproduce a previous Ganymede tracing results with Vern9() using recent versions of OrdinaryDiffEq.jl, I noticed that the performance deceased a lot. After investigating the issue, I noticed that the adaptive timestepping control must have changed between versions, because most of the time is spent in advancing with extremely small dt near the planet boundary where the magnetic field becomes stronger and isoutofdomain may take place.
According to the common solver options, one possible fix to recover the previous speed performance is to set a dtmin. This needs further testing.
For the Boris pusher, we can try the adaptive timestepping scheme implemented in FLEKS. Instead of using characteristic wave speeds, we can use local gyroperiod to limit the timesteps.
When I tried to reproduce a previous Ganymede tracing results with
Vern9()
using recent versions of OrdinaryDiffEq.jl, I noticed that the performance deceased a lot. After investigating the issue, I noticed that the adaptive timestepping control must have changed between versions, because most of the time is spent in advancing with extremely smalldt
near the planet boundary where the magnetic field becomes stronger andisoutofdomain
may take place.According to the common solver options, one possible fix to recover the previous speed performance is to set a
dtmin
. This needs further testing.P.S. I don't really understand how the adaptive timestepping schemes work.
The text was updated successfully, but these errors were encountered: