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

Problem updating connections with structural plasticity and multiple threads #290

Closed
sdiazpier opened this issue Apr 4, 2016 · 6 comments
Assignees
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: High Should be handled next T: Bug Wrong statements in the code or documentation ZC: Kernel DO NOT USE THIS LABEL ZP: PR Created DO NOT USE THIS LABEL
Milestone

Comments

@sdiazpier
Copy link
Contributor

Unwanted behaviour is observed when updating the connectivity of the network using structural plasticity with multiple threads. This is not the case when multiple MPI processes are used. It seems like it is a problem with the structural plasticity manager while updating the number of deleted synapses.

@heplesser
Copy link
Contributor

@sdiazpier Could you add a script reproducing this problem? It should be as compact as possible and preferably written in SLI so we can develop a regression test from it.

@heplesser heplesser added the T: Bug Wrong statements in the code or documentation label Oct 31, 2016
@heplesser
Copy link
Contributor

@sdiazpier What is the status on this?

@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: High Should be handled next labels Nov 17, 2016
@heplesser heplesser added this to the NEST 2.12 milestone Nov 17, 2016
@heplesser
Copy link
Contributor

Per 2.12, NEST should at least prohibit simulations with structural plasticity and multiple threads, if we cannot solve this issue properly by then.

@sanjayankur31
Copy link
Contributor

sanjayankur31 commented Nov 17, 2016

@sdiazpier - can you please expand on "unwanted behaviour"? I'm using SP with MPI but I haven't really been analysing the data yet. If you can give us more information, I can narrow down the issue. Either a test case or a data dump from a test case would be most helpful?

@heplesser
Copy link
Contributor

@sdiazpier Could you create a follow-up issue to remind us to check whether and how structural plasticity can be enabled in multi-threaded simulations?

@heplesser
Copy link
Contributor

Using structural plasticity is now blocked when using multiple threads (see #629) and #633 is created as a follow-up issue. Thus closing this issue.

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: High Should be handled next T: Bug Wrong statements in the code or documentation ZC: Kernel DO NOT USE THIS LABEL ZP: PR Created DO NOT USE THIS LABEL
Projects
None yet
Development

No branches or pull requests

3 participants