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

Microcircuit model quick fix for issue #2741 #2749

Merged
merged 2 commits into from
Apr 28, 2023
Merged

Conversation

JoseJVS
Copy link
Contributor

@JoseJVS JoseJVS commented Apr 28, 2023

This pull request proposes a quick fix for the MPI deadlock at the Python API level when accessing kernel information with a subset of the MPI processes available (cf issue #2741) in the microcircuit model.
In the model, this bug is caused by the __setup_next function in network.py#L263 when printing out the rng seed and total number of virtual processes only by rank 0.
Although this pull request does not fix the issue causing this bug, the proposed quickfix does not alter the behavior of the model in any way.

@JoseJVS JoseJVS requested a review from jhnnsnk April 28, 2023 14:09
@heplesser
Copy link
Contributor

This quickfix is just the right fix: One should never call any nest.xyz function inside a block that will only be executed on a subset of MPI ranks.

Since it is a small fix to informational output in an example, I will merge without second review. The failing sphinx_rtd test is due to a configuration error (see #2753), so it should not block merging this PR.

@heplesser heplesser added T: Bug Wrong statements in the code or documentation S: High Should be handled next I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) labels Apr 28, 2023
@heplesser heplesser added this to In progress in Documentation via automation Apr 28, 2023
@heplesser heplesser merged commit cb3aced into nest:master Apr 28, 2023
19 of 20 checks passed
Documentation automation moved this from In progress to Done Apr 28, 2023
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
Projects
Documentation
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants