pith. sign in

arxiv: 1510.08829 · v1 · pith:XW3NTKAKnew · submitted 2015-10-29 · 💻 cs.LG · cs.NE

Spiking Deep Networks with LIF Neurons

classification 💻 cs.LG cs.NE
keywords networksspikingdeepmodelsneuronsclassificationhardwareimage
0
0 comments X p. Extension
pith:XW3NTKAK Add to your LaTeX paper What is a Pith Number?
\usepackage{pith}
\pithnumber{XW3NTKAK}

Prints a linked pith:XW3NTKAK badge after your title and writes the identifier into PDF metadata. Compiles on arXiv with no extra files. Learn more

read the original abstract

We train spiking deep networks using leaky integrate-and-fire (LIF) neurons, and achieve state-of-the-art results for spiking networks on the CIFAR-10 and MNIST datasets. This demonstrates that biologically-plausible spiking LIF neurons can be integrated into deep networks can perform as well as other spiking models (e.g. integrate-and-fire). We achieved this result by softening the LIF response function, such that its derivative remains bounded, and by training the network with noise to provide robustness against the variability introduced by spikes. Our method is general and could be applied to other neuron types, including those used on modern neuromorphic hardware. Our work brings more biological realism into modern image classification models, with the hope that these models can inform how the brain performs this difficult task. It also provides new methods for training deep networks to run on neuromorphic hardware, with the aim of fast, power-efficient image classification for robotics applications.

This paper has not been read by Pith yet.

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Forward citations

Cited by 1 Pith paper

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score.

  1. Evaluating Container Orchestration for Neuromorphic Workloads in Virtual Edge Environments

    cs.DC 2026-05 unverdicted novelty 5.0

    SNN workloads deployed via K3d show up to 47.6 times higher latency and 49 times lower throughput when CPU is limited to 0.5 cores, with accuracy staying stable but tail latency issues from round-robin routing during scaling.