Harden DualVLN navigation recovery - #366
Draft
lighthqg wants to merge 6 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The original evaluator averaged multimodal S1 candidates, continued stale actions after collisions, and could repeatedly retry unproductive directions. Camera-only depth capture also needed an explicit restore path.
Impact
The seed-42 regression preserved all nine previously successful holdout episodes and added one metric success. Recovery remains lightweight, while suspected rendering and high-level semantic failures stay visible in diagnostics.
Validation
python -m pytest tests/unit_test/test_minimal_s1_safety.py tests/unit_test/test_navigation_state.py -q— 29 passed locally and on the cloud evaluation host