NIRTorch - Torch for the Neuromorphic Intermediate Representation
PyTorch helpers for the Neuromorphic Intermediate Representation (NIR). This is a no frills python package to enable torch based libraries to translate to NIR.
Installation
pip install nirtorch
Usage
[!TIP] Read the full documentation at neuroir.org/docs.
NIRTorch is typically only interfaced by library/hardwarae developers.
NIRTorch provides two functions nir_to_torch and torch_to_nir that maps NIR graphs to Torch and vice versa.
Translating from NIR to Torch
NIRTorch automatically creates the Torch graph and module behind the scenes.
The only thing you have to do as a developer is to provide a mapping between NIR nodes to PyTorch modules.
That is, a dictionary of nodes with associated functions that produces Torch modules, given a NIR Node (Dict[nir.NIRNode, Callable[[nir.NIRNode], torch.nn.Module]]), where a NIR node is an element in the NIR compute graph, corresponding to neuromorphic ODEs.
Here is one example taken from the Norse library:
# Define NIR -> Norse mapping
my_node_dictionary = {}
def _map_linear(linear: nir.Linear) -> torch.nn.Module:
output_shape, input_shape = linear.weight.shape[-2:]
l = torch.nn.Linear(input_shape, output_shape, bias=False)
l.weight.data = linear.weight
return l
_my_node_dictionary[nir.Linear] = _map_linear
... # And so on for other modules
# Declare a user-facing function to output Norse modules
def from_nir(module: nir.NIRGraph) -> torch.nn.Module:
return nirtorch.nir_to_torch(
module, # The NIR Graph to map
_my_node_dictionary # The dictionary used to map modules to Norse
)
Translating from Torch to NIR
NIRTorch helps construct a NIR graph by tracing through the PyTorch graph module by module.
Our job as a developer is now to provide a mapping that helps translate PyTorch modules into NIR nodes, where a NIR node is an element in the NIR compute graph.
That is, a Dict[torch.nn.Module, Callable[[torch.nn.Module], nir.NIRNode]].
Note that the output node may be a subgraph.
def torch_to_nir( module: torch.nn.Module, module_map: Dict[torch.nn.Module, Callable[[torch.nn.Module], nir.NIRNode]], default_dict: Optional[ Dict[torch.nn.Module, Callable[[torch.nn.Module], nir.NIRNode]] ] = None, ) -> nir.NIRGraph:
# Define Norse -> NIR mapping
_my_module_dict = {}
def _extract_lif_module(module: norse.LIFBoxCell) -> Optional[nir.NIRNode]:
return nir.LIF(
tau=module.p.tau_mem_inv,
v_th=module.p.v_th,
v_leak=module.p.v_leak,
r=torch.ones_like(module.p.v_leak),
)
_my_module_dict[norse.LIFBoxcell] =_extract_lif_module
# Declare a user-facing function to output NIR graphs
def to_nir(module: torch.nn.Module) -> nir.NIRNode:
return nirtorch.torch_to_nir(
module, # The Norse/Torch module to parse
_my_module_dict # The dictionary that maps Norse module to NIR
)
Read the full documentation at neuroir.org/docs.
Acknowledgements
If you use NIRTorch in your work, please cite the our work in Nature Communications
article{NIR2024,
title={Neuromorphic intermediate representation: A unified instruction set for interoperable brain-inspired computing},
author={Pedersen, Jens E. and Abreu, Steven and Jobst, Matthias and Lenz, Gregor and Fra, Vittorio and Bauer, Felix Christian and Muir, Dylan Richard and Zhou, Peng and Vogginger, Bernhard and Heckel, Kade and Urgese, Gianvito and Shankar, Sadasivan and Stewart, Terrence C. and Sheik, Sadique and Eshraghian, Jason K.},
rights={2024 The Author(s)},
DOI={10.1038/s41467-024-52259-9},
number={1},
journal={Nature Communications},
volume={15},
year={2024},
month=sep,
pages={8122},
}
For developers
If you want to make sure that your code is linted correctly on your local machine, use pre-commit to automatically perform checks before every git commit. To use it, first install the package in your environment
pip install pre-commit
and then install the pre-commit hooks that are listed in the root of this repository
pre-commit install
Next time you commit some changes, all the checks will be run!
Metadata
Release files for nirtorch 2.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 | Provenance | |
|---|---|---|---|---|
| nirtorch-2.6.tar.gz | 54.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nirtorch-2.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 82.9 kB
Release files / nirtorch-2.6.tar.gz
| Download URL | nirtorch-2.6.tar.gz |
|---|---|
| Size | 54.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ed4afaf2eef0b125a8355fddb5adadcee17695083f25f93eac4d29143bd6701
|
|
BLAKE2b-256 checksum How to use checksums |
bc03df95dff89702406fca8d66cac57d99e8330ab17507fc0c00013feff9475a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 23, 2026.
Transparency logRelease files / nirtorch-2.6-py3-none-any.whl
| Download URL | nirtorch-2.6-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c114565ce42a95c0b2763f0db1107f2c5de452a4eec593e12cac37e9716838ab
|
|
BLAKE2b-256 checksum How to use checksums |
bc967e01b260a4de736c46af17ab3398bb48afd51b14cf723ad7b492e8845972
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 23, 2026.
Transparency logSecurity for nirtorch 2.6
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for nirtorch-2.6.tar.gz
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 Jan 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.