Repository navigation
Rename benchmark to XEbench and emphasize cross-embodiment scores - #2
Merged
ytong6 merged 1 commit intoOct 1, 2026
Merged
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.
Rename the benchmark to XEbench (Cross-Embodiment Benchmark) across the README, specification, citation metadata, Python distribution/package/command, and adapter documentation. The README leads with cross-embodiment σ, mean success, and embodiment coverage, using the evaluation page as the reference for the controlled-cohort rules.
Introduce
rc-xebench,xebench, andXEBENCH_LLM_*. Preserve the legacy command, module identities, environment fallback, MCAP topics, and submission schema identifiers so existing adapters and recorded runs continue to work. Document that the CLI scores individual runs and that cohort σ is computed separately; illustrative website values are not measured results.Validation: Ruff lint and formatting checks, local Markdown link checks, both CLI names, legacy/new adapter type identity, environment fallback and precedence, a renamed mock run, and rescoring MCAP trials produced by the pre-rename code all passed.