-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run_regularly() with large dt in standalone mode #1054
Comments
Hi Felix, thanks for the report, I can reproduce the issue with your example script. It seems to be specific to C++ standalone mode, I could imagine that there is some conversion of time to integer time steps at some point that goes over 32bit bounds, or something along these lines. I'll have a closer look soon. |
Thanks for the fast reply! I'm very curious to learn what's happening here. I wasn't successful in reproducing the behaviour in a minimal example network, so I've cut my current simulation down to what I hope is a manageable size to track down the issue. The initial idea was to set the |
I looked into this a bit, and I no longer think it has to do with 32bit integers. It is rather about some rounding tests where we consider things to fall into the same time step if they differ by less than a 10000th of dt – in your example, the first run time is less than that (for the |
As mentioned in #1057 , removing the
This issue does not seem to be fixed by a591214. |
I'm running into an issue with using run_regularly() in standalone mode that I believe could possibly be a bug.
Below is the network that reproduces the issue. The simulation segment 'T2', although very long, is completely skipped. For example I get an output of
Two things fix the problem:
Brian2 version '2.2.1'. Can anyone reproduce this? Thanks!
The text was updated successfully, but these errors were encountered: