Software for computational neuroscience
Upstream packages
The following tools are among the software currently tested in NeuroFedora and can be installed directly from upstream forges (e.g. PyPi). You can see the tests results here.
Python packages
Software | Summary | pip (PyPi) | Notes |
---|---|---|---|
Blue Brain Python Optimisation Library (bluepyopt). |
|
||
A clock-driven simulator for spiking neural networks. |
|
||
A module for modeling extracellular potentials of multicompartment neuron models built on NEURON. |
|
||
A Python library for working with NeuroML descriptions of neuronal models. |
|
||
|
Does not currently install on Python 3.13. https://github.com/nest/NEAT/issues/183 |
||
A Python package to develop, simulate and analyse biological neuronal networks in NEURON. |
|
||
NeuroM: a light-weight neuron morphology analysis package. |
|
||
A common JSON/YAML based format for compact network specification, closely tied to NeuroML v2. |
|
||
Empirically-based simulator for modeling neurons and networks of neurons. |
|
||
A Python library for optimising neuronal models. |
|
||
A Python library for working with the Low Entropy Model Specification language (LEMS). |
|
||
Python scripting interface of MOOSE Simulator (https://moose.ncbs.res.in). |
|
||
Python utilities for NeuroML. |
|
||
A Python package for simulator-independent specification of neuronal network models. |
|
||
A test-driven framework for formally validating scientific models against data. |
|
System packages
The following general purpose utilties are included in the repositories:
Software | Install with | Notes |
---|---|---|
|
A high-performance library for Computational Neuroscience simulations |
|
|
A package to simulate recurrent spiking neural networks with spike timing dependent plasticity (STDP). |
|
|
Common interfaces for neuronal simulators |
|
|
Systems Biology Markup Language library |
|
|
A Python and C++ interface to the SONATA format |
|
|
Multiscale Neuroscience and Systems Biology Simulator |
|
|
The NEST simulator |
Want to help? Learn how to contribute to Fedora Docs ›