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

Follow up on structural plasticity with multi-threaded simulations not working correctly #633

Open
sdiazpier opened this issue Jan 19, 2017 · 4 comments
Assignees
Labels
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 stale Automatic marker for inactivity, please have another look here T: Enhancement New functionality, model or documentation

Comments

@sdiazpier
Copy link
Contributor

This is a follow up issue for #290 where the problem was that structural plasticity currently does not work properly when multiple threads are enabled. With the PR #629 an exception is now raised when the user tries to enable structural plasticity in combination with a multi-threaded setup.
However the underlying issue is still unsolved and needs to be addressed.

@heplesser heplesser added this to the NEST 3.0 milestone Jun 29, 2017
@heplesser heplesser added ZC: Kernel DO NOT USE THIS LABEL I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) ZP: Pending DO NOT USE THIS LABEL S: Normal Handle this with default priority T: Enhancement New functionality, model or documentation labels Jun 29, 2017
@heplesser
Copy link
Contributor

@sdiazpier Any news on this?

@sdiazpier
Copy link
Contributor Author

No news here, I need to do more tests on it to identify the source of this problem.

@terhorstd terhorstd removed this from the NEST 3.0 milestone Nov 7, 2018
@heplesser heplesser removed ZC: Kernel DO NOT USE THIS LABEL ZP: Pending DO NOT USE THIS LABEL labels Apr 7, 2020
@heplesser
Copy link
Contributor

@sdiazpier Ping!?

@github-actions
Copy link

github-actions bot commented Sep 3, 2021

Issue automatically marked stale!

@github-actions github-actions bot added the stale Automatic marker for inactivity, please have another look here label Sep 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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 stale Automatic marker for inactivity, please have another look here T: Enhancement New functionality, model or documentation
Projects
Development

No branches or pull requests

3 participants