- Rating
- 2(+1)
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper investigates spiking activity constraints and target representation learning for resource-constrained UAV visual tracking, and proposes the fully spiking SBMVTrack. The training stage comprises EWSB and MVTM: the former constrains the spike firing rate and saturated activity according to the computational cost of each layer, while the latter treats the initial template, online template, and search region as temporal views and learns through masked reconstruction and cross-view identity consistency. During inference, only the original tracking branch is retained. On four UAV tracking benchmarks, the authors report an average precision/success rate of 86.5%/67.4% and a theoretical energy consumption of 4.4 mJ. On VisDrone2018, the corresponding figures are 90.0%/70.0%; compared with SpikeTrack, the success rate is 9.7 percentage points higher and the theoretical energy consumption is 45.7% lower.
Critical strengths
-
EWSB incorporates the computational costs of different layers into the spiking budget, while MVTM improves the stability of target representations under occlusion and appearance changes. Ablation studies show that combining the two achieves the best tracking performance and theoretical energy consumption.
-
The paper covers four UAV tracking benchmarks and compares multiple types of tracking methods, while reporting precision, success rate, theoretical energy consumption, and inference speed. It also conducts experiments on modules, loss functions, occlusion strategies, pooling methods, hyperparameters, and cross-model generalization.
Critical weaknesses
- Equation (12) appears to introduce non-spike-driven division operations during inference. This would make inference on neuromorphic chips impossible, rendering the energy-consumption calculation meaningless. Moreover, since , , and are calculated separately for each layer, hardwiring them onto the chip for shift operations is also unrealistic. If a customized chip were designed specifically for this purpose, it would greatly limit the practical value of this work.
- It is not stated whether fine-tuning is performed based on pretrained weights.
- Training uses RGB single-object tracking datasets. Does this affect the fairness of the evaluation? Do the datasets listed in Table 1 provide only test sets without training sets? Are their training strategies all the same as that used in this work?
- How was the parameter configuration of EWSB determined? The parameters currently discussed are relatively limited. Even if some of them were selected empirically, I believe this should be explained to some extent.
- The proposed SBMVTrack does not seem to perform as well as ORTrack, and it is also slower. As shown in Table 7, this weakens the significance of this work to some extent.
- The description of the energy-consumption calculation method is missing. Since many different methods for calculating energy consumption currently exist, clarifying this point is very important for fair comparison. I believe this must be included in the main text.
- The authors do not provide the code or other raw data. Although this is not necessary, I am quite certain that these materials would be crucial for me to verify the spike-driven characteristics of this paper; nevertheless, this should not be considered a mandatory requirement. More importantly, if possible, I hope the authors can provide the energy-consumption calculation scripts and the raw data for the spike firing rates.
- According to my brief investigation, many SNN-based single-object tracking algorithms have already been proposed and released as open source. I believe this paper should evaluate them fairly, such as the following representative works that I collected: SpikeFET [1] and SDTrack [2]. The authors seem to have deliberately avoided discussing these two prior works.
- There is no low-power/high-speed inference validation on neuromorphic chips.
- The ablation study of EWSB has not sufficiently demonstrated that energy weighting is superior to simple constraints.
- There is no fair comparison with STATrack [3], which is a highly related work. According to my observations, some metrics reported in that work are higher than those in this paper. [1] Yang J, Fan L, Zhang J, et al. Fully spiking neural networks for unified frame-event object tracking[J]. Advances in Neural Information Processing Systems, 2026, 38: 121132–121163. [2] Shan Y, Ren Z, Wu H, et al. SDTrack: A baseline for event-based tracking via spiking neural networks[C]//Proceedings of the IEEE/CVF Conference on Computer Vision and Pattern Recognition. 2026: 36245–36254. [3] Zhong P, Mo J, Zeng D, et al. Fully Spiking Neural Networks with Target Awareness for Energy-Efficient UAV Tracking[J]. arXiv preprint arXiv:2603.27493, 2026.
Questions for authors
See Weakness. If the authors can resolve my concerns or correct my misunderstandings, I will revise my score.
4 comments
Q1.Equation (12) is used only during training to compute the EWSB regularization loss. The divisions by and by the sum of layer costs normalize training statistics. Once training is complete, the tracker predicts bounding boxes without evaluating Eq. (12). Thus, deploying the tracker does not require implementing these divisions, hardwiring layer dimensions, or designing a custom chip for EWSB. We will mark Eq. (12) explicitly as a training-only computation.
Q2.We initialized the 10M E-SpikeFormer backbone from the V3_10.0M_1x4 pretrained checkpoint and fine-tuned it for tracking. The initial learning rates were for the backbone and for the prediction head. We will add the checkpoint source and initialization details to Sec. 4.1.
Q3.As described in Sec. 4.1, we trained SBMVTrack on LaSOT, GOT-10k, COCO, and TrackingNet and used the four UAV benchmarks only for evaluation. Following standard tracking practice, we evaluated the competing trackers using their officially released weights. Many of these trackers, including ORTrack, SpikeTrack, and SGLATrack, use the same main training datasets. For each benchmark in Table 1, we evaluated the trackers on the same sequences using the same precision and success metrics.
Q4.Table 6 evaluates from 0.08 to 0.16. We use 0.12 as a common operating point across datasets. For example, 0.08 gives higher success on UAV123 (68.8% versus 67.9%) and lower estimated energy, whereas 0.12 gives higher success on UAVDT (64.1% versus 61.9%). Table 8 reports the sensitivity to the budget and saturation loss weights. The remaining settings have an operational interpretation: with , normalized activations take values in , so places the saturation threshold between the two highest levels. Appendix A.3.1 discusses how the budget and saturation loss weights affect tracking accuracy, spike activity, and estimated energy (Table 8).
Q5.ORTrack is faster on the tested CPU and GPU. On VisDrone2018, SBMVTrack achieves a higher tracking success rate (70.0% vs. 66.8%) while running at 118.8 FPS on a conventional GPU. The lightweight SBMVTrack-S also exceeds 30 FPS on the tested CPU (33.3 FPS). Hardware supporting event-driven execution could further reduce SBMVTrack’s inference latency by skipping accumulations when no input spike is emitted.
Q6.We agree that the energy-accounting protocol belongs in the main text. Appendix A.1.2 currently gives the arithmetic-energy assumptions, including 4.6 pJ per MAC and 0.9 pJ per AC under the adopted 45-nm model. We will expand Sec. 4.1 to specify the operators included, how spike activity is measured and aggregated, and how each attention multiplication is counted.
Q7.Appendix Table 12 reports layer-wise firing rates averaged over the evaluation data. To make the energy estimate reproducible, we will provide the evaluation script together with the corresponding per-sequence firing-rate statistics, model configuration, and checkpoint identifier. These materials will make it possible to trace the aggregate estimate back to individual operators.
Q8.Thank you for highlighting these methods. SpikeFET is directly relevant, and our submission already evaluates EWSB on SpikeFET-Tiny using synchronized frame–event inputs on FE108 (Table 11). In that transfer experiment, estimated energy decreases from 18.4 to 14.2 mJ, while AUC changes from 67.9% to 67.6%. We will make this result more visible. SDTrack is also relevant as an event-based SNN tracker. The RGB UAV benchmarks in Table 1 do not supply its native event input, so a direct ranking there would confound tracker performance with input modality. We will discuss both methods explicitly and label the modality and purpose of each comparison.
Q9.We agree that end-to-end latency and energy per frame remain unmeasured on a physical neuromorphic chip. We validated the spiking neuron and recurrent attention computation on Lava’s CPU backend using Loihi fixed-point semantics. In a separate full-network simulation, we compared the outputs of 116 active spiking layers against the reference implementation over 117 tracking frames from three UAVDT sequences. Across all 13,572 comparisons, the maximum observed absolute difference was below 0.0001. Table 7 reports measured CPU and GPU throughput, while the reported energy values are estimates based on operation counts and spike activity.
Q10.Table 4 compares a uniform firing-rate budget with a layer-cost-weighted budget on UAV123. Using the weighted budget alone improves precision from 85.5% to 86.5% and success from 66.9% to 67.4%, while estimated energy increases from 4.8 to 5.1 mJ. Adding the saturation penalty yields the best observed trade-off: 87.1% precision and 67.9% success at 4.4 mJ. Appendix Table 8 further examines sensitivity to the budget and saturation loss coefficients.We will clarify that the joint accuracy and energy improvement is demonstrated for the full EWSB objective.
Q11.At the time of submission, we prioritized peer-reviewed publications when selecting baselines for Table 1. We cited STATrack in Related Work but omitted it from the table because it was then available as an arXiv preprint. We agree that its RGB-only UAV tracking setting makes it a directly relevant baseline, and we will add its author-reported precision and success rates to Table 1. SBMVTrack achieves higher success rates on UAVTrack112 (70.1% vs. 69.7%), VisDrone2018 (70.0% vs. 69.4%), and UAV123 (68.0% vs. 67.6%). STATrack achieves a higher success rate on UAVDT (65.3% vs. 64.8%) and slightly higher precision on UAVTrack112 (83.0% vs. 82.8%). The reported theoretical energy estimates are 4.4 mJ for SBMVTrack and 5.6 mJ for STATrack, corresponding to a 21.4% lower estimate for SBMVTrack.
The authors’ responses have resolved several of my concerns. Regarding my first question, I acknowledge that it was indeed a misunderstanding on my part. However, the authors seem to have misunderstood my point about energy estimation. What I meant is that, even when energy consumption is estimated for 45 nm neuromorphic chips, different calculation methods can be used, such as explicitly counting all MAC and AC operations in the network or calculating FLOPs and applying appropriate weights. To my knowledge, some papers also use other methods. A more detailed description would help readers understand the estimation procedure and make fair comparisons.
In their response to Question 5, the authors state that “hardware supporting event-driven execution can further reduce SBMVTrack’s inference latency by skipping accumulation operations when no input spikes are present.” In my view, although this can certainly reduce the number of computations, achieving an actual speedup requires the proposed network to be deployable on neuromorphic chips that support spike-driven inference. The research community still has reservations about this feasibility. Under these circumstances, assuming that the method can accelerate inference is not justified. To my knowledge, Loihi does not support spike-driven inference either.
I acknowledge that the paper I recommended, “Fully Spiking Neural Networks with Target Awareness for Energy-Efficient UAV Tracking,” is indeed still a preprint. Under these circumstances, omitting a comparison with it is acceptable. Nevertheless, given the various remaining issues in this work, I can only raise my score to 2. I hope the authors will implement all the revisions they have promised, as I consider several of the issues I raised to concern fundamental standards of academic rigor. Thank you for your understanding.
Dear authors, the AC has reminded us reviewers to respond to your rebuttal. If there is anything you would like to clarify or discuss, please leave a comment here, and I will respond as soon as possible.