- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
PerProp retains BP's training structure but measures neuron sensitivity using paired perturbations and learns feedback connections from random input–response correlations. It targets physical networks where derivatives and copied feedback weights are difficult to obtain. The authors evaluate Transformers, Mamba, non-differentiable and spiking units, and implement on-chip learning on BrainScaleS-2. Crossbar energy results are projections.
Critical strengths
Three-seed GPT/Mamba evaluations show better in-domain and out-of-domain performance than the evaluated alternatives without access to transposed forward weights, with Mamba loss close to BP. Results across several spiking units support applicability. Actual on-chip updates and improvement over R-STDP under matched BrainScaleS-2 conditions provide evidence beyond simulation.
Critical weaknesses
1.Insufficient comparison with closely related feedback-learning methods. The paper discusses Akrout et al. (2019) but does not evaluate it, leaving the additional benefit unclear. A direct comparison on one representative architecture is needed, with matched training data and tuning budgets, reporting predictive performance and runtime including feedback learning.
2.The contributions of the key modifications remain unclear. BP, Hybrid, and PerProp provide overall controls, but do not isolate the benefits of direct linear probing and coordinate-wise normalization. Controlled ablations should report validation loss and feedback alignment under matched probe and update budgets.
3.The faster-scaling claims are affected by jointly changing training resources. Larger batches process more tokens, while deeper models receive more updates and different learning rates; each configuration uses only one seed. Comparisons at fixed total tokens for batch size and fixed compute for depth, with multiple seeds on representative configurations, are needed.
4.Evidence that a fixed probe budget supports wider networks is insufficient. Feedback estimation error grows with input dimension, and the width sweep shows a widening loss gap to BP. Varying probe count and feedback learning rate at two or three widths, while reporting feedback error, validation loss, and measured runtime, would clarify this limitation.
Questions for authors
Please see the weaknesses above.
5 comments
Response to reviewer TLPF (cont.)
W2. "The contributions of the key modifications remain unclear. BP, Hybrid, and PerProp provide overall controls, but do not isolate the benefits of direct linear probing and coordinate-wise normalization. Controlled ablations should report validation loss and feedback alignment under matched probe and update budgets."
Response. We welcome this request. We ran one-change ablations, with the same probes and the same update budget in every arm, first on language models and then on a spiking network.
Language models (setting of W1; m = 96, ρ = 0.1, one feedback update per step):
- Normalisation removed: no change in loss or alignment (GPT 5.578 vs 5.579, alignment 0.914 vs 0.913; Mamba-2 4.549 vs 4.546, 0.940 vs 0.939). Our variance analysis predicts this for isotropic Gaussian probes.
- Direct linear probing replaced by reading after the nonlinearity (the weight-mirror readout): +0.11 nats on GPT and +0.19 on Mamba-2, at alignment 0.910 / 0.924. Direct linear probing carries the result on these architectures.
Spiking network (SHD, recurrent adaptive LIF, 256 units per layer, 60 epochs; 3 seeds at 1–2 layers, 6 at 4 layers), where probe-driven spike differences cannot be isotropic:
| Arm | Test %, L = 1 | L = 2 | L = 4 (runs that train) | L = 4 feedback error ‖B − Wᵀ‖/‖Wᵀ‖ |
|---|---|---|---|---|
| PerProp | 86.1 ± 0.7 | 85.3 ± 0.5 | 62.3 ± 21.1 (4/6) | 0.092 |
| one scalar denominator | 85.6 ± 0.9 | 85.1 ± 1.9 | 44.4 ± 24.3 (1/6) | 0.401 |
| read after nonlinearity | 86.3 ± 0.3 | 86.0 ± 0.9 | — | — |
Normalisation matters here. Without the per-coordinate denominator, feedback error rises 3.6–4.4×, and at 4 layers test accuracy drops by 17.9 points, paired, with PerProp higher on 5 of 6 seeds. Reading after the nonlinearity matches PerProp at 1 and 2 layers on SHD (86.3 vs 86.1, 86.0 vs 85.3) but costs 1.45–1.48× the multiply-accumulates, and on language models it loses 0.11–0.19 nats.
Both components are necessary. Direct linear probing carries the result on language models. Per-coordinate normalisation is inert when probe responses are isotropic, as our variance analysis predicts and the language-model ablation confirms, because it then reduces to a scalar denominator. It becomes essential when responses are not isotropic, as on the spiking network above, and physical devices with mismatched gains produce anisotropic responses in the same way. Each component costs nothing where it is not needed and is required where it is.
W3. "The faster-scaling claims are affected by jointly changing training resources. Larger batches process more tokens, while deeper models receive more updates and different learning rates; each configuration uses only one seed. Comparisons at fixed total tokens for batch size and fixed compute for depth, with multiple seeds on representative configurations, are needed."
Response. We take this concern seriously. Our protocol follows standard practice for single-axis scaling studies. Energy-Based Transformers (Gladstone et al., ICLR 2026), which compare the scaling rates of two training methods along data, batch size, depth and parameters, run the batch-size experiments "for 105k steps", so larger batches also see more tokens. Letting data grow with the scaled resource is also the basis of compute-optimal scaling (Kaplan et al., 2020; Hoffmann et al., 2022). Most importantly, every comparison in our study is paired: at each point PerProp and backprop use the same configuration, data order and token count. Any resource change along an axis applies equally to both, and the quantity we report is their relative scaling.
We also address the concern directly.
- (a) A refit of the published curves with one shared floor and exponent shows PerProp behaving like backprop at a constant resource multiplier (k = 1.99 in tokens, 2.58 in model size), so the gap narrows with scale.
- (b) With each method at its own tuned settings, PerProp reaches backprop's loss with 1.23×, 1.25× and 1.22× the FLOPs at 20.8M, 49.6M and 162.9M parameters, a constant overhead of about 1.2× rather than a growing one (general response, Second). Backprop's seed SD at these settings is 0.002–0.004 nats; across both methods it is 0.002–0.009 nats, 4–20× smaller than the tuned gaps.
Response to reviewer TLPF (cont.)
W4. "Evidence that a fixed probe budget supports wider networks is insufficient. Feedback estimation error grows with input dimension, and the width sweep shows a widening loss gap to BP. Varying probe count and feedback learning rate at two or three widths, while reporting feedback error, validation loss, and measured runtime, would clarify this limitation."
Response. We agree that the published width sweep used a fixed m = 96, and this explains the widening gap. The feedback error follows a closed-form law in probe count m, input width d_in and rate ρ: ‖B − Wᵀ‖²/‖W‖² ≈ ρ/(2 − ρ)·(d_in − 1)/(m − 2). Measured over predicted is 1.000 (0.997–1.003) on all 20 published runs. So m must grow with width to hold the error fixed; the experiments below test exactly this.
Feedback error, 4 widths × 5 probe counts × 2 rates × 3 seeds: at fixed m/d the error is flat to 0.2% from d = 192 to 1536 (ρ = 0.2: 0.375 at m/d = 1, 0.265 at 2, 0.188 at 4). At fixed m = 96 it rises from 0.53 to 1.51. All 34 configurations match the law (0.993–1.002).
Validation loss. Published, m = 96: gap 0.31 / 0.38 / 0.42 / 0.51 nats at d = 192 / 384 / 768 / 1536. Trained with m = 1536 (m/d = 8 / 4 / 2) and tuned LRs: 0.037 / 0.042 / 0.036 nats at d = 192 / 384 / 768. At d = 384, varying m (16–384) and ρ (0.02–0.5) moves the loss as the law predicts (see fHyc W3 for the table).
Runtime. Feedback arithmetic is 2m/(3T) of a step: 0.20% at m = 96 and 3.1% at m = 1536; the tuned campaign measured 1.03× arithmetic per step. Measured full-step time on language models is in W1. Measured on one dedicated H200 (6 layers, sequence 1024), a PerProp step takes 1.33–1.43× backprop's step time from d = 192 to 1536. Feedback learning is 0.25–1.19% of the step at m = 96 and 1.1–3.7% with m = 4d, so the overhead comes from the slope-measurement path, not from feedback learning. On analog hardware the probe cost is energy: at m = 1536, feedback is 1.7–6.1% of PerProp's projected training energy at 0.1 pJ per product.
We thank the reviewer. Each of the four requests now has a direct experiment: KP and WM on two architectures with runtime (W1), one-change ablations on language and spiking models (W2), tuned scaling and the published protocol in context (W3), and probe count and rate against width with a law that predicts the error to within 1% (W4). We hope this resolves the concerns that led to the current score, and we would be grateful if the reviewer would consider raising it.
References
- Akrout, M., Wilson, C., Humphreys, P. C., Lillicrap, T., Tweed, D. Deep Learning without Weight Transport. NeurIPS 2019. arXiv:1904.05391.
- Gladstone, A., et al. Energy-Based Transformers are Scalable Learners and Thinkers. ICLR 2026. arXiv:2507.02092.
- Kaplan, J., McCandlish, S., Henighan, T., et al. Scaling Laws for Neural Language Models. arXiv:2001.08361, 2020.
- Hoffmann, J., Borgeaud, S., Mensch, A., et al. Training Compute-Optimal Large Language Models. NeurIPS 2022. arXiv:2203.15556.
- Yi, S.-i., Kendall, J. D., Williams, R. S., Kumar, S. Activity-difference training of deep neural networks using memristor crossbars. Nature Electronics 6, 45–51 (2023). doi:10.1038/s41928-022-00869-w.
Response to reviewer TLPF
We thank the reviewer for a precise review and for noting that "three-seed GPT/Mamba evaluations show better in-domain and out-of-domain performance than the evaluated alternatives without access to transposed forward weights", that results "across several spiking units support applicability", and that "actual on-chip updates and improvement over R-STDP under matched BrainScaleS-2 conditions provide evidence beyond simulation". We ran each requested comparison.
Several requests concern conventions specific to in-situ learning, so we state three briefly first.
W1. "Insufficient comparison with closely related feedback-learning methods. The paper discusses Akrout et al. (2019) but does not evaluate it, leaving the additional benefit unclear. A direct comparison on one representative architecture is needed, with matched training data and tuning budgets, reporting predictive performance and runtime including feedback learning."
Response. This request was very useful, and we ran it on two architectures rather than one. We now benchmark both of Akrout et al.'s rules, weight mirror (WM) and Kolen–Pollack (KP), on GPT-24L and Mamba-2-24L (WikiText-103, plus TinyStories out of distribution), 3 seeds, same data and same learning-rate pilot, at matched probe budget and at Akrout et al.'s own configuration. Validation NLL, and full step time including feedback learning (A6000-equivalent):
PerProp has the lowest loss among the rules without weight transport in every column, also out of distribution (TinyStories, GPT / Mamba-2: PerProp 7.177 / 6.653; full out-of-distribution columns in the general response, First). WM trails by 0.07–0.19 nats even with 21× the probes, which cost +6% / +34% step time. KP ties PerProp on GPT in distribution at Akrout et al.'s decay but trails by 0.35 nats on Mamba-2 and degrades out of distribution (+0.038 on GPT, +0.360 on Mamba-2). Both rules, as published, need analytic derivatives of the neuron nonlinearity, which physical and non-differentiable units do not provide; PerProp measures them with the same probing operation it uses for feedback. Step times are A6000-equivalent, calibrated through the BP/PerProp ratio rather than measured on a dedicated card.
For the spiking (SHD) benchmark in the paper, the Kolen–Pollack baseline uses weight decay 2e-3; we will state this setting in the revision.