Papers › Ternary Spike: Learning Ternary Spikes for Spiking Neural Networks

Ternary Spike: Learning Ternary Spikes for Spiking Neural Networks

11 Dec 2023arXiv:2312.06372archive 2025-07-28

Yufei Guo, Yuanpei Chen, Xiaode Liu, Weihang Peng, Yuhan Zhang, Xuhui Huang, Zhe Ma

The Spiking Neural Network (SNN), as one of the biologically inspired neural network infrastructures, has drawn increasing attention recently. It adopts binary spike activations to transmit information, thus the multiplications of activations and weights can be substituted by additions, which brings high energy efficiency. However, in the paper, we theoretically and experimentally prove that the binary spike activation map cannot carry enough information, thus causing information loss and resulting in accuracy decreasing. To handle the problem, we propose a ternary spike neuron to transmit information. The ternary spike neuron can also enjoy the event-driven and multiplication-free operation advantages of the binary spike neuron but will boost the information capacity. Furthermore, we also embed a trainable factor in the ternary spike neuron to learn the suitable spike amplitude, thus our SNN will adopt different spike amplitudes along layers, which can better suit the phenomenon that the membrane potential distributions are different along layers. To retain the efficiency of the vanilla ternary spike, the trainable ternary spike SNN will be converted to a standard one again via a re-parameterization technique in the inference. Extensive experiments with several popular network structures over static and dynamic datasets show that the ternary spike can consistently outperform state-of-the-art methods. Our code is open-sourced at https://github.com/yfguo91/Ternary-Spike.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 15 code samples harvested from 1 repository linked to this paper: 13 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 2 violated, 2 with no contract checked; 9 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 7 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 15 samples from 1 repository, 13 ran (4 with no instrument failure; 9 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 13 samples that ran has no recorded date.

yfguo91/ternary-spike officialmentioned in papermentioned on GitHubpytorchSyntology: 15 samples, 13 ran (9 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

15 samples harvested: 13 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 2 violated, 2 with no contract checked; 9 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · violated contract
7ran · our draft was wrong
2ran; the contract check could not run
2ran
2unverified

Licence: 15 of the 15 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from yfguo91/ternary-spike. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

yfguo91/ternary-spike official repository 15 samples, 13 ran (9 instrument-failed) · 2 unverified
MPR models/spike_layer.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 84864b7304ea2f94 · report fixture: signature s:Tensor/2/float, thresh:float/0/float · returned Tensor · level recorded 2026-09-22
accuracy in 872 papers
census: 8 implementations from 7 papers, 7 distinct outputs across 6 buckets, one shared input per bucket
utils.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant no licence file found · pointer only · 4134b8420b4c48b5 · report fixture: signature output:Tensor/2/float, target:Tensor/1/int, topk:tuple/1/int · returned list · level recorded 2026-09-22
conv3x3 in 1,376 papers models/resnet.py ran · our draft was wrong no licence file found · pointer only · dacc6812ec177540 · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int · returned Conv2d · level recorded 2026-09-24
gradient_scale models/spike_layer.py ran fingerprinted no licence file found · pointer only · 6899805d3c9c6510 · report fixture: signature x:Tensor/2/float, scale:float/0/float · returned Tensor · level recorded 2026-09-24
init_bias models/init.py ran · our draft was wrong no licence file found · pointer only · 506029b9782311de · report fixture: signature net:callable/0/? · returned SimpleNet · level recorded 2026-09-24
init_weights in 109 papers models/init.py ran · our draft was wrong no licence file found · pointer only · bc15a35a19eccd77 · report fixture: signature net:callable/0/? · returned SimpleNet · level recorded 2026-09-24
is_absorbing in 6 papers models/fold_bn.py ran · violated contract no licence file found · pointer only · bc1bf5bb29e60206 · report fixture: signature m:callable/0/? · returned bool · level recorded 2026-09-24
is_bn in 9 papers models/fold_bn.py ran · violated contract no licence file found · pointer only · 06ddc213753098ff · report fixture: signature m:callable/0/? · returned bool · level recorded 2026-09-24
make_layers in 155 papers models/vggcifar.py ran · our draft was wrong no licence file found · pointer only · d816051f5a32a403 · report fixture: signature cfg:list/1/int, batch_norm:bool/0/bool · returned Sequential · level recorded 2026-09-24
plot_overlap in 37 papers myutils/logger.py ran · our draft was wrong no licence file found · pointer only · 50afa2863ffd9fde · report fixture: signature logger:MockLogger/0/?, names:NoneType/0/? · returned list · level recorded, date not recorded
search_fold_and_remove_bn models/fold_bn.py ran · our draft was wrong no licence file found · pointer only · d7cc95c193f0291c · report fixture: signature model:callable/0/? · returned Conv2d · level recorded 2026-09-24
spike_activation models/spike_layer.py ran no licence file found · pointer only · dc807df34e66cf20 · report fixture: signature x:Tensor/2/float, binary:bool/0/bool, temp:float/0/float · returned Tensor · level recorded 2026-09-24
split_weights models/init.py ran · our draft was wrong no licence file found · pointer only · 314691fc56c14c2a · report fixture: signature net:callable/0/? · returned list · level recorded 2026-09-24
vgg11 in 50 papers models/vggcifar.py unverified no licence file found · pointer only · 9c695d51a5fdcc9e · report
vgg11_bn in 40 papers models/vggcifar.py unverified no licence file found · pointer only · ff89b5bc32b8bfd8 · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

SNN

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections