- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
Spec-Spike combines a spiking action drafter with cached and low-rank interfaces for speculative decoding under a frozen OpenVLA verifier. The framework recovers compressed projections using the original drafter’s prediction histories and expands candidate branches to explore the trade-off between proposal cost and task performance.
Critical strengths
-
The paper identifies dense interfaces as an important bottleneck in spiking drafters and evaluates optimizations beyond the spiking core.
-
The matched ANN/SNN evaluation covers multiple LIBERO suites and three training seeds with paired closed-loop comparisons.
-
The paper transparently reports training exposure, negative outcomes, adaptive development, and the distinction between analytical cost and measured latency.
Critical weaknesses
-
All evaluation initial states were used to generate drafter-training trajectories, so the decision-excluded masks do not establish generalization to training-unseen states and limit comparisons with externally trained systems.
-
Parameter matching does not isolate spiking dynamics from architecture, integer activations, or the SNN-only activity penalty; activation-quantized and compute-matched ANN controls are missing.
-
The cost model excludes memory traffic and neuron-state updates, while Table 6 shows neither lower GPU latency nor lower total modeled arithmetic cost than the matched ANN; an end-to-end energy benefit remains unverified.
-
Three training seeds do not establish task-success non-inferiority, and significant declines occur against the ANN on LIBERO-Goal and against verifier-only decoding on LIBERO-Long.
-
Although prior history-aligned distillation and low-rank methods are cited, the additional benefit of own-history recovery is not established through matched closed-loop comparisons with alternative recovery strategies, and its implementation requires more precise definitions.
Questions for authors
-
How does Spec-Spike perform when evaluation initial states are excluded from drafter training, calibration, recovery, and all development decisions?
-
Can you compare against activation-quantized and compute-matched ANN drafters, including a control with matched architecture and activity regularization, to isolate the contribution of spiking dynamics?
-
What are the measured end-to-end latency and energy when verifier execution, memory traffic, neuron-state updates, CPU–GPU communication where applicable, and lookup-table construction are included?
-
What additional independent-seed results and prespecified non-inferiority margin would support preserved task success, and how does this conclusion change across acceptance radii?
-
Can you compare recovery strategies in closed loop under matched training budgets and specify the I-LIF recurrence, initial hidden state, and SmoothL1 reduction required to reproduce the recovery procedure?