NeuroM
NeuroM is a Python toolkit for the analysis and processing of neuron morphologies.
Documentation
NeuroM documentation is built and hosted on readthedocs.
Migration to v2 or v3 versions
Refer to the doc page on this topic.
Reporting issues
Issues should be reported to the NeuroM github repository issue tracker. The ability and speed with which issues can be resolved depends on how complete and succinct the report is. For this reason, it is recommended that reports be accompanied with
- A minimal but self-contained code sample that reproduces the issue. Minimal means no code that is irrelevant to the issue should be included. Self-contained means it should be possible to run the code without modifications and reproduce the problem.
- The observed and expected output and/or behaviour. If the issue is an error, the python error stack trace is extremely useful.
- The commit ID of the version used. This is particularly important if reporting an error from an older version of NeuroM.
- If reporting a regression, the commit ID of the change that introduced the problem
- If the issue depends on data, a data sample which reproduces the problem should be
up-loaded. But check first whether the error can be reproduced with any of the data
samples available in the
tests/datadirectory.
Citation
When you use the NeuroM software, we ask you to cite the following (this includes poster presentations):
Funding & Acknowledgements
This work has been partially funded by the European Union’s Horizon 2020 Framework Programme for Research and Innovation under the Specific Grant Agreement No. 720270, 785907 (Human Brain Project SGA1/SGA2) and by the EBRAINS research infrastructure, funded from the European Union’s Horizon 2020 Framework Programme for Research and Innovation under the Specific Grant Agreement No. 945539 (Human Brain Project SGA3).
The development of this software was supported by funding to the Blue Brain Project, a research center of the École polytechnique fédérale de Lausanne (EPFL), from the Swiss government’s ETH Board of the Swiss Federal Institutes of Technology.
For license and authors, see LICENSE.txt and AUTHORS.md respectively.
Copyright (c) 2015-2024 Blue Brain Project/EPFL Copyright (c) 2025 Open Brain Institute
4 maintainers
Metadata
4 maintainers
Release files for neurom 4.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| neurom-4.0.6.tar.gz | 548.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| neurom-4.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 659.3 kB
Release files / neurom-4.0.6.tar.gz
| Download URL | neurom-4.0.6.tar.gz |
|---|---|
| Size | 548.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2592d152030ab40d9c05fcc657b11b42607062039e1b84f0b4402595399d5e8
|
|
BLAKE2b-256 checksum How to use checksums |
6a365a39915cc4c427b4bae977f3b5a8f078740c13bbdd33f5b7e91494561bcf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logRelease files / neurom-4.0.6-py3-none-any.whl
| Download URL | neurom-4.0.6-py3-none-any.whl |
|---|---|
| Size | 110.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f0fb3228f443864ba82526b5cdae6d8212709c1d8481087d997c49c10251b390
|
|
BLAKE2b-256 checksum How to use checksums |
c54d4da712ab79d9e5beea51efe9359f78cc0ef0cc176d3f2313f398b5c052a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency log
