Repository navigation
Document proposed sim-to-real VLA evaluation workflow - #38
Merged
Merged
Conversation
niksacdev
marked this pull request as ready for review
September 24, 2026 10:13
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
1 participant
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.
Simulation success alone does not establish hardware task reliability. This note proposes a failure-driven evaluation workflow: capture hardware episodes, isolate policy versus execution causes, reproduce measured deployment variations, and validate changes against held-out hardware outcomes.
Includes a workflow diagram and an explicit boundary between current ROVE capabilities and the proposed hardware extension. No physical-robot performance is claimed.
Validation: checked scope against README and the action/episode and ABC integration documentation. Documentation-only change; no runtime tests run.