GetConnections not working with multiple threads in combination with detailed timers.

[JanVogelsang]

Calling GetConnections when using multiple threads triggers the assertion in line 207 of vp_manager.cpp. The following script reproduces the issue:

import nest

nest.total_num_virtual_procs = 2

neuron = nest.Create("parrot_neuron")
nest.Connect(neuron, neuron)

nest.GetConnections()

[heplesser]

@JanVogelsang The code works on my computer, but it may depend on build details. How did you build NEST (which cmake options)?

[JanVogelsang]

Here is the list of (relevant) cmake options I use:
-Dwith-optimize=OFF
-Dwith-debug=ON
-Dwith-mpi=ON
-Dwith-cpp-std="c++17"
-Dwith-models="iaf_psc_alpha;static_synapse;poisson_generator;spike_recorder;weight_recorder;stdp_pl_synapse_hom;parrot_neuron;music_event_in_proxy;music_event_out_proxy"
-Dwith-detailed-timers=ON
-Dwith-mpi-sync-timer=ON

[heplesser]

I have localized the problem now. If we have detailed, threaded timers, the stopwatch start here (

nest-simulator/nestkernel/per_thread_bool_indicator.cpp

Line 84 in 09b349c

kernel().get_omp_synchronization_construction_stopwatch().start();

) triggers a check for running in parallel here (

nest-simulator/nestkernel/stopwatch_impl.h

Line 36 in 09b349c

kernel().vp_manager.assert_thread_parallel();

) which fails, because we get here from a serial context here (

nest-simulator/nestkernel/connection_manager.cpp

Line 1227 in 09b349c

if ( is_source_table_cleared() )

).

I am not yet sure how to resolve this. We are doing something serially here which makes eminent sense to do serially, but then end up in a place that may also be called from a parallel context so the assertion does make sense.

[JanVogelsang]

Hm true. We could probably move the omp parallel outside of the if ( not source.get() and not target.get() ) and do the if ( is_source_table_cleared() ) inside the parallel region.

[heplesser]

Hm true. We could probably move the omp parallel outside of the if ( not source.get() and not target.get() ) and do the if ( is_source_table_cleared() ) inside the parallel region.

Yes, that should work. We could do the check for 0 connections first, then enter #omp parallel. Then we would also just need the parallel context once outside the entire if-elseif-chain. And when we are at it, we might want to split the function into three, one for each of the three cases we have (the fourth is hidden deep in the third with another if) for better readability, keeping any function shorter than a screen height.

[JanVogelsang]

Sounds good! Are you already on it or should I quickly implement it?

[heplesser]

It would be great if you could create a PR. I’ll be happy to review 😊. Best, Hans Ekkehard

…

-- Prof. Dr. Hans Ekkehard Plesser Research Committee Chair, Faculty of Science and Technology Head, Department of Data Science Department of Data Science Faculty of Science and Technology Norwegian University of Life Sciences PO Box 5003, 1432 Aas, Norway Phone +47 6723 1560 Email ***@***.******@***.***> Home http://arken.nmbu.no/~plesser From: Jan Vogelsang ***@***.***> Date: Wednesday, 26 March 2025 at 10:14 To: nest/nest-simulator ***@***.***> Cc: Hans Ekkehard Plesser ***@***.***>, Comment ***@***.***> Subject: Re: [nest/nest-simulator] GetConnections not working with multiple threads (Issue #3442) Sounds good! Are you already on it or should I quickly implement it? — Reply to this email directly, view it on GitHub<#3442 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAICWPGEC5676G7XVTT44JD2WJOUPAVCNFSM6AAAAABZXJERHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJTGY4TAOJWGU>. You are receiving this because you commented.Message ID: ***@***.***> [Image removed by sender. JanVogelsang]JanVogelsang left a comment (nest/nest-simulator#3442)<#3442 (comment)> Sounds good! Are you already on it or should I quickly implement it? — Reply to this email directly, view it on GitHub<#3442 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAICWPGEC5676G7XVTT44JD2WJOUPAVCNFSM6AAAAABZXJERHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJTGY4TAOJWGU>. You are receiving this because you commented.Message ID: ***@***.***>