Hi!

I agree with Jan that the connections should be updated regardless of you using RunManager or not. Can you please send a minimal reproducer script that triggers the erroneous behavior? It is quite hard to reproduce the error from just your verbal description.

There seems to be a misconception about the purpose of stimulation backends here. The mpi backend you are referring to allows to send stimulation device parameters from and external application to NEST at runtime via MPI (hence the name of the backend). When using this backend, the file in {data_path}/{data_prefix}{label}/{node_id}.txt ({node_id} being the device’s node ID, not the target neuron’s) will specify the MPI address where data comes from (i.e. the external application), not the data you want to set (the rate in your case).

Please see these documentation pages for more information:

• https://nest-simulator.readthedocs.io/en/v3.3/guides/stimulate_the_network.html
• https://nest-simulator.readthedocs.io/en/v3.3/models/stimulation_backend_mpi.html

Cheers,
Jochen!

-- 
Dr. Jochen Martin Eppler (he/him)
Simulation and Data Lab Neuroscience
Jülich Supercomputing Centre
Institute for Advanced Simulation
---------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Stefan Müller
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens,
Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior
---------------------------------------------------------------------