www.neuron.yale.edu

Hmmm... looks like that example depends on a change introduced about a month ago... so it's available in the "pip install" version for mac/linux or the windows nightly build . (Don't try to pip install on Windows, that will give a VERY old version of NEURON.) Sorry about that. So I guess the best so...

Unfortunately the .plot for both matplotlib and plotly (available in 8.0 development version) does not currently support the .color or .color_list values and instead always color based on the value of some variable (v, by default). (Note that you can use .mark as in the documentation to highlight sp...

Thanks for pointing this out.

The old link works now too.

Python provides a standard way of using a string to grab a property, namely the getattr function. e.g. if you have a section called soma and you wanted to get a pointer to a specific variable var from the 0.5 location, you could do ptr = getattr(soma(0.5).hh, f'_ref_{var}') Similarly, a second getat...

There was a significant revamp of the internals from 7.4 to 7.7 with the intent of speeding up calculations but it likely broke anything that depended on overriding internal functions. What kind of connections do you need? callbacks at each time step? reading and writing concentrations? do you need ...

Why did you compile NEURON from source?

Do you get this problem if you use the version from
How are you compiling the mod files? The x86_64 should appear in whatever folder you run nrnivmodl from.

You can't drop onto the main menu window directly, but I believe in Windows you can drop onto the icon . Three other options: (1) Select File - load hoc, change the filter from *.hoc to *.nrm, and then load your model that way. (2) type (using the correct filename): load_file("filename.nrm") (3) ope...

This is harmless. You can ignore it. Even though you're not using Python explicitly, NEURON will connect to Python to have it available (and Python is needed to enable certain functions). What happened was there was something in the NEURON internals that did not raise a Python warning until a change...

You are creating a single file because your file creation is happening once, outside of the for loop. If you look at the Python example, you'll see I'm creating a new file every time with a different filename based on the trial number (trial0.csv, trial1.csv, trial2.csv, ...) You can generate filena...

Python, HOC, and most programming languages use a for loop to run the same code a fixed number of times. e.g. in Python, we'd write for trial in range(100): # do stuff here and in HOC, we might write: for (trial = 0; trial < 100; trial += 1) { // do stuff here } NEURON provides the h.Random (or just...

Simple work-around: don't compile NEURON yourself. :) BMTK supports all the way back to NEURON 7.4 which is almost 5 years old, and any guidance you're seeing about issues with NEURON and Anaconda (which we now explicitly suggest using in the NEURON quickstart guide ) pertains to old versions of NEU...

Oof. My mistake. Ted is right, of course. The key thing I was missing is that the values should be set based on the position of the center of the segment, which means that they must be strictly inside the interval specified. I was effectively interpolating from the center of the first segment to the...

You'd have to do it with a for loop. Here's a generic function that does this for you: def range_assignment(sec, var, start, stop): """linearly assign values between start and stop to each segment.var in section""" import numpy as np for seg, val in zip(sec, np.linspace(start, stop, sec.nseg)): seta...

The integration advance failed, even when it tried using a really tiny timestep. One possible cause of this is when some of your state variables have found themselves in an invalid place. You could try reducing the atol to see if that helps, because it'll force the system to more carefully track val...

When you run nrnivmodl on macOS (and I assume Linux, but I didn't check), it puts the compiled version of the mod files in the x86_64/.libs/libnrnmech.so file. (You won't see this if you just do an "ls" because macOS and Linux hide file and folder names beginning with a . by default but you can see ...