- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes a two-stage framework to address payload-induced sensor blind spots and changes in geometric constraints during quadruped navigation. In the first stage, a LOADNav policy is trained through reinforcement learning to adapt its trajectory and orientation to the payload geometry. In the second stage, a proprioception-based geometry predictor estimates the dimensions of an unknown payload. A recurrent memory mechanism is further introduced to mitigate the loss of contact information caused by a finite observation window, enabling payload-size estimation without prior geometric knowledge.
Critical strengths
- The problem is practical and distinct from ordinary obstacle avoidance. Standard navigation treats the robot as a rigid body of fixed size, whereas the obstacle-avoiding body is the robot together with its payload.
- The experiments are reasonably thorough, with easy-to-interpret scenarios covering payloads of different geometries and validation on a real robot.
- The observation that payload geometry is observable only through contact is insightful. The added model addresses a concrete observability limitation rather than increasing complexity arbitrarily.
Critical weaknesses
- The way ACT is computed introduces a clear selection bias. Because ACT is averaged only over successful trials, a method with a higher success rate may retain more trajectories that succeed after collisions and consequently report a higher ACT. Therefore, ACT should not be interpreted as a standalone safety metric.
- The analysis relies on several idealized assumptions, including that the payload is rigidly attached and that its dynamic effects during contact-free motion are negligible. These assumptions may limit the method’s applicability to more realistic transportation tasks.
Questions for authors
- Could the authors report the number of collisions over all attempted trajectories, the success rate among trials with no payload contact, and the fraction of trials that become stuck and fail after a collision? Does CoGE-LOADNav+ actually make more contacts and simply recover from them more easily than CoGE-LOADNav?
- Before the first informative contact event, how does the system handle uncertainty about the unknown payload dimensions? Does the policy adopt a more conservative route, or can underestimating the payload size cause it to select a passage that is not actually traversable?