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
This has come up a few times in different contexts, most notably for the Network class. The reason one would want to separate the geometry from the actual Neuron code are:
it allows easy pickling of the class, necessary in the context of parallelization
it prevents weird bugs due to the way Neuron works. Neuron holds everything in global workspace. It's better to hold the state of objects in Python as much as possible and not in HOC.
it will allow HNN-core to be easily extensible to new kinds of neuron morphologies and networks
it is also more future proof. If there are updates to Neuron code, we can look in specific designated spots and update the code there. If there is another differential solver engine that we want to use for running our code, it will be straightforward to switch back and forth between Neuron and the others
I tried to come up with a prototype here. This is literally from 3 hours of hacking, so nothing is final but gives an idea what we can aspire for. I would propose a Section, Cell and Network class, each with its own plot method and create or build_in_neuron method.
This 200 line script demos how one could load an arbitrary cell morphology downloaded from the internet and incorporate it in HNN workflow.
I propose we start from cell.py first since network.py is still undergoing a few changes.
The text was updated successfully, but these errors were encountered:
This has come up a few times in different contexts, most notably for the
Network
class. The reason one would want to separate the geometry from the actual Neuron code are:This came up during our discussion with @blakecaldwell and @rythorpe
I tried to come up with a prototype here. This is literally from 3 hours of hacking, so nothing is final but gives an idea what we can aspire for. I would propose a
Section
,Cell
andNetwork
class, each with its ownplot
method andcreate
orbuild_in_neuron
method.This 200 line script demos how one could load an arbitrary cell morphology downloaded from the internet and incorporate it in HNN workflow.
I propose we start from
cell.py
first sincenetwork.py
is still undergoing a few changes.The text was updated successfully, but these errors were encountered: