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
simplify process for initializing cell-to-cell connections #129
Comments
I would love to discuss this. +100, I literally had the same issue the other day wrapping my head around these methods |
Agreed! The reason that it was moved out of |
I think it's a great policy to keep all hoc references out of |
We should be fine. |
is there still stuff to do here after #164 ? |
Nope, I think you covered it! Thanks @jasmainak! |
Currently, various functions and wrappers are involved in allowing a
NeuronNetwork
instance to establish cell-to-cell (i.e., local network and feed) connections:NeuronNetwork()._build()
calls_parnet_connect()
NeuronNetwork()._parnet_connect()
then callsparconnect()
,parreceive()
, andparconnect_ext()
within one of the child cell classes (e.g., Pyramidal).Pyramidal().parconnect()
then callsPyramidal._connect()
andPyramidal().parreceive()
andPyramidal().parconnect_ext()
callsPyramidal()._parconnect_from_src()
(all of which are inherited from the parent_Cell
class). (Same for the basket cell class.)Finally,
_PC.gid_connect()
is called from thePyramidal()._parconnect_from_src()
which is the lowest common python element in establishing a cell-to-cell connection.It would be nice to rearrange and simply this process so that it is more transparent to
Network
how and when network connections are made. Ideally, there would be a single function, a method in_Cell
, thatNetwork
could call in order to create a given cell-to-cell connection.The text was updated successfully, but these errors were encountered: