www.neuron.yale.edu

The PYTHONPATH should be export PYTHONPATH=$HOME/local/lib64/python2.6/site-packages. But are you sure the $HOME got expanded and there is not a OME folder in nrn/src/nrnpython The latter is what happened to me on my desktop with I used your configure options and I needed hines@hines-T7500:~/neuron/...

which installed two folders in $HOME/local That is because a default build and make install installs the neuron module by default in <prefix>/lib/python . This can be turned off with the configure option --disable-pysetup Alternatively, you can avoid the manual execution of setup.py with the config...

which installed two folders in $HOME/local That is because a default build and make install installs the neuron module by default in <prefix>/lib/python . This can be turned off with the configure option --disable-pysetup Alternatively, you can avoid the manual execution of setup.py with the config...

vecevent.mod has been updated to be compatible with CoreNEURON. See https://github.com/neuronsimulator/nrn/commit/7adabc176763386031a9c88ef5218a64f9402219 This kind of VERBATIM code is quite painful. I need to consider an NMODL syntax for easily describing the use of Random variables and Vectors in ...

i've updated vecevent.mod (VecStim)
Just need to test with coreneuron.
When it is working I'll push to the github repository and mention that here.

look at nrn/src/nrnoc/netstim.mod for an analogy. You need to replace POINTER with BBCOREPOINTER and introduce
bbcore_write and bbcore_read implementations. Anything containing the string BBCORE is of interest.
I should update vecstim.mod to make it compatible with CoreNEURON.

Using
neurondemo -python
#select release model yields
'0b11110111'
If you send me the code fragment that returns I can look into it in more detail.

from nrn/src/nrnoc/eion.c /*the bitmap is 03 concentration unused, nrnocCONST, DEP, STATE 04 initialize concentrations 030 reversal potential unused, nrnocCONST, DEP, STATE 040 initialize reversal potential 0100 calc reversal during fadvance 0200 ci being written by a model 0400 co being written by ...

is there a reason

I don't know the reason yet.

In my notebook, the output from that function shows up in the terminal

Today I pushed a fix in the master branch of github.com/neuronsimulator/nrn that directs the output of
h.allobjects() to stdout of Python.

Something mysterious is going on with jupyter that I can't yet quite figure out. Can you work around the problem with print (soma.psection()) Everytime Jupyter default pretty prints the result of soma.psection(), the hoc reference count of the POINT_PROCESS is incremented and never gets decremented ...

You only need to call sec.simulate(0) for one section in a cell and all the sections in that cell will follow along. However, if you call sec.simulate(0) for several or all of the sections in a cell it should not matter as any after the first will do nothing. for sec in neuron.h.allsec(): sec.simula...

Ok. The do-not-simulate branch is ready to try. the log message is commit 0ebc0f8ff10ddd68b8cd3fe12cfb5e78bd9dd6a5 (HEAD -> do-not-simulate, origin/do-not-simulate) Author: Michael Hines <michael.hines@yale.edu> Date: Thu Jan 24 13:38:54 2019 -0500 nrn.Section.simulate(False) causes the entire tree ...

You've convinced me that removing cells from a simulation without destroying them is a useful feature. I've concluded that the basic functionality will have a straightforward implementation. More rarely used combinations of features that will break the system can raise errors until the implementatio...

I was completely unaware that Nengo can create a NEURON Section. I don't know very much about Nengo but thought it had its own native implementation of models. Can you point me to a document that explains more of the Nengo workflow related to NEURON. As I think about the possibility of removing a Se...

Sorry. I'm not quite seeing the problem yet. I'm hearing that when build_connection is called, that you need to build something that you can optimize and then throw it away. Can you not also save the relevant info of each build_connection call (and return value) in set/dict/list for later simulation...