- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes EventVista, an event-based action recognition framework that decouples the event retention budget from the computation budget of a single forward pass. Authentic Candidate Preservation retains a broader pool of original events, Coverage-Aware Runtime Observation constructs temporally complementary views under a bounded per-view budget, and Adaptive Evidence Integration aggregates predictions with confidence- and stability-based early stopping. Experiments on THU-EACT-50-CHL, DVSGesture, and DailyDVS-200 report Top-1 accuracies of 70.40%, 99.35%, and 50.68%, respectively. The paper includes component ablations, comparisons of observation strategies, and analyses of computational budgets and adaptive inference.
Critical strengths
1.The paper identifies a meaningful limitation of conventional fixed-size event-point processing, where coupling evidence retention with the per-pass computation budget may discard useful motion information prematurely. The proposed retain–observe–stop framework provides a coherent approach to preserving and selectively processing complementary event evidence while accommodating variable-length recordings.
2.The empirical evaluation covers three benchmarks with different event characteristics and reports strong recognition performance. Component ablations, budget sensitivity analyses, comparisons of fixed-view and adaptive inference, and results from three independent runs provide substantial evidence for the potential effectiveness of the framework.
Critical weaknesses
1.Unclear stopping protocols in the single-criterion ablations. Section 3.3 specifies a minimum of two views for the proposed joint stopping rule. However, Table 4 reports mean view counts below two for the confidence-only and stability-only variants on DVSGesture, whose candidate pools all exceed the per-view budget according to Appendix Table 7. These controls may use different stopping rules, but their minimum-view requirements and initialization are not clearly specified. In particular, the stability-only result requires clarification because the stated stability measure compares consecutive predictions. This ambiguity limits the reproducibility and interpretation of the stopping-rule ablations.
2.Incomplete end-to-end efficiency evaluation. Although EventVista maintains a bounded per-pass input budget and reports network GFLOPs, multiple views are generally processed per recording, and the computation estimates exclude candidate construction. The paper does not provide a complete comparison of preprocessing time, end-to-end inference latency, and peak memory consumption under matched resource budgets. Consequently, the practical efficiency advantages of the proposed framework remain insufficiently established.
Questions for authors
1.Section 3.3 defines the proposed joint stopping rule after at least two views, while Appendix Table 7 shows that all DVSGesture test recordings have 48K candidates, exceeding the 24K per-view budget. Why do the confidence-only and stability-only variants in Table 4 report average view counts of 1.86 and 1.72? Were these variants allowed to stop after one view, and if so, how was the stability criterion defined for the first view?
2.Table 2 reports noticeable accuracy differences between packed batching and per-recording execution. Were these variants evaluated using the same trained checkpoint and identical input views, or were they trained separately? Could the authors clarify which implementation or training differences account for these results?
3.Could the authors provide end-to-end inference latency, candidate-construction time, and peak memory consumption, together with comparisons against representative baselines under matched computational budgets?
4 comments
Response to Reviewer h7hJ Part (2/2)
W2 & Q3: End-to-End Efficiency and Resource Consumption
Thank you for requesting a full-pipeline evaluation. Joint reduces end-to-end latency with essentially unchanged peak GPU memory and achieves higher accuracy in budget-matched comparisons.
1. End-to-end latency
Measurements use an RTX 3090, FP32, batch size 1, one CPU thread, TF32 disabled, and 20 warm-up iterations. Cached includes view construction, network inference, and prediction integration from prebuilt candidate pools; Raw E2E additionally includes candidate construction from raw events. Both use the same profiling recordings. Latencies are per-recording means in ms.
| Dataset | Scope | Fixed-5 (ms) | Joint (ms) | Reduction |
|---|---|---|---|---|
| THU | Cached | 557.16 | 515.75 | 7.43% |
| THU | Raw E2E | 3,522.48 | 3,446.25 | 2.16% |
| DVSGesture | Cached | 861.21 | 459.84 | 46.61% |
| DVSGesture | Raw E2E | 1,010.07 | 605.34 | 40.07% |
| DailyDVS-200 | Cached | 873.74 | 819.86 | 6.17% |
| DailyDVS-200 | Raw E2E | 1,149.62 | 1,090.36 | 5.15% |
Joint reduces Raw E2E latency by 2.16%, 40.07%, and 5.15% on THU, DVSGesture, and DailyDVS-200, respectively. THU's smaller end-to-end gain reflects its dominant candidate-construction cost.
2. Preprocessing overhead and peak memory
Raw−Cached is the difference between mean Raw E2E and Cached latencies, estimating additional preprocessing overhead rather than independently timing candidate construction. View construction is already included in Cached. Candidate construction occurs once before observation; its timing variation is not attributed to early stopping. CPU memory is process peak RSS; times are ms and memory is MiB.
| Dataset | Method | Raw−Cached | View construction | Peak GPU | Peak CPU RSS |
|---|---|---|---|---|---|
| THU | Fixed-5 | 2,965.32 | 8.97 | 173.73 | 1,052.66 |
| THU | Joint | 2,930.50 | 8.25 | 173.74 | 1,111.44 |
| DVSGesture | Fixed-5 | 148.86 | 16.11 | 173.70 | 903.79 |
| DVSGesture | Joint | 145.50 | 10.25 | 173.70 | 962.38 |
| DailyDVS-200 | Fixed-5 | 275.88 | 15.33 | 173.88 | 5,175.98 |
| DailyDVS-200 | Joint | 270.50 | 13.84 | 173.89 | 5,237.61 |
Peak GPU memory remains approximately 174 MiB, differing by at most 0.01 MiB. Joint increases peak CPU RSS by approximately 59–62 MiB while reducing view construction time and inference latency.
3. Budget-matched controls
Coverage Static MV and Joint share the encoder, candidate pool, and single-view cap. Static inference uses predetermined integer view-count allocations, independent of test labels and runtime predictions, to match Joint's average encoder calls over the full test set. Short recordings are processed once and included in the mean. Strong Wider increases encoder channel width with a 24K input cap; Strong More Points raises the input cap to 48K.
Each cell reports test Top-1 accuracy (%) / network GFLOPs per recording, excluding candidate construction. Under this estimation convention, both stronger single-view alternatives differ from Joint by at most approximately 1.1%.
| Dataset | Coverage Static MV | Strong Wider | Strong More Points | EventVista Joint |
|---|---|---|---|---|
| THU | 68.93 / 10.18 | 68.75 / 10.08 | 69.12 / 10.24 | 70.40 / 10.18 |
| DVSGesture | 98.21 / 14.37 | 98.38 / 14.23 | 98.59 / 14.42 | 99.35 / 14.37 |
| DailyDVS-200 | 49.66 / 20.88 | 49.50 / 20.65 | 49.99 / 20.94 | 50.68 / 20.88 |
Joint improves over Coverage Static MV by 1.47, 1.14, and 1.02 percentage points, respectively, and outperforms both stronger single-view alternatives. These results support allocating limited computation to complementary evidence according to each recording's prediction state.
Once again, we sincerely thank you for recognizing the research value and potential of our paper and for your important contributions to improving experimental rigor and system-level efficiency evaluation! We have revised the paper according to your suggestions. If the above protocol clarifications and end-to-end efficiency evidence have fully addressed your concerns, we respectfully ask you to consider further raising your score to support acceptance of this paper; your recognition and a higher score would be tremendous encouragement and support for our team!
Sincere Thanks and Gentle Follow-up on Our Response
Dear Reviewer h7hJ,
We hope everything is going smoothly with your research. We sincerely appreciate your positive assessment of our framework and your constructive questions about stopping initialization, packed training, and practical efficiency. Your suggestions helped us clarify the execution protocol and strengthen the evaluation with measured end-to-end latency and resource-consumption results.
With the discussion period closing soon on November 18 (AoE), we wanted to gently follow up on our point-by-point response above. If you have a moment, we would be grateful to hear whether the protocol clarifications and additional efficiency measurements address your questions. We remain available to provide any further clarification that would be helpful.
If our responses and additional evidence have addressed your main concerns, we would be very grateful if you could consider raising your score. Your recognition and support would mean a great deal to our team and provide tremendous encouragement for our continued research.
Thank you again for your thoughtful guidance and encouragement. Wishing you continued success in your research!
Warm regards,
The Authors
Warm Thank You and Quick Summary of New Experiments & Clarifications
Dear Reviewer h7hJ,
Thank you again for your positive assessment of our framework and your constructive suggestions. Your questions helped us make the execution protocol clearer and strengthen the practical efficiency evaluation. To make our detailed response easier to review, we summarize the three main points below:
-
Stopping Initialization and Minimum Observations: For candidate pools exceeding the per-view budget, the official Joint policy evaluates at least two views before checking its confidence and stability conditions; shorter pools are processed once in full. The single-criterion ablations explicitly allow first-view exits, with Stability-only using a confidence gate at initialization. This explains their DVSGesture averages below two calls without computing stability from a single prediction.
-
Packed Training and Variable-Length Inputs: The packed and per-recording settings are trained separately and use their own validation-selected checkpoints. Per-recording training updates after each recording, whereas packed training averages the losses of eight recordings before updating; the comparison therefore reflects different effective batch sizes and optimization schedules. Cumulative offsets preserve recording boundaries throughout feature extraction and pooling, enabling batch learning without padding or event duplication.
-
Measured End-to-End Efficiency and Resource Costs: Relative to Fixed-5, actual runtime stopping reduces raw end-to-end latency by 2.16%, 40.07%, and 5.15% on THU-EACT-50-CHL, DVSGesture, and DailyDVS-200, respectively. These measurements include raw-event preprocessing, view generation, inference, and prediction integration. Peak GPU memory remains approximately 174 MiB, while peak CPU RSS increases by approximately 59–62 MiB; the additional budget-matched comparisons also favor Joint over static multi-view and stronger single-view alternatives.
We are grateful for your encouragement and for the suggestions that helped us improve the clarity and practical evaluation of EventVista. If you have a moment, we would sincerely value your thoughts on whether these clarifications and measurements address your questions. If they have addressed your main concerns, we would be very grateful if you could consider raising your score. Your support would mean a great deal to our team and encourage our continued research.
Thank you again for your time and thoughtful guidance, and wishing you continued success!
Warm regards,
The Authors
Response to Reviewer h7hJ Part (1/2)
We sincerely thank you for your careful review and positive evaluation of our paper, and for fully recognizing its focus on the problem of prematurely discarding discriminative information in fixed-point-count processing, its coherent Retain–Observe–Stop decoupled framework, and its solid empirical performance across three benchmark datasets! Your suggestions on the stopping protocol, batch training, and practical efficiency have helped us further clarify the method's operating conditions and empirical basis. We respond point by point below.
W1 & Q1: Initialization of the stopping policy and minimum number of observations
Thank you for carefully checking the stopping protocol. Both single-criterion ablations in Table 4 allow an exit after the first view; the official Joint policy checks for stopping only after at least two observations for recordings whose candidate counts exceed the single-view budget. The first-view branch of the original Stability-only policy uses a confidence gate and does not compute stability from a single prediction.
Let m(k) denote the difference between the two highest predicted probabilities after aggregating the first k views. The stability condition is:
\left\lVert p^{(k)}-p^{(k-1)}\right\rVert_1\le0.10,\qquad \arg\max p^{(k)}=\arg\max p^{(k-1)}.$$ To clarify the initialization and stopping rules of each strategy, we separately list below the exit conditions for the first view and from the second view onward. | Strategy | First-view exit condition | Exit condition from the second view onward | DVSGesture average number of observations | | --------------------------- | ------------------------------------ | -------------------------------------------- | ----------------------------------------: | | Confidence-only | $m^{(1)}\ge0.70$ | $m^{(k)}\ge0.70$ | 1.86 | | Stability-only | $m^{(1)}\ge\tau_{\mathrm{first}}$ | $S^{(k)}$ is satisfied | 1.72 | | Joint (paper configuration) | Not allowed | $m^{(k)}\ge0.70$ and $S^{(k)}$ is satisfied | 2.12 | All strategies continue up to $K_{\max}=5$ if their respective conditions are not satisfied. All DVSGesture candidate pools contain 48K events, exceeding the 24K per-view budget, so the means below two here **indeed arise from the ablation strategies allowing an exit after the first view and are unrelated to the exception for processing short recordings in full once**. Joint retains at least two observations because **high confidence after the first view does not guarantee that the prediction is already reliable**: a single bounded view may miss discriminative events, and subsequent complementary views still have the opportunity to supplement evidence and correct predictions. Therefore, the formal method first obtains subsequent evidence and then jointly assesses confidence and stability. We have added the above initialization and stopping conditions to the revised manuscript to make their correspondence with the official Joint configuration in Section 3.3 clear. ## Q2: Packed Batching vs. Per-recording Execution Thank you for focusing on the specific settings of this control. **The two settings in Table 2 are trained separately and use their own selected checkpoints. The purpose of this control is to examine how batch training can learn more effectively from variable-length event data while preserving the true event cardinality of each recording.** Specifically, Per-recording training computes the loss and updates parameters after processing each recording; Packed training directly packs the variable-length inputs of 8 recordings, averages the batch loss, and then performs a single update. The two therefore have different effective batch sizes, parameter-update frequencies, and optimization trajectories. Packed training uses cumulative offsets to maintain each recording's boundaries during feature extraction and pooling, allowing event recordings of different lengths to participate jointly in batch training while keeping recordings isolated, without adding points or duplicating events to equalize input lengths. These results support our use of Packed training: **it combines genuinely variable-length event inputs with batch learning and achieves consistent recognition benefits on all three datasets under the current training settings.** This implementation allows EventVista's preservation of event cardinality to extend throughout data processing and model training, without forcing all recordings to have the same number of points to form batches.