- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
AdaFly targets fully onboard UAV vision-language navigation with a 545M-parameter policy. It selects between two and four historical frames and compresses them into 16 memory tokens using the current navigation context. The paper evaluates the method on AeroBrain with component ablations, and reports approximately 270 ms inference on a Jetson Orin NX and 40 real-world flight trials.
Critical strengths
1: Fully onboard navigation is a useful practical target. The reported deployment includes inference latency and memory usage, providing evidence that the compact policy can run within onboard computing limits. 2: The history-utility analysis and budget-matched random-selection baseline support the idea that when additional history is used matters. The compression ablation also shows benefits from conditioning memory on the current task.
Critical weaknesses
1: The contribution seems incremental, and the benefit of adaptive selection is modest. The method combines a turn/stop predictor for history selection with context-conditioned attention for compression. Both are fairly standard, and the new insight beyond their combination is unclear. Compared with fixed four-frame history, success increases from 43.22% to 44.94%, while latency drops from 297.24 ms to 268.44 ms. The practical importance of adding the selector needs stronger support.
2: The real-flight evaluation needs more detail and stronger comparisons. The supplementary video shows real drone operation, but the paper says little about the task difficulty, success criteria, interventions, and failures across the 40 trials. This makes the reported 30% success rate difficult to interpret. Without a fixed-history comparison, the benefit of adaptive memory in real flight also remains unclear. Missing training and execution details further limit reproducibility.
Questions for authors
1: What is new beyond combining history selection and compression? Both components use fairly standard designs. Please clarify what technical insight the method adds beyond existing approaches, and which experiments support that contribution.
2: What do the real-flight experiments establish? The supplementary video shows real drone operation, but the evaluation remains briefly described. How were the 40 tasks selected, what counted as success, and how were interventions handled? Please provide the task breakdown and main failure cases to help interpret the approximately 30% success rate. As additional validation, a fixed-history flight comparison would help show the method’s practical benefit.
3: How important is adaptive selection in practice? Compared with fixed four-frame history, success increases from 43.22% to 44.94%, while latency drops from 297.24 ms to 268.44 ms. What practical advantage do these gains provide that justifies the additional selector? Also, why does fixed H4 with conditioned compression achieve 45.03% in Table 4(b), compared with 43.22% in Table 4(a)? Please explain any differences in training or evaluation.
4: Can the missing implementation details be provided? Please specify the training data and splits, training objectives and settings, turn/stop label definitions, selection thresholds, and history sampling intervals. The real-flight action-chunk execution and handling of human intervention also need clarification. These details are needed to reproduce the results and assess whether the comparisons use consistent settings.