- The provenance of some values in Figures 3 and 4 needs to be verified
The embedded figure files for the left panel of Figure 3 and both panels of Figure 4 contain annotation text outside the cropped region. This text is not visible on the rendered page, but it is present in the PDF text layer and can be located by searching the PDF for "illustrative" (one occurrence on p. 7 and two on p. 8; it can also be extracted with tools such as pdftotext):
Figure 3 (left): "SIS-Motion: supplied result. Other models: illustrative estimates. Y-axis truncated (85–96)."
Figure 4 (both panels): "EnvSelf-UAV-4B. Filled: reported at K = 16." (H = 6 in the right panel) and "Open markers: illustrative estimates."
These notes are consistent with the visible marker styles: in Figure 4, only K = 16 and H = 6 use filled markers, while the remaining 16 data points use open markers. Read literally, all bars in Figure 3 other than SIS-Motion (including EnvSelf-UAV's 94.5) are labeled as estimates.
I cannot conclude from this alone that these values were not obtained from actual runs; the notes may be leftovers from an early draft. However, if the notes reflect what actually happened, then the OpenUAV-QA results for GPT-5.4 and Gemini-3-Flash, as well as all points in Figure 4 other than K = 16 and H = 6, are not measured values, and the trend analysis in §4.4 (e.g., the slight decline at K = 64 and the peak at H = 6) and the choice of K and H rest precisely on these points. This would no longer be a presentation issue; it would directly affect the reliability of the corresponding conclusions. I ask the authors to state whether each value in both figures comes from an actual run and to provide the corresponding evaluation logs. If any placeholder or estimated values are present, please replace them with measured results and revise §4.4 and the conclusions drawn from Figure 3 accordingly.
- The training configurations and memory-integration pathways of the ablation variants are not specified
Appendix B.3 describes the two-stage scheme (AerialVG image pretraining followed by SIS-Motion-54K video adaptation), but it does not state, row by row, whether the variants in Table 3 share the same pretraining data, initialization, and training budget. Section 4.3 explicitly mentions SIS-Motion-54K for the SFT baseline but does not say whether it also received the same AerialVG pretraining. If SFT did not receive image pretraining while the subsequent variants did, the improvement from 66.9% to 71.6% would conflate the contributions of additional data and architectural changes. My concern is that the protocol is under-specified; this alone does not establish that the comparison is unfair.
Similarly, the authors explain the conceptual difference between image-only training and temporal adaptation, but the concrete experimental setup remains unclear, for example whether the memory parameters continue to be updated during the video stage, whether the memory is re-initialized at every frame, and whether cross-frame updates are disabled. Moreover, the +DESM and +EMDM rows in Table 3 do not yet include QGMI, and the paper does not explain how the environmental memory, motion representation, and predicted representation are fed into the decoder in these variants. This directly affects how the per-row increments should be interpreted, particularly the 0.3-point gain attributed to QGMI.
Table 3 reports only 4 of the 13 SIS-Bench subtasks. Among those reported, adding DESM lowers path planning from 35.2 (SFT) to 29.6 and 30.4, below both SFT and the backbone (36.3), so the "consistent aggregate improvements" claimed in the text hold only at the level of the overall score. I suggest reporting the full per-subtask ablation in the appendix.
- The specific value of the core coupling design needs more targeted empirical support
The methodological contribution lies mainly in the coupling among regional memory, geometric motion representation, and future prediction. The individual building blocks have clear precedents; for example, MOTR[1] propagates and updates object queries frame by frame, and Flamingo[2] injects visual information into a language model through gated cross-attention. A more convincing argument would therefore show what additional benefit the coupling mechanism designed for UAV tasks provides.
The progressive ablations support the downstream utility of each component, but they do not yet distinguish among the following explanations:
Whether EMDM's gains come mainly from the geometric-consistency branch. The authors provide a reasonable robust matching and fallback mechanism, but they do not report the number of valid matches, the success rate of the affine fit, or the fallback rate, and there is no comparison with a variant that always uses the global-feature fallback. As a result, how often the geometric branch is actually used, and its independent contribution, remain unclear.
Whether the LWM's gains come specifically from future prediction and motion conditioning. The authors define the prediction target and provide an ablation with and without the LWM, but they report no prediction error and no comparison with copying the current environment state, removing motion conditioning, or a capacity-matched feature transformation. It is therefore difficult to separate the contributions of predictive ability, additional representational capacity, and the auxiliary training objective. Table 3 also omits Action Prediction, the subtask most directly related to prediction.
These requests do not require EMDM to output metric 6-DoF poses, nor do they require the LWM to perform candidate action planning. What would be more valuable is to add controls, under the existing representation-learning objectives, that directly test the roles of geometric consistency and motion conditioning.
[1]. Zeng F, Dong B, Zhang Y, et al. Motr: End-to-end multiple-object tracking with transformer[C]//European conference on computer vision. Cham: Springer Nature Switzerland, 2022: 659-675.
[2]. Alayrac J B, Donahue J, Luc P, et al. Flamingo: a visual language model for few-shot learning[J]. Advances in neural information processing systems, 2022, 35: 23716-23736.
- Camera transformation falls below the backbone at both scales, without a specific diagnosis
In Table 2, the Camera Transformation scores are 6.9 for the 4B backbone vs. 2.6 for EnvSelf-UAV-4B, and 6.2 for the 9B backbone vs. 1.8 for EnvSelf-UAV-9B. The authors acknowledge the limited fine-grained geometric reasoning ability, which is appreciated. However, the full system falls below its own backbone at both scales, while the text only states that "camera transformation remains weak" without noting this degradation; moreover, the camera-transformation example chosen for Figure 7 is a relatively favorable case.
The current results only show that the full training recipe degrades performance on this task; they do not allow the degradation to be attributed to EMDM. Because SFT and per-module results for this task are missing, it is impossible to tell whether this reflects a capability trade-off introduced by task adaptation, the effect of a particular component, or evaluation factors such as output format. Given the paper's emphasis on spatial and motion understanding, such a diagnosis would help clarify the method's benefits and limits.
- The relationship between hyperparameter selection and the zero-shot evaluation needs clarification
Section 4.4 states that K = 16 "provides performance close to the peak on both benchmarks" and selects H = 6 after noting that "Both curves peak at H = 6," which indicates that the SpatialUAV curves were used in parameter selection. The manuscript does not state whether these curves were computed on a held-out validation set or on the final evaluation instances.
This in itself is not evidence of data leakage, nor does it invalidate the authors' definition of zero-shot. However, since cross-task transfer is a key claim of the paper, the authors should state when K and H were fixed and on which data split, so that readers can judge whether the final evaluation was affected by model selection on the target test set. If the authors provide measured curves in response to Weakness 1, I also recommend performing the parameter selection on validation data that excludes SpatialUAV test instances.
- The statistical stability of small component gains is not reported
Appendix B.3 discloses the random seed (42) and the main training configuration, but Table 3 provides no run-to-run variation, confidence intervals, or paired uncertainty estimates. For example, QGMI's increment on SIS-Bench is from 76.6% to 76.9%. With 4,856 questions and an accuracy of about 77%, the binomial standard error of a single accuracy estimate is roughly 0.6 points, so a 0.3-point increment is well below this magnitude.
This does not mean the gain is insignificant, nor does it imply that the authors ran their experiments only once. More complete reporting could include results from repeated training runs or an uncertainty analysis based on paired predictions. Since multiple questions in SIS-Bench share the same video, resampling at the video level would better match the data structure.
- Some implementation and evaluation details need to be supplied
For the different input types in SpatialUAV, the paper defines the memory construction for single images and states that the benchmark's original input formats are retained, but it does not specify how EMDM, the LWM, and each memory source are enabled for single-image and independent multi-view inputs. Video training samples 4–16 frames at 2 fps, whereas evaluation is only described as using 8–32 frames, so the sampling interval at evaluation and the actual temporal meaning of the prediction horizon H remain unclear. The evaluation sequences are also longer than those seen in training, so both the memory recurrence and the number of motion tokens (up to 31) involve length extrapolation.
The QGMI formulation includes source embeddings but specifies no temporal or prediction-step encoding. Since DESM's accumulated state and the LWM rollout are produced by ordered recursion, and the raw observations are fed directly into the decoder, this alone does not imply that the model lacks temporal information. However, the motion tokens are computed for each pair of adjacent frames and carry no time index of their own, while Action Sequence and Action Recall depend precisely on their order. Please clarify whether the module relies entirely on token content to represent time or uses an additional, unstated temporal encoding.
OpenUAV-QA is defined in the appendix as offline multiple-choice navigation QA, and the results should be evaluated within that scope; I do not ask the authors to add closed-loop navigation or real-robot experiments. However, Figure 3 does not state which model scale is used and lacks the corresponding backbone and SFT comparisons. A sample record left outside the cropped region of the right panel of Figure 3 shows that the example is TravelUAV_Train_13187 (split: unseen_map), with the correct option being "about 48 m, turn left about 36°, about 34 m," whereas the figure is annotated with 50 m, 40°, and 35 m, suggesting that the text in the figure is not the model's actual output. The authors should also explain how the mislabeled sample identified in Appendix C.2 is handled in the final evaluation.