Add note about maximum enforced timestep #3249
Conversation
clinssen
added
S: Normal
|
@clinssen, could you please provide a description for this PR? |
| A maximum integration step size of 10 μs is enforced, regardless of the | ||
| resolution set in the NEST kernel. |
There was a problem hiding this comment.
This is not correct. init_buffers_() initialises B_.IntegrationStep_ to min(0.01, Time::get_resolution().get_ms()), but after that the adaptive stepsize mechanism controls IntegrationStep_. The initialization line has been unchanged since 2.6.1 at least, and I am not sure why we have it at all, given that we are using an adaptive stepsize solver. It might be a leftover from very early versions with a fixed-stepsize solver.
There was a problem hiding this comment.
@clinssen I think in this case the code is actually wrong/outdated. We us an adaptive-stepsize solver, so we should not need to control the integration time step manually. See also inline comment. I'd suggest to change the code instead (but check for consequences).
Add note about maximum enforced timestep in all aeif models.