www.neuron.yale.edu

No worries, I thought that it wasn't going to be possible. I might try something with proxy artificial cells for each port and RANGE pointers.

To try to answer my own questions then * Is that weight vector a property of the individual events or the NetCon? So as I thought, they are properties of the NetCon, not the event. * Is it possible to send an individual event down selected NetCons or do all events get sent to all connected NetCons? ...

Thanks Ted. * Is that weight vector a property of the individual events or the NetCon? * Is it possible to send an individual event down selected NetCons or do all events get sent to all connected NetCons? I only provided that Purkinje cell example as a concretish example of what I am trying to mode...

Yes, say if condition A is satisfied emit a spike labelled "simple" and if condition B is satisfied emit a spike labelled "complex", which the receiving cell could then treat differently.

This is a bit of unusual question as I am trying to implement the specification of a general neuro-modelling language (www.nineml.net) in Neuron. but would it be possible (including nasty hacks) to get Neuron to emit different types of spikes from a single cell. One possible use case for this featur...

Just to confirm that removing the #include Python/Python.h lines from grids.h, grids.c, rxd.c and rxd_vol.c fixes the problem I had with the compile. A separate issue I ran into during make install was /Library/Developer/CommandLineTools/usr/bin/make install-exec-hook echo "enter install-exec-h...

I can't actually get Neuron to compile on High Sierra. Did you upgrade your existing installation (and not rebuild Neuron) or is it a fresh install? The problem I am getting is with the include line #include <Python/Python.h> in src/nrnpython/grids.h, which looks like it is meant to be commented /**...

Sorry for the delay in replying I only just saw your response. Yes, you could delete the tag now. On the topic of tagging releases, I have noticed that the link to the latest version of neuron seems to be updated as you add bug fixes, is that right? If so, this causes issues for the Homebrew (https:...

Actually, scratch all that. It appears the segfault I am getting on travis is unrelated so I expect the problem I am having is caused by having multiple Neuron installations on my laptop and the PyNN extensions being built against the wrong one.

So probably all good now, sorry for the confusion.

No sorry if my message was a little confusing, I was referring to it being a pitfall os using code that is deemed "prerelease" (i.e. not fully tested) rather than any difference between 'prerelease' and 'release' on GitHub (there shouldn't be any in my understanding). I reverted my build t...

Hi Mike,

The trouble with using a pre-release I realise, but just FYI the combination of that tag and PyNN's 0.9.1 built-in mod files throws a segfault, so I haven't been able to use it.

Cheers,

Tom

Thanks!

Thanks Rob. That works a treat. Although the docs may need amending slightly as using h.neuronhome() on macOS I still received the --prefix/nrn/share value, not the bin directory directly. This may be because I installed from source though.

Hi, I have been trying to work out a fail safe way to get the Neuron install prefix, and thereby the path to nrnivmodl, using only the Python Neuron module. Currently I am assuming that it is on the system path (I don't want to have to rely on NRNHOME being set) but this fails if I need to switch be...

Okay great. I assume it has also been merged into the master branch. If so, would it be possible to tag a release on the github repo so I can point my travis build at it?