Skip to content
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

Automatically stop Simulate() if update time becomes too long #2033

Closed
heplesser opened this issue May 10, 2021 · 0 comments · Fixed by #2095
Closed

Automatically stop Simulate() if update time becomes too long #2033

heplesser opened this issue May 10, 2021 · 0 comments · Fixed by #2095
Assignees
Labels
good first issue Good for newcomers I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Enhancement New functionality, model or documentation
Milestone

Comments

@heplesser
Copy link
Contributor

Is your feature request related to a problem? Please describe.

NEST simulations can slow down significantly if network activity becomes high, even more so if neuron models use adaptive-stepsize solvers. Currently, there is no way to interrupt this simulation except killing the entire NEST process.

Describe the solution you'd like

The user sets an upper limit for the duration of a single update time slice (length: minimum delay), e.g.,

nest.SetKernelStatus({'max_update_duration': 1.0})

to set a limit of 1 second wall-clock time for a single min-delay-length update step. If a step takes longer, simulation terminates.

Additional context
See also this mailing list discussion: https://www.nest-simulator.org/mailinglist/hyperkitty/list/users@nest-simulator.org/thread/FQ6VDQ7EDSSKRIHMMRETIAIXK43A5GCZ/

@heplesser heplesser added T: Enhancement New functionality, model or documentation S: Normal Handle this with default priority I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) good first issue Good for newcomers labels May 10, 2021
@heplesser heplesser self-assigned this Jun 30, 2021
@heplesser heplesser added this to the NEST 3.2 milestone Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Enhancement New functionality, model or documentation
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant