Indeed, from this NEST version on, re-sorting of internal connection structures may
invalidate the descriptor tuples that GetConnections() returns, see
If I understand correctly what the developers say at the link above, one should place all
their Connect() calls before all their GetConnections() calls. So, you may safely ignore
that warning if at the moment it appears you do not have any connection descriptors stored
to be then passed to GetStatus() or SetStatus().
student at Kurchatov Institute, Moscow, Russia
Четверг, 20 февраля 2020, 15:57 +03:00 от Lea Steffen
I switched from Nest 2.16 to 2.20 and now I get this warning message:
New connections created, connection descriptors previously obtained using
'GetConnections' are now invalid
This happens at several parts in my code while building synapses with
'sim.Projection(...)' . I use a 'FromListConnector'
and 'STDPMechanism' as synapse_type.
I neversaw this warning in the previous Nest version, is it something to be concerned
I am not quite sure what it is trying to tell me.
Thanks in advance, Lea
M. Sc. Lea Steffen
Wissenschaftlicher Mitarbeiter | Research Scientist
Intelligent Systems and Production Engineering (ISPE)
Interactive Diagnosis and Service Systems (IDS)
FZI Forschungszentrum Informatik
76131 Karlsruhe, Germany
Tel.: +49 721 9654-218