- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes Uni-Fly360, an end-to-end framework for UAV omnidirectional obstacle avoidance using panoramic images. It uses optical flow as intermediate representation to reduce sim-to-real gap. A differentiable spherical motion reasoning module disentangles ego-motion from object motion. Perception and policy are jointly optimized in a differentiable simulator. Evaluated on 3 tasks in sim and tested on real videos.
Critical strengths
-
Joint Optimization via Differentiable Simulation: Unifying the perception (optical flow) and control modules in an end-to-end differentiable pipeline is a strong contribution. The ablation study (Table 2) convincingly demonstrates that joint optimization significantly improves performance compared to frozen perception, validating the core motivation of the paper.
-
Spherical Motion Reasoning (SMR): The geometric design of the SMR module is elegant. By leveraging antipodal constraints to cancel rotation and estimating the global translation axis, it provides physically meaningful features to the policy without requiring heavy neural networks. The ablation confirms its effectiveness when combined with joint training.
Critical weaknesses
-
Lack of Real-World Flight Validation: The paper claims strong "sim-to-real transfer," but only evaluates the model by feeding pre-recorded real-world videos and visualizing the output acceleration vectors (Fig. 4). Without deploying the policy on a physical UAV, it is impossible to verify if the predicted commands actually result in safe closed-loop obstacle avoidance in reality. This significantly weakens the practical claim of the paper.
-
Degraded Performance After Collisions: As shown in Table 1, while Uni-Fly360 achieves higher Success Rates (SR), its Collision Time (CT) is notably worse than the baseline Fly360 in Hovering Maintenance (1.86s vs 1.19s) and Fixed-Trajectory Filming (2.8s vs 0.27s). The authors acknowledge that optical flow becomes unstable after collisions. For a safety-critical task like obstacle avoidance, prolonged collision duration is a significant drawback that needs better justification or mitigation.
Questions for authors
-
Are there any plans or fundamental blockers to deploying Uni-Fly360 on a real physical drone for closed-loop flight tests? If computational cost is the issue, what is the current inference FPS of the entire pipeline?
-
The SMR module relies on the assumption that the background is predominantly static to estimate ego-translation. How robust is the system in environments heavily populated with dynamic/moving obstacles?
-
Regarding the high Collision Time (CT) in Tasks 1 and 3 compared to Fly360: could the auxiliary loss weights be tuned to recover faster from collisions, or is this an inherent limitation of using optical flow instead of depth?
2 comments
Response to Authors
Thank you for the comprehensive rebuttal. The additional real-world flight experiments (10/10 and 8/10 success rates) and failure scenario analysis adequately address my concerns regarding closed-loop validation and collision recovery. The clarifications on the CT metric and dynamic obstacle performance are satisfactory.
My rating remains unchanged: 3 (Weak Acceptance).
some explanation and additional experinments
Response to Question1
Thanks. Since submitting the paper, we have conducted extensive real-world flight experiments to validate our method’s closed-loop control performance in real environments. The experimental results and UAV platform specifications are presented below.
Table. Hardware and deployment configuration of the real-world UAV platform.
We evaluated our system on two real-world tasks:
The success rates are reported in table below.
Response to Question2
Thank you for raising this concern. To assess robustness to moving obstacles, we re-evaluated the compared variants separately in static-obstacle and dynamic-obstacle scenarios. Table below reports success rate (SR) and collision time (CT) for both settings.
Response to Critical Question2:
Thank you for highlighting this issue. We agree that the higher CT in Tasks 1 and 3 is a limitation of our method. We adopted the CT protocol from Fly360, in which episodes continue after collisions. CT therefore measures cumulative contact duration and reflects post-collision recovery and trajectory stability.
After analyzing the results, we found that although CT is averaged over all episodes, its nonzero contributions come exclusively from episodes containing collisions. In Fixed-Trajectory Filming, both methods have only three such episodes out of 40, making CT sensitive to individual prolonged contacts. This limits the available observations for assessing recovery, while the longer contact duration remains a concern.
To further investigate this issue, we reproduced several observed failure scenarios and conducted extensive repeated evaluations in these settings. As shown in Table below, Uni-Fly360 achieves comparable CT (1.21 vs. 1.28 s) while maintaining a substantially higher success rate (63% vs. 38%).
Table. Comparison on reproduced failure scenarios.