You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The answer being that as edges.iter_connections iterates over all edge populations and their source node populations, it ends up finding projections and a virtual node population that does not have synapse_class or, really, any attributes.
I don't think it makes sense that iter_connections or any circuit.edges functionalities would raise on these occasions. Especially so, as it is very difficult to understand the issue from the stacktrace.
I propose we don't raise/do silently handle the error(s) in the background on situations such as the above.
@edasubert approached me with a question as to why does this happen:
The answer being that as
edges.iter_connections
iterates over all edge populations and their source node populations, it ends up finding projections and a virtual node population that does not havesynapse_class
or, really, any attributes.I don't think it makes sense that
iter_connections
or anycircuit.edges
functionalities would raise on these occasions. Especially so, as it is very difficult to understand the issue from the stacktrace.I propose we don't raise/do silently handle the error(s) in the background on situations such as the above.
Any thoughts?
@eleftherioszisis , @edasubert, @GianlucaFicarelli
The text was updated successfully, but these errors were encountered: