Neuron (software)
simulation environment for modeling neurons
Neuron is a simulation environment for modeling individual and networks of neurons. It was primarily developed by Michael Hines, John W. Moore, and Ted Carnevale at Yale and Duke.
Neuron models individual neurons via the use of sections that are automatically subdivided into individual compartments, instead of requiring the user to manually create compartments. The primary scripting language is hoc but a Python interface is also available. Programs can be written interactively in a shell, or loaded from a file. Neuron supports parallelization via the MPI protocol.
Neuron is capable of handling diffusion-reaction models, and integrating diffusion functions into models of synapses and cellular networks. Parallelization is possible via internal multithreaded routines, for use on multi-core computers. The properties of the membrane channels of the neuron are simulated using compiled mechanisms written using the NMODL language or by compiled routines operating on internal data structures that are set up with Channel Builder.
Along with the analogous software platform GENESIS, Neuron is the basis for instruction in computational neuroscience in many courses and laboratories around the world.
This brief starts where responsible research should: with the source description of “Neuron (software)” as simulation environment for modeling neurons. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as simulation environment for modeling neurons. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Mar 1, 2026. The linked authority identifier is Q7002467. 1 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Neuron (software)”, its source revision and the description used here.
- Expand the search: follow Neuron (software) primary sources, Neuron (software) archive and Neuron research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Neuron (software)”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Neuron (software)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.