- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
This paper introduces SURE, a humanoid locomotion controller for unreliable terrain maps. SURE keeps a blind policy as the base and adds a visual residual when vision is used. The controller compares estimated foot support and collision events with the map to decide when to withdraw the visual residual and when to use it again. The experiments in paper reports improved robustness under map faults in simulation environments, it also shows deployment experiments on real robot.
Critical strengths
The described problem is practical, as the robot cannot always trust its terrain map. It also makes lot sense to treat withdrawing vision and restoring vision as two separate decisions. Getting foot contact again doesn't mean the map is correct. The blind base stays active, so withdrawing vision doesn't require switching to a separately trained policy. These points claimed are reasonable
Critical weaknesses
-
I see this as a useful but fairly incremental improvement in vision-blind fallback. The physical checks provide a concrete way to withdraw and restore visual corrections. My concern is whether this design brings enough additional value over existing fallback methods, beyond using a different rule to decide when vision should be trusted.
-
Vision-blind fallback is already explored in previous works, for example: VB-Com, which the paper already cited, in VB-Com, the decision uses predicted returns. SURE instead uses physical consistency. The question is what additional practical value does this physical-consistency criterion bring over return-based switching?
-
I am not sure how much of the gain over HS comes from the new design, since the training is also different. SURE trains the blind and visual parts together, while HS trains them separately.
-
Hardware side, the tests only show the proposed method. What happens if the robot keeps using vision in these same situations? Successful runs show that SURE can work, but don't really tell us how much the proposed design improves reliability on real robots
Questions for authors
Please see weakness, questions are mentioned in weakness above
4 comments
Response to Reviewer 8LcP (2/4)
W2. Practical value over return-based switching
Answer to W2: The practical gain is retaining visual assistance on difficult terrain when the map is correct. On the same frozen controller, SURE achieved 100% on high-step ascent (T2-up) and 99.40% on repeated gutters (T5). VB-Com-style return selection achieved 0% on both.
To compare the criteria directly, we tested both on identical terrains and faults. Each selects between the same blind base (B) and visually assisted mode (B+R), where R is the visual residual.
Return selection predicts locomotion performance from proprioceptive history. SURE instead checks the received map against map-independent estimates of support and collision at the corresponding feet.
The return heads use five-frame proprioceptive histories and additional clean and fault-matched rollouts covering G1–G4. Independent critics with training-only privileged inputs provide advantage-plus-value (GAE+V) targets averaged over 50 steps. On independent validation, the B/B+R heads explain most of the target variation (explained variance 0.83/0.85). Both criteria use the direct stream-loss alarm for G5.
Success rate (%). Parentheses give evaluation-seed SD in units of the mean's last digit. G1–G5 denote unmapped protrusions, false support, map delay, height drift, and stream loss.
| Configuration | Clean | G1 | G2 | G3 | G4 | G5 |
|---|---|---|---|---|---|---|
| SURE | 99.93 (2) | 100.00 (0) | 100.00 (0) | 95.60 (56) | 100.00 (0) | 100.00 (0) |
| Return selection | 77.66 (3) | 100.00 (0) | 100.00 (0) | 88.80 (61) | 100.00 (0) | 100.00 (0) |
Return selection handles several faults well. Its clean-terrain failures show that a criterion can reject misleading guidance yet also withdraw vision needed for traversal.
To test the rules without learned prediction error, we keep both rules and replace their scores with measured finite-horizon returns. Simulating both modes from cloned decision states with their map inputs is computationally expensive, so we use 10 episodes per scene. T2-up remains 0/10 and T5 1/10.
- Relative-return comparison. In T5, some withdrawals occur even after the current visual return exceeds the blind return. Earlier low visual scores remain in the averaging window, because the rule compares a smoothed visual score with the current blind score. Those different time references can cause withdrawal on a correct map.
- Blind-return decline. This rule requests blind control when the current blind score is at or below its recent mean minus a margin. In T2-up, the decline rule still requests blind control when the visual score exceeds the current blind score both before and after smoothing. A falling blind score on difficult terrain can indicate a greater need for vision, not a map error.
The recorded decisions explain why better prediction alone need not resolve these failures. SURE's consistency criterion withdraws the visual residual when the map contradicts physical evidence, not simply when locomotion becomes harder.
Response to Reviewer 8LcP (3/4)
W3. Separating action structure from training
Answer to W3: To separate action structure from training, we compared the residual design with jointly trained full-action heads. SURE retains its success-rate advantage on unmapped protrusions and map delay.
The comparison removes the separate-versus-joint training difference in the original hard-switching baseline. We matched the full-action heads to SURE in terrain and visual-availability curricula, model capacity, and consistency rules. The full-action heads share proprioceptive features and use an event head calibrated on their own clean rollouts.
The full-action heads replace the blind action with a full visual action (a = (1−β)a_B + βa_V). SURE instead adds a visual residual to the proprioceptive blind base (a = a_B + βa_R). Binary β enables or withdraws visual assistance.
Success rate in the joint-training structural comparison (%). Parentheses give evaluation-seed SD in units of the mean's last digit.
| Configuration | Clean | G1 | G2 | G3 | G4 | G5 |
|---|---|---|---|---|---|---|
| SURE | 99.92 (3) | 100.00 (0) | 100.00 (0) | 96.90 (40) | 100.00 (0) | 100.00 (0) |
| Full-action heads | 98.08 (33) | 0.00 (0) | 99.93 (12) | 79.23 (172) | 100.00 (0) | 99.90 (10) |
G1 denotes unmapped protrusions, G2 false support, G3 map delay, G4 height drift, and G5 stream loss.
Both designs perform well on G2/G4/G5. SURE's success advantage is clearest on G1/G3 despite matching joint training.
We use observations collected during each method's own visually assisted rollouts. At each observation, we evaluate both modes and compare their targets for the 12 controlled leg joints. The mean RMS gap is 0.07114 versus 0.12107 rad (41.2% smaller for SURE). The mean within-episode 95th percentile is 0.12761 versus 0.20967 rad (39.1% smaller). This is a between-mode difference, not a temporal action difference. A smaller gap means the leg-joint targets change less if vision is withdrawn at the evaluated state.
Motion metrics. and are torso-tilt and torso-angular-velocity CVaR95; is velocity-tracking error and is time-normalized first-order action-difference RMS.
| Condition | Configuration | (rad) | (m/s) | (s⁻¹) | (rad/s) |
|---|---|---|---|---|---|
| Clean | SURE | 0.073 (<1) | 0.088 (<1) | 14.947 (<1) | 1.766 (<1) |
| Clean | Full-action heads | 0.096 (<1) | 0.092 (<1) | 16.858 (4) | 1.899 (1) |
| G1–G5 | SURE | 0.080 (<1) | 0.088 (<1) | 16.892 (3) | 2.133 (1) |
| G1–G5 | Full-action heads | 0.084 (<1) | 0.114 (<1) | 22.923 (20) | 2.329 (3) |
Scene means include valid motion up to termination, including from failed episodes, and are equally weighted within each group. (<1) denotes a nonzero SD that rounds to zero.
In clean rollouts, SURE reduces first-order action-difference RMS by 11.3% and torso-tilt CVaR95 by 23.2%, with lower tracking error. Under faults, first-order action-difference RMS is 26.3% lower and tracking error falls from 0.114 to 0.088 m/s. The same-observation comparison shows why sharing a blind reference can reduce the action change at withdrawal. The rollout results show that the advantage extends to motion during traversal.
Response to Reviewer 8LcP (4/4)
W4. Always-visual control in the hardware stair task
Answer to W4: We reproduced the hardware stair task in an idealized, repeatable simulation to avoid further hardware damage. An earlier always-visual trial had resulted in an ankle-joint malfunction after a collision. With a delayed map, always-visual control rarely finished the route. The robot often retreated and advanced again, with frequent leg collisions.
The three configurations share one controller, with a persistent 500 ms map delay and a 0.5 m/s command. Success means reaching the endpoint within 20 s. Leg-collision rate is the share of episodes with leg–terrain collisions; those collisions do not end the episode.
| Method | Success rate (%) | Leg-collision rate (%) |
|---|---|---|
| SURE | 100.000 ± 0.000 | 4.07 |
| Always blind | 100.000 ± 0.000 | 1.40 |
| Always visual | 2.167 ± 0.551 | 99.80 |
SURE and always-blind control completed every route, showing the blind base can traverse the stairs. Withdrawing misleading visual correction preserved route completion and reduced leg collisions relative to always-visual control.
Response to Reviewer 8LcP (1/4)
Thank you for asking what SURE adds beyond existing fallback methods and how the selection criterion and action structure each affect performance.
W1. Contribution beyond existing fallback
Answer to W1: We would like to clarify that SURE's main contribution is to use cross-modal verification to decide whether to apply a map-driven correction to the blind action. It compares the geometry given by the elevation map with proprioceptive estimates of support and collision at the same foot locations. The event estimator does not read the map, so it provides a separate source of evidence.
VB-Com selects between complete blind and visual actions using predicted returns. A low blind return can reflect a difficult step even when the map is correct. Miki et al. combine proprioception and exteroception in a learned belief. SURE instead keeps the two sources separate so that it can check the mapped geometry against estimated foot interactions.
Both SURE and VB-Com can revert to blind control. In SURE, even with vision enabled, the visual branch takes the blind action as input and learns a correction to it. At a given observation, withdrawing vision removes that correction without changing the underlying blind action.
The design therefore changes both the evidence used to withdraw visual guidance and how vision contributes to the action while it is enabled.