Repository navigation
interpreter spine
Phase 1 lifts the models onto the Neuromorphic Intermediate Representation
(NIR) and proves the translation. A
model is declared once as a TopologySpec and rendered twice: into the
snnTorch module that trains, and into the nir.NIRGraph that exports.
Pick a topology by name — the training server takes a topology field and
the CLI takes --topology:
| Preset | Shape |
|---|---|
fc_legacy |
The original two-layer FC LIF SpikingNet (default) |
fc_small |
Small FC LIF with an explicit flatten entry stage |
conv_net |
Conv/pool feature extractor with a linear LIF readout |
recurrent_net |
FC LIF with a one-step delayed feedback edge |
fc_legacy stays the default and keeps SpikingNet's
_fc1/_lif1/_fc2/_lif2 state-dict keys, so existing checkpoints load
and infer unchanged.
spikeforge/neurons/ maps a neuron name to its snnTorch factory and
its canonical NIR parameter contract. The registry ships leaky,
lapicque, synaptic, and recurrent (RLeaky) neurons.
-
to_nir(spec, module)exports a JSON-ablenir.NIRGraph;graph_summarydescribes its nodes and edges. -
NirInterpreterexecutes the exported graph independently of snnTorch, sovalidate(spec, module, spikes)reports a genuineValidationReport(per-layer max/mean/relative error plus spike agreement, and an overallwithin_toleranceflag). Every shipped preset validates with bit-exact spikes. - All
nir/nirtorchimports are confined tonir_bridge/api.py.
Headless export and validate commands. validate exits non-zero when a
report falls outside tolerance, so it doubles as a CI gate:
python -m spikeforge.cli.verify export --topology conv_net
python -m spikeforge.cli.verify export --topology fc_legacy --out g.json
python -m spikeforge.cli.verify validate --topology conv_net
python -m spikeforge.cli.verify validate --topology recurrent_netThe server answers two new client actions: nir_export returns the graph
summary for the active or configured topology, and nir_validate returns a
drift report for the active model.
- Home
- Architecture
- Backend Execution
- Benchmarks
- Dashboard
- Development
- Event Datasets
- Event Runtime And Energy
- Features
- Implications And Boundaries
- Interop Foldins
- Interpreter Spine
- Introspection
- Model Deployment
- Model Hub
- Notes
- Operational Maturity
- Production Workflows
- Project Layout
- Quickstart
- Requirements
- Sequence Primitives
- Streaming Timeseries
- Targets And Interop
- Usage
- Arch 0001 Adr Repo Topology
- Arch 0001 Core Boundary
- Arch 0001 Decision Metrics
- Arch 0001 Migration Plan
- Arch 0001 Packaging Versioning
- Arch 0001 Protocol Contract
- Arch 0001 Risk Register
- Arch 0001 Target Topology
- Backend Execution Plan
- Ecosystem Listings
- Ecosystem Roadmap
- Event Runtime Plan
- Hub Expansion Plan
- Plans
- Interop Foldins Plan
- Interpreter Spine Plan
- Memory System Research
- Model Hub Plan
- Operations Plan
- Production Toolkit Plan
- Production Use Cases
- Professional Roadmap
- Repo Topology Plan
- Sequence Primitives Plan
- Use Case Audio Keyword Spotting
- Use Case Biosignal Medical Monitoring
- Use Case Computational Neuroscience
- Use Case Edge Power Budgets
- Use Case Event Camera Vision
- Use Case Intrusion Anomaly Detection
- Use Case Low Latency Sensor Stream
- Use Case Rl Control Robotics
- Use Case Spiking Transformers
- Use Case Streaming Timeseries