Downloads · 30 days
149
15% of all-time downloads
cy0307/ropedia-xperience-10m-task-baselines
ropedia-xperience-10m-task-baselines is a robotics model from cy0307. Use it for the robotics task on the model card, and read the license before you ship it in a product. It is set up for pytorch. The card lists the license as mit.
<p align="center" <img src="docs/assets/brand/xperience10m-logo-social-card.png" alt="Ropedia Xperience-10M Task Suite cover" width="100%" </p
Downloads · 30 days
149
15% of all-time downloads
All-time downloads
1K
Public
Repo size
1.3 GB
Likes
4
Public
Click a slice to open those files.
.npz644 MB · 37%
From the Hugging Face model README
This project builds on the Xperience-10M dataset released by Ropedia to provide public, reproducible embodied-AI evaluation materials. It is organized into two evidence lines. Line 1 turns one public sample episode into inspectable tasks, targets, and baseline runs. Line 2 uses selected 128-episode public-safe artifacts for aligned metadata/raw baselines, Qwen3-Omni v6 LoRA, Cosmos3-Super Reasoner, and Cosmos3-Nano Future Window. Every score links back to its source artifact, and direct scores remain clearly separated from compact-proxy estimates.
Updated: 2026-06-23.
Scope: Line 1 uses one public sample episode. Line 2 uses selected 128-episode public-safe artifacts linked back to official gated episode paths. Raw Xperience-10M MP4/HDF5/RRD files, Qwen3 base weights, Cosmos3 base weights, and gated data are not redistributed here.
Use this copyable BibTeX block for the repository:
@misc{he2026ropedia_xperience10m_task_suite,
author = {Chaoyue He},
title = {Ropedia Xperience-10M Task Suite},
year = {2026},
url = {https://github.com/ChaoYue0307/ropedia-xperience-10m-task-suite},
note = {Public task and evaluation layer for Ropedia Xperience-10M: two evidence lines, 20 embodied-AI tasks, 180 scored method-task records, and selected-128 model diagnostics}
}
Use the two evidence lines first, then choose the artifact that answers your question. The dashboard is the best visual overview; the GitHub repo is the source of truth for scripts and generated JSON; Hugging Face mirrors contain public-safe cards, metrics, figures, and model artifacts.
Quick rule: use Line 1 for “can I inspect and reproduce the task?” Use Line 2 for “how do aligned baselines and model diagnostics compare on the selected 128 episodes?”
The committed task contracts, result matrices, validation JSON, public-safe result packages, GitHub sources, and Hugging Face mirrors are the canonical technical evidence.
The project has four connected layers. The 20 tasks are the scored benchmark contracts. The 4 directions are research groupings over those same tasks. The 3 foundation pipelines are training recipes that reuse the same modalities, windows, and task targets. The 1 unified embodied model target is the long-term integration goal after those pipelines mature.
Layer rule: if it has a metric, it is a task; if it explains what the evidence studies, it is a direction; if it describes model inputs and training targets, it is a pipeline; if it combines perception, 3D memory, language, action, and planning, it is the unified target rather than an extra score axis.
<p align="center"> <img src="docs/assets/charts/task_direction_pipeline_relationship.png" alt="Relationship map showing 20 task contracts, 4 research directions, 3 foundation-model pipeline tracks, and 1 unified embodied model target" width="100%"> </p>| Layer | Count | Role | Exact public labels |
|---|---|---|---|
| Task contracts | 20 | Score axes used by the matrix, radars, task cards, and method rows. | Action Recognition; Procedure Step Recognition; Action Boundary Detection; Next-Action Prediction; Hand Trajectory Forecasting; Contact State Prediction; Object Relevance Prediction; Language Grounding; Cross-Modal Retrieval; Cross-Modal Reconstruction; Temporal Order Verification; Multimodal Synchronization Detection; Long-Horizon Next-Action Forecasting; Long-Horizon Next-Subtask Forecasting; Interaction Text Prediction; Action-Object Relation Prediction; Future Object-Set Forecasting; IMU-to-Hand Pose Reconstruction; Camera-View Synchronization Retrieval; Time-to-Next-Transition Regression. |
| Research directions | 4 | Ways to interpret what the 20 tasks study; not separate benchmark tiers. | Human Modeling & Motion Understanding; 3D/4D Reconstruction & Neural Rendering; Egocentric Vision & Interaction; Scene Reconstruction & World Modeling. |
| Foundation pipelines | 3 | Larger-model training tracks with separate input-output recipes and result gates. | Spatial intelligence models; Human-video world models; Vision-language-action models. |
| Unified embodied model target | 1 | Long-term integration target, not a task/method row in the 180-result matrix. | Perception; 3D memory; language-grounded reasoning; action; planning. |
The data explorer is now a three-scope analysis layer, not only a raw-file browser. It compares the public sample episode, selected 128-episode feature exports, and the Hugging Face-hosted gated full-dataset metadata without mixing their evidence boundaries.
| Scope | Question | Current public analysis |
|---|---|---|
| Public sample | What files and signals are directly inspectable? | 1 episode, 5,821 frames, 1,161 aligned 20-frame windows, 8,546 feature dimensions, raw-file browser, modality breakdowns, action-window distribution. |
| Selected 128 | What selected-episode surface supports model comparison? | 96/16/16 split, 34,269 Qwen3-Omni v6 multiscale rows, 106,095 dense compact rows, selected episode links, public-safe matrices. |
| Full HF dataset | How large is the official upstream dataset? | Authenticated Hub file metadata: 804 sessions, 12,103 episode-like folders, 85,257 files, 24.63 TiB training-byte view, without redistributing raw gated data. |
Entry points: website analysis section, analysis report, and structured analysis record.
The public suite is organized around two evidence lines. Keep them separate when comparing metrics.
<p align="center"> <img src="docs/assets/charts/two_evidence_line_map.svg" alt="Two evidence-line map: 1 sample episode and 128 selected episodes combine into 180 scored method-task records" width="100%"> </p> <table> <thead> <tr> <th width="20%">Line</th> <th width="24%">Data unit</th> <th width="22%">Score statement</th> <th width="20%">Best use</th> <th>Read separately from</th> </tr> </thead> <tbody> <tr> <td><strong>1 sample episode</strong></td> <td>One public Xperience-10M sample episode: 5,821 frames, 1,161 aligned 20-frame windows, 8,546 feature dimensions.</td> <td>40/40 direct scores from Minimal and Neural MLP heads.</td> <td>Inspect the raw sample, understand file organization, reproduce the 20 task targets, and compare Minimal vs Neural MLP behavior inside one episode.</td> <td>The selected-128 comparison rows and any broader held-out model behavior.</td> </tr> <tr> <td><strong>128 selected episodes</strong></td> <td>Selected held-out 96/16/16 split: 34,269 exported windows with public-safe processed features linked to official gated episode paths. The Hugging Face artifact dataset exposes these rows separately as <a href="https://huggingface.co/datasets/cy0307/ropedia-xperience-10m-task-suite-artifacts/viewer/selected_128_windows/selected_128"><code>selected_128_windows/selected_128</code></a>; it is not mixed with the one-sample <code>episode_sample/public_sample</code> viewer.</td> <td>140/140 selected-128 scores: 134 direct + 6 compact-proxy.</td> <td>Compare same-split metadata/raw baselines, Qwen3-Omni v6, Cosmos3-Super, and Cosmos3-Nano while keeping the 6 compact-proxy cells visible.</td> <td>Direct raw-target measurements for the proxy-marked cells.</td> </tr> </tbody> </table>Cosmos3-Super Forward-Dynamics LoRA is published as a separate fine-tuned adapter artifact with weights/results; it is not counted as a 20-task matrix method row.
These are Qwen3-Omni run versions inside Line 2: selected 128 episodes. They are not the project evidence lines. The 20-task matrix uses Qwen3-Omni v6 LoRA; v5 remains the pinned prior multiscale release; v1-v4 are lineage and ablation evidence.
<table> <thead> <tr> <th width="8%">Run</th> <th width="26%">Purpose</th> <th width="28%">Main change</th> <th width="16%">Eval signal</th> <th>Use now</th> </tr> </thead> <tbody> <tr><td><strong>v1</strong></td><td>Prove the selected-128 LoRA/eval/package loop.</td><td>First verified 96/16/16 selected-episode Qwen3-Omni LoRA run.</td><td>448 eval; JSON 0.8750; contact 0.6451.</td><td>Lineage only.</td></tr> <tr><td><strong>v2</strong></td><td>Make answers schema-checked.</td><td>Structured-JSON contract with full-8-GPU LoRA on the same split.</td><td>448 eval; JSON 0.9978; contact 0.7188.</td><td>Structured-output ablation.</td></tr> <tr><td><strong>v3</strong></td><td>Separate prompt/eval effects from training.</td><td>Strict-label prompt/eval over the v2 adapter; no new adapter training.</td><td>448 eval; JSON 1.0000; contact 0.7210.</td><td>Prompt/eval ablation.</td></tr> <tr><td><strong>v4</strong></td><td>Test longer structured-JSON LoRA training.</td><td>New four-epoch full-8-GPU adapter on the same selected split.</td><td>448 eval; JSON 1.0000; contact 0.7299.</td><td>Overfit/metric-tradeoff evidence.</td></tr> <tr><td><strong>v5</strong></td><td>Move to denser multiscale evaluation.</td><td>Multiscale cap96 export with 4,032 held-out predictions.</td><td>4,032 eval; JSON 1.0000; contact 0.7865.</td><td>Pinned prior release; stronger on several non-contact metrics.</td></tr> <tr><td><strong>v6</strong></td><td>Publish the current Qwen 20-task row.</td><td>Rank64/lr5e-5 multiscale LoRA plus verified task-specific probes.</td><td>4,032 eval; JSON 0.9990; contact 0.8177.</td><td>Current public 20-task Qwen3-Omni row.</td></tr> </tbody> </table>Detailed lineage:
QWEN3_OMNI_RUN_LINEAGE.md and
qwen3_omni_run_lineage.json.
Result entry points:
TWO_EVIDENCE_LINES.md,
two_evidence_lines.json,
TWO_EVIDENCE_LINE_RESULT_SUMMARY.md,
two_evidence_line_result_summary.json,
QWEN3_OMNI_RUN_LINEAGE.md,
qwen3_omni_run_lineage.json,
single_episode_task_model_radar.json,
episode128_task_model_radar.json,
task_method_20_result_matrix.json, and
xperience10m_128_episode_feature_index.json.
This project is organized as a compact research artifact around Xperience-10M: start from a real public episode, make every modality and label path inspectable, turn the data into concrete embodied-AI tasks, and keep the evaluation boundary clear while preparing the next multi-episode experiments. The emphasis is on research judgment as much as implementation: what the sample can show, where the selected-128 comparison begins, and what evidence should exist before presenting stronger model quality.
The work is designed to demonstrate four capabilities that matter for embodied-AI research infrastructure:
<table> <thead> <tr> <th width="26%">Capability</th> <th>What this project shows</th> </tr> </thead> <tbody> <tr><td><strong>Multimodal data understanding</strong></td><td>Parses the public sample into synchronized windows across video, audio, depth, pose/SLAM, mocap, IMU, calibration, and language-derived signals.</td></tr> <tr><td><strong>Task design</strong></td><td>Defines 20 human-readable tasks in one unified public-sample suite, plus four direction-extension probes with inputs, outputs, process modules, metrics, and case-study walkthroughs.</td></tr> <tr><td><strong>Model and evaluation discipline</strong></td><td>Runs minimal and compact neural baselines, records predictions/metrics, keeps chronological split boundaries explicit, and separates the sample readout from held-out comparison rows.</td></tr> <tr><td><strong>Scale-up planning</strong></td><td>Connects the public-sample pipeline to 32/128-episode held-out pilots, Qwen3-Omni LoRA, Cosmos-style world-model tracks, policy/VLA tracks, and the future Xperience-native foundation-model pretraining goal.</td></tr> </tbody> </table>The public release is split across GitHub, the website, and Hugging Face. Use the public evidence map first for the shortest route through those mirrors, or use the machine-readable companion evidence-map data. For the one-page project summary, use the project brief and project-summary data.
<table> <thead> <tr> <th width="32%">Goal</th> <th>Best entry point</th> </tr> </thead> <tbody> <tr><td><strong>Choose the right published mirror</strong></td><td><a href="PUBLIC_READER_MAP.md">Public evidence map</a><br><a href="docs/data/public_reader_map.json">evidence-map data</a></td></tr> <tr><td><strong>Resolve confusing terms and abbreviations</strong></td><td><a href="GLOSSARY.md">Glossary</a><br><a href="docs/data/glossary.json">glossary data</a></td></tr> <tr><td><strong>Understand the whole project quickly</strong></td><td><a href="PROJECT_BRIEF.md">Project brief</a></td></tr> <tr><td><strong>See the visual research dashboard</strong></td><td><a href="https://chaoyue0307.github.io/ropedia-xperience-10m-task-suite/">GitHub Pages dashboard</a></td></tr> <tr><td><strong>Navigate the unified 20 tasks, four tracks, and scale-up plan</strong></td><td><a href="https://chaoyue0307.github.io/ropedia-xperience-10m-task-suite/research_roadmap.html">Interactive research roadmap</a><br><a href="TASK_SUITE_20.md">20-task suite note</a><br><a href="docs/data/task_suite_20.json">task contract data</a><br><a href="docs/data/research_roadmap_interactive.json">interactive roadmap data</a></td></tr> <tr><td><strong>Compare current task metrics</strong></td><td><a href="RESEARCH_TAKEAWAYS.md">Research takeaways</a><br><a href="docs/data/summary_metrics.json">summary metrics</a></td></tr> <tr><td><strong>Compare possible foundation backbones</strong></td><td><a href="FOUNDATION_MODEL_PLAN.md">Foundation-model plan</a><br><a href="docs/data/foundation_model_plan.json">foundation-model data</a></td></tr> <tr><td><strong>Understand the future native pretraining goal</strong></td><td><a href="XPERIENCE_EMBODIED_FOUNDATION_MODEL_PRETRAINING.md">Native pretraining plan</a></td></tr> <tr><td><strong>See additional concrete project directions</strong></td><td><a href="ADDITIONAL_DEVELOPMENT_DIRECTIONS.md">Additional development directions</a><br><a href="docs/data/additional_development_directions.json">direction data</a></td></tr> <tr><td><strong>Understand one model input</strong></td><td><a href="results/episode_task_suite/feature_manifest.json">feature manifest</a><br><a href="results/episode_task_suite/windows.csv">window table</a></td></tr> <tr><td><strong>Check multi-episode data status</strong></td><td><a href="results/omni_finetune/DATA_ACCESS_STATUS.md">multi-episode data status</a></td></tr> </tbody> </table>Use the glossary when a term such as evidence line, 20-frame window, direct score, compact-proxy score, raw metric value, normalized radar value, minimal/minimum baseline, simple baseline, Qwen v1-v6, Cosmos3-Super, LoRA adapter, or HF artifact dataset is unclear. The same definitions are mirrored as glossary data for the website and Hugging Face repos.
Public release checks are exposed as structured records for mirrors and dashboards: website integrity, rendered-site check, task-surface integrity, publication audit, mirror parity, public-surface QA, and roadmap data.
For the fastest interpretation of the current metrics, start with the research takeaways and takeaway data. They summarize what the public sample results actually show: class shift under chronological splits, neural gains on dynamics/order/alignment, harder retrieval/reconstruction probes, and why the next model-quality step needs held-out episodes.
Current contributions:
This project is best read as a staged embodied-AI research study:
<table> <thead> <tr> <th width="17%">Layer</th> <th width="53%">Current scope</th> <th width="30%">Where to start</th> </tr> </thead> <tbody> <tr> <td><strong>Data understanding</strong></td> <td>One public Xperience-10M sample episode is converted into 5,821 frames, 1,161 aligned windows, and an 8,546-dimensional multimodal representation.</td> <td><a href="PROJECT_BRIEF.md">PROJECT_BRIEF.md</a><br><a href="PROJECT_STATUS.md">PROJECT_STATUS.md</a></td> </tr> <tr> <td><strong>Task suite</strong></td> <td> Twenty human-readable tasks cover recognition, prediction, retrieval, reconstruction, synchronization, long-horizon forecasting, interaction text, action-object binding, sensor bridging, camera sync, and transition timing. Historical <code>tier2_task_suite</code> artifact paths are kept for link stability, but they are provenance paths inside the same suite. </td> <td> <a href="TASK_SUITE_20.md">20-task suite note</a><br> <a href="docs/data/task_suite_20.json">task contract data</a><br> <a href="RESEARCH_TAKEAWAYS.md">research takeaways</a><br> <a href="results/episode_task_suite/summary_report.json">summary report</a><br> <a href="results/episode_task_suite/tier2_task_suite/TIER2_TASK_BASELINES.md">historical provenance baselines</a> </td> </tr> <tr> <td><strong>Baselines</strong></td> <td> Minimal heads and compact PyTorch MLP heads provide a controlled single-episode comparison on the same chronological split. The selected 128-episode setup adds same-split metadata simple/NN baselines for JSON-supported tasks and raw-feature simple/NN baselines on all 20 task axes. Tasks 15 and 19 are explicitly marked as compact-proxy completions. </td> <td> <a href="results/episode_task_suite/neural_mlp/">neural MLP outputs</a><br> <a href="results/omni_finetune/multi_episode_128_task_baselines/BASELINE_ALIGNMENT_REPORT.md">baseline alignment report</a><br> <a href="results/omni_finetune/a100_128_raw20_task_baselines_complete20_proxy_20260616T091500Z/run_summary_all.json">raw20 run summary</a> </td> </tr> <tr> <td><strong>Diagnostics</strong></td> <td>Audio contribution, modality ablations, timeline overlays, object labels, and alignment stress tests show which signals are useful and which tasks remain hard.</td> <td><a href="results/audio_ablation/AUDIO_ABLATION_SUMMARY.md">audio ablation summary</a><br><a href="docs/single_episode_explorer.html">single-episode explorer</a></td> </tr> <tr> <td><strong>Scale-up</strong></td> <td> <ul> <li>Qwen3-Omni LoRA v6 is verified on the selected 96/16/16 split with 34,269 exported windows and 4,032 held-out test predictions.</li> <li>v6 improves action macro-F1/contact accuracy versus v5; v5 remains a pinned prior-release row because it is stronger on several other metrics.</li> <li>Same-split simple/NN metadata baselines are published for JSON-supported axes, and the raw-feature run adds simple/NN baselines on 20/20 task axes.</li> <li>Tasks 15 and 19 are documented compact proxies because raw interaction strings and paired video-view embeddings are absent from the 128 export.</li> <li>Cosmos3-Nano has a verified future-window compatibility package; Cosmos3-Super has a 448-window base-weight JSON-task Reasoner evaluation.</li> <li>Cosmos3-Super also has a fine-tuned forward-dynamics LoRA package over camera-pose proxy targets with 2,848 train rows, 512 validation rows, and 448 test rows.</li> <li>The 128-episode enhancement pack records dense-window sizing, hierarchical action/subtask targets, task bottlenecks, and next experiment cards without overwriting existing results.</li> </ul> </td> <td> <a href="RESEARCH_ROADMAP.md">research roadmap</a><br> <a href="FOUNDATION_MODEL_PLAN.md">foundation-model plan</a><br> <a href="XPERIENCE10M_128_EPISODE_FEATURE_INDEX.md">selected-128 feature index note</a><br> <a href="docs/data/xperience10m_128_episode_feature_index.json">selected-128 feature-index data</a><br> <a href="TASK_SUITE_ENHANCEMENT_128.md">selected-128 enhancement note</a><br> <a href="docs/data/task_suite_enhancement_128.json">selected-128 enhancement data</a><br> <a href="docs/data/omni_model_comparison.json">model comparison data</a><br> <a href="docs/data/omni_finetune_verified_result.json">verified Omni result data</a><br> <a href="docs/data/qwen3_v5_v6_comparison.json">Qwen v5/v6 comparison data</a><br> <a href="results/omni_finetune/QWEN3_V5_V6_COMPARISON_20260614.md">Qwen v5/v6 comparison note</a><br> <a href="results/omni_finetune/OMNI_MODEL_COMPARISON.md">Omni model comparison note</a><br> <a href="results/omni_finetune/verified_public/">verified public package</a><br> <a href="results/omni_finetune/task_suite_enhancement_128_v1_20260608/">selected-128 enhancement run</a> </td> </tr> </tbody> </table>Detailed dataset notes, reproduction checks, and generated data reports are included for implementation inspection. The full file map is available in the artifact guide.
Source alignment is tracked in the source-alignment note
and source-alignment data.
Whenever this repo says "full dataset," it refers to the Hugging Face-hosted
gated dataset version at ropedia-ai/xperience-10m, not a local raw-data
mirror. The official gated ropedia-ai/xperience-10m card reports 31.9 TB
on the live Hugging Face dataset card and an about-1PB full-scale storage statement; the committed
API-listing snapshot records 12,103 episode folders as upstream metadata only,
not a local raw-data inventory. In other words, those episode folders are
upstream listing metadata only for this project. The public sample remains
ropedia-ai/xperience-10m-sample under cc-by-nc-4.0, with the HOMIE Toolkit
and Rerun 0.29.0 noted as source tooling. The official responsible-use note
that the data is limited in diversity is preserved.
If you only have one minute, use the project status note and project-status data. They give the current research state in one compact table:
<table> <thead> <tr> <th width="28%">Area</th> <th>Current decision</th> </tr> </thead> <tbody> <tr><td><strong>Public-sample pipeline</strong></td><td>Verified on one public sample episode: 5,821 frames, 1,161 windows, 8,546 dimensions.</td></tr> <tr><td><strong>20-task suite</strong></td><td>Verified minimal baselines with committed metrics, predictions, and manifests.</td></tr> <tr><td><strong>Neural heads</strong></td><td>Verified compact PyTorch MLP heads over the same task contracts and chronological splits.</td></tr> <tr><td><strong>Dataset context</strong></td><td>Official Xperience-10M links, sample-vs-gated-data boundary, modality coverage, and redistribution policy are documented.</td></tr> <tr><td><strong>Evaluation protocol</strong></td><td>Verified generated protocol for windowing, split policy, leakage controls, and per-task metrics.</td></tr> <tr><td><strong>Website and Hub pages</strong></td><td>Public dashboard, Hugging Face Space, artifact dataset, baseline model repo, and collection use the same project framing and links.</td></tr> <tr><td><strong>Qwen3-Omni multi-episode pilot</strong></td><td>Final verified diagnostic result package exists for the selected 96/16/16 episode split; JSON validity meets the target, while action/subtask metrics remain weak.</td></tr> <tr><td><strong>Raw data / full Qwen weights</strong></td><td>Raw Xperience-10M data and full Qwen weights are not redistributed.</td></tr> </tbody> </table>Recommended project sequence:
<table> <thead> <tr> <th width="6%">Step</th> <th width="24%">Question</th> <th width="34%">Primary artifacts</th> <th>What should be true</th> </tr> </thead> <tbody> <tr><td><strong>1</strong></td><td>What is this project?</td><td><a href="PROJECT_BRIEF.md">Project brief</a><br><a href="PROJECT_STATUS.md">Project status</a><br><a href="https://chaoyue0307.github.io/ropedia-xperience-10m-task-suite/">Dashboard</a></td><td>A public-sample Xperience-10M research project with 20 tasks, baselines, and a scale-up plan.</td></tr> <tr><td><strong>2</strong></td><td>What data is used?</td><td><a href="XPERIENCE10M_DATASET_CARD_ALIGNMENT.md">Dataset-card alignment</a><br><a href="https://huggingface.co/datasets/ropedia-ai/xperience-10m">Official HF dataset</a><br><a href="https://huggingface.co/datasets/ropedia-ai/xperience-10m-sample">Sample HF dataset</a></td><td>The implemented suite uses one public sample episode; the gated dataset is reserved for selected multi-episode training.</td></tr> <tr><td><strong>3</strong></td><td>What does one model input contain?</td><td><a href="results/episode_task_suite/windows.csv">window table</a><br><a href="results/episode_task_suite/feature_manifest.json">feature manifest</a><br><a href="results/episode_task_suite/available_modalities.json">available-modality data</a></td><td>Each window is an aligned multimodal unit with video, audio, depth, pose/SLAM, mocap, IMU, calibration, and language-derived signals.</td></tr> <tr><td><strong>4</strong></td><td>What are the 20 tasks?</td><td><a href="TASK_SUITE_20.md">20-task suite note</a><br><a href="docs/data/task_suite_20.json">task contract data</a><br><a href="results/episode_task_suite/task_walkthroughs/">task walkthroughs</a><br><a href="docs/data/task_walkthroughs.json">walkthrough data</a></td><td>Every task has a human-readable name, input, output, metric, baseline scores, and an explicit artifact path.</td></tr> <tr><td><strong>5</strong></td><td>How are tasks evaluated?</td><td><a href="EVALUATION_PROTOCOL.md">evaluation protocol note</a><br><a href="docs/data/evaluation_protocol.json">evaluation-protocol data</a></td><td>The window unit, chronological split, leakage controls, task metrics, and current limitations are explicit.</td></tr> <tr><td><strong>6</strong></td><td>What do current results mean?</td><td><a href="RESEARCH_TAKEAWAYS.md">research takeaways</a><br><a href="docs/data/research_takeaways.json">takeaway data</a><br><a href="docs/data/summary_metrics.json">summary metrics</a></td><td>Current metrics describe sample-level task behavior and identify which signals need larger held-out experiments.</td></tr> <tr><td><strong>7</strong></td><td>Which models are implemented?</td><td><a href="results/episode_task_suite/summary_report.json">summary report</a><br><a href="results/episode_task_suite/neural_mlp/">neural MLP outputs</a><br><a href="https://huggingface.co/cy0307/ropedia-xperience-10m-task-baselines">HF baseline repo</a></td><td>Each task has minimal and neural-head evidence over the same feature windows.</td></tr> <tr><td><strong>8</strong></td><td>What research directions does this support?</td><td><a href="RESEARCH_ROADMAP.md">research roadmap</a><br><a href="docs/data/research_directions.json">direction data</a><br><a href="docs/data/research_direction_extensions.json">extension-probe data</a><br><a href="docs/data/task_suite_20.json">task contract data</a></td><td>The unified tasks are mapped to human modeling, 3D/4D reconstruction, egocentric interaction, and world modeling.</td></tr> <tr><td><strong>9</strong></td><td>Which foundation model comes next?</td><td><a href="FOUNDATION_MODEL_PLAN.md">foundation-model plan</a><br><a href="docs/data/foundation_model_plan.json">foundation-model data</a><br><a href="XPERIENCE_EMBODIED_FOUNDATION_MODEL_PRETRAINING.md">Native pretraining plan</a></td><td>Qwen3-Omni is the first held-out LoRA baseline; Cosmos 3 has Nano compatibility and Super forward-dynamics LoRA; policy models wait for robot-compatible action targets.</td></tr> <tr><td><strong>10</strong></td><td>How can the 128-episode suite be pushed without more data?</td><td><a href="TASK_SUITE_ENHANCEMENT_128.md">selected-128 enhancement note</a><br><a href="docs/data/task_suite_enhancement_128.json">selected-128 enhancement data</a></td><td>The enhancement pack proposes dense windows, hierarchical action/subtask labels, raw-feature shard priorities, and <code>multiscale_20s10_40s20_80s40</code> as the next export target.</td></tr> <tr><td><strong>11</strong></td><td>How do I reproduce it?</td><td><a href="REPRODUCIBILITY.md">reproducibility guide</a><br><a href="notes/reproducibility_audit.md">reproduction audit</a></td><td>Public commands and expected outputs are documented for the sample-episode task suite.</td></tr> <tr><td><strong>12</strong></td><td>What is still pending?</td><td><a href="docs/data/omni_finetune_verified_result.json">verified Omni result data</a><br><a href="results/omni_finetune/DATA_ACCESS_STATUS.md">data access status</a><br><a href="results/omni_finetune/MULTI_EPISODE_ACCESS_STATUS.md">multi-episode access status</a></td><td>The final held-out diagnostic Qwen pass is verified and JSON-validity target is met; strong action/subtask model quality remains pending.</td></tr> </tbody> </table>A compact project-path summary is available at project-packet data.
The artifact guide maps the public evidence who want to inspect the project files after the first pass. It groups the main briefs, task outputs, baseline results, visual assets, data notes, and scale-up documents.
The artifact index is the compact machine-readable companion used by the website and Hugging Face artifact dataset.
The project resource map is the complete generated inventory for scripts, result artifacts, website data, visual assets, configs, notes, and prepared Hugging Face bundles. Its structured companion, docs/data/project_resource_map.json, is used by the website Resources tab to search, filter, and open scripts/results directly.
The evaluation protocol and evaluation-protocol data are generated from committed metric artifacts. They define:
The official ropedia-ai/xperience-10m
dataset is a gated large-scale egocentric multimodal dataset for embodied AI,
robotics, spatial intelligence, and world modeling. The public
ropedia-ai/xperience-10m-sample
repo provides the sample episode used for the implemented task suite here.
This project keeps two evidence lines separate. Line 1 uses the public sample for raw-file inspection, task construction, and local reproducibility. Line 2 uses selected 128-episode public-safe artifacts for same-split method comparison, Qwen3-Omni v6 diagnostics, and Cosmos3 diagnostics. Raw Xperience-10M MP4/HDF5/RRD files are not redistributed in this repo or in the Hugging Face mirrors.
The current verified public-sample subset is:
annotation.hdf5 carrying depth, SLAM/camera pose, hand/body mocap, IMU,
language/caption annotations, calibration, metadata, and timing records,Detailed dataset notes are available in the dataset-card alignment note and dataset-alignment data for full upstream-card and access-term context. Line 1 is the task lab; Line 2 is the selected-128 comparison layer; compact-proxy cells stay explicitly marked where direct raw targets are missing.
Start with the visual dashboard:
chaoyue0307.github.io/ropedia-xperience-10m-task-suite
Hugging Face Space app:
cy0307-ropedia-xperience-10m-task-suite.hf.space
If you use this project, cite the Ropedia Xperience-10M Task Suite by
Chaoyue He and also cite the upstream Ropedia Xperience-10M dataset according
to its official dataset card. The repository includes CITATION.cff,
codemeta.json, and docs/data/project_manifest.json
for machine-readable metadata.
Copy this BibTeX entry for the repository:
@misc{he2026ropedia_xperience10m_task_suite,
author = {Chaoyue He},
title = {Ropedia Xperience-10M Task Suite},
year = {2026},
url = {https://github.com/ChaoYue0307/ropedia-xperience-10m-task-suite},
note = {Public task and evaluation layer for Ropedia Xperience-10M: two evidence lines, 20 embodied-AI tasks, 180 scored method-task records, and selected-128 model diagnostics}
}
The code files are MIT-licensed. Raw Xperience-10M data is not redistributed
here, and dataset use remains governed by the official Ropedia/Xperience-10M
terms. See LICENSE and DATA_NOTICE.md.

The infographic uses a custom text-free research background and puts the shared
processing contract plus all 20 unified task families in one figure. Public
sample stream thumbnails remain available through the raw sample browser and
derived modality assets instead of a separate repeated atlas panel. The task
names, input/output summaries, and metrics are overlaid from
results/episode_task_suite/summary_report.json
with scripts/render_task_suite_infographic.py,
so the published PNG is a presentation graphic with verified labels and metrics,
not a hallucinated metric sheet.
The complete unified task list is documented in TASK_SUITE_20.md
and docs/data/task_suite_20.json. Historical
tier2_task_suite paths remain only as stable provenance links inside the same
suite.
The unified radar is now a grouped small-multiple comparison board instead of a
nine-method overlay. It keeps all 20 task axes and all 9 method rows visible,
but separates the methods into single-episode, 128-episode metadata/text,
128-episode raw-feature, and foundation-model panels. Every method has 20
explicit result records in the public matrix. Tasks 15 and 19 are marked as
compact-proxy completions where the 128 export lacks raw interaction strings or
paired video-view embeddings; those six proxy cells stay explicitly marked
instead of being blended into direct-target metrics. The SVG uses
sqrt(normalized_score) only for visual radius so small but real differences
are readable; raw metrics and exact linear normalized scores remain in JSON and
the table.
Cosmos3-Super forward-dynamics LoRA
remains a separate artifact card because its camera-pose proxy MSE is not one of
the 20 task metrics.
The machine-readable copies are
docs/data/unified_task_model_radar.json
and
docs/data/task_method_20_result_matrix.json;
the explicit score/proxy ledger is
docs/data/task_method_20_gap_audit.json
and TASK_METHOD_20_GAP_AUDIT.md;
the public matrix is
TASK_METHOD_20_RESULT_MATRIX.md.
The website Results section also renders the same 180 cells as a wide,
source-linked table with raw values, normalized radar values, metric keys, and
direct/proxy badges.
The same source data is also split into two focused radars:
The single-episode radar uses one enlarged panel for Minimal vs Neural MLP, both with 20/20 scored public-sample axes. The 128-episode radar uses three grouped panels for metadata/text baselines, raw-feature baselines, and foundation-model rows: metadata and raw-feature simple/NN baselines are now complete 20/20 multi-episode records, and Qwen3-Omni v6 LoRA, Cosmos3-Super Reasoner, and Cosmos3-Nano Future Window each carry 20 scored task records. The current matrix has 180/180 scored method-task records.
The website raw sample browser includes a concise stream-to-feature ledger
backed by docs/data/modality_atlas.json and
docs/assets/modalities/. Those assets are small
derived thumbnails from the public sample, not raw Xperience-10M files.



The pipeline and architecture figures use the same pattern: text-free visual
backgrounds carry the composition, while
scripts/render_overview_figures.py
overlays exact labels, dimensions, and metrics from the committed result files.
This is a learning, inspection, and pipeline-validation repo with two public evidence lines. Line 1 is built from one public sample episode. Line 2 uses a selected 96/16/16 split over 128 episode paths, public-safe processed features, and verified Qwen3-Omni/Cosmos3 diagnostic artifacts.
scripts/
train_min_action_model.py # motion/IMU baseline
train_all_modalities_model.py # current all-feature lightweight baseline
episode_task_suite.py # public-sample task definitions
neural_task_models.py # optional PyTorch MLP heads for task contracts
research_direction_taxonomy.py # maps walkthrough-backed tasks to the four research tracks
research_direction_extension_tasks.py # one extra data-backed probe per track
tier2_task_suite.py # historical-name provenance builder for unified task rows
build_unified_task_suite.py # builds TASK_SUITE_20.md and task_suite_20.json
build_unified_task_model_radar.py # builds grouped 20-axis model comparison radars
build_task_method_20_gap_audit.py # builds the explicit 180/180 scored-cell ledger
task_walkthroughs.py # human-readable task-card and walkthrough-storyboard metadata
generate_visualizations.py # refreshes SVG charts + summary JSON
render_task_suite_infographic.py # renders the task-suite presentation PNG
export_modality_atlas_assets.py # exports responsive modality-card assets
render_overview_figures.py # renders polished pipeline/architecture PNGs
build_brand_assets.py # derives logo sizes, favicon, social card
build_artifact_index.py # builds the compact artifact guide data
build_quality_gates.py # builds release checks
validate_mirror_parity.py # checks prepared GitHub/HF mirror file parity
validate_scope_claims.py # separates setup artifacts from completed model metrics
validate_task_surface.py # checks readable task cards and interactive storyboard wiring
validate_website_integrity.py # checks local site links, anchors, and images
validate_publication_package.py # checks public repo + HF bundle contents
publish_hf_bundles.py # uploads prepared HF Space/artifact/model bundles
omni/
download_sample_modelscope.py # ModelScope sample download helper
build_episode_manifest.py # metadata-only multi-episode scanner
plan_finetune_sample_budget.py # storage/sample-count planner
qwen3_omni_adapter_smoke.py # real-data Qwen3-Omni adapter setup check
score_existing_model_output_task_probes.py # scores task targets already present in verified model outputs
collect_qwen3_v4_release_artifacts.py # pulls verified v4 results after remote eval
results/
min_action_model/ # motion-only action baseline artifacts
min_subtask_model/ # motion-only subtask baseline artifacts
min_all_modalities_action_model/ # current all-feature action artifacts
min_all_modalities_subtask_model/ # current all-feature subtask artifacts
episode_task_suite/ # task-suite metrics and predictions
neural_mlp/ # optional neural baseline artifacts per task
research_directions/ # four-track taxonomy, CSV, and summary
research_direction_extensions/ # four extra direction probes + predictions
tier2_task_suite/ # provenance baseline tasks + predictions; historical path
task_walkthroughs/ # case-study walkthroughs for walkthrough-backed tasks
omni_exploration/ # ModelScope readiness-check artifacts
omni_finetune/model_output_task_probes_20260616/ # task-13/task-16 probes derived from verified model JSON
docs/
index.html # GitHub Pages dashboard
data/additional_development_directions.json # concrete non-backbone project directions
data/summary_metrics.json # website-readable metrics bundle
data/task_suite_20.json # unified 20-task suite bundle
data/unified_task_model_radar.json # 20-task radar values, groups, and sources
data/single_episode_task_model_radar.json # 1-episode grouped radar values
data/episode128_task_model_radar.json # 128-episode grouped radar values
data/task_method_20_result_matrix.json # 9-method x 20-task result matrix
data/task_method_20_gap_audit.json # explicit 180/180 scored-cell ledger
data/task_icon_manifest.json # assigned icon asset map for all 20 tasks
data/evidence_contract.json # machine-readable project scope
data/artifact_index.json # compact project-artifact catalog
data/live_publication_status.json # live GitHub/HF publication verification
data/quality_gates.json # machine-readable release checks
data/task_suite_enhancement_128.json # no-new-episode 128-suite enhancement pack
data/task_surface_integrity.json # machine-readable task-card/storyboard integrity check
data/project_manifest.json # machine-readable public-surface metadata
data/project_packet.json # compact project path and scope summary
data/research_roadmap.json # multi-episode and omni-model roadmap
data/research_directions.json # four-track website data bundle
data/research_direction_extensions.json # four extra probe data bundle
assets/task-icons/*.svg # one crisp assigned icon per task
assets/task-icons/task-icon-atlas.png # generated overview atlas for the 20-task visual language
data/tier2_task_suite.json # provenance baseline bundle; historical path
data/task_walkthroughs.json # human-readable task-card and walkthrough-storyboard data
data/modality_atlas.json # responsive modality-card data
assets/brand/*.png # project logo, favicon, social card
assets/task_suite_infographic.png # task-suite presentation graphic
assets/modalities/ # public-sample derived modality thumbnails
assets/pipeline_diagram.png # verified episode pipeline graphic
assets/qwen3_omni_lora_pipeline.png # Qwen3-Omni LoRA training-flow figure
assets/task_architectures.png # verified task-head architecture map
assets/charts/unified_task_model_radar.svg # 9-method grouped small-multiple radar board
assets/charts/single_episode_task_model_radar.svg # 1-episode enlarged radar panel
assets/charts/episode128_task_model_radar.svg # 128-episode grouped radar panels
assets/charts/*.svg # regenerated visualizations
notes/
min_action_model.md
all_modalities_model.md
episode_task_suite.md
Raw Xperience-10M data is not committed. Download it from the official Ropedia distribution and follow the dataset terms.
The public dashboard is packaged as a static-site container on GitHub Container
Registry. It contains the docs/ site plus the main project documents; it does
not include raw Xperience-10M videos, raw annotations, gated data, or model
weights.
docker pull ghcr.io/chaoyue0307/ropedia-xperience-10m-task-suite:latest
docker run --rm -p 8080:80 ghcr.io/chaoyue0307/ropedia-xperience-10m-task-suite:latest
Then open http://localhost:8080.
The scripts expect a workspace with the Ropedia HOMIE toolkit and the Xperience-10M sample episode:
<workspace>/
HOMIE-toolkit/
data/sample/xperience-10m-sample/
annotation.hdf5
fisheye_cam0.mp4
fisheye_cam1.mp4
fisheye_cam2.mp4
fisheye_cam3.mp4
stereo_left.mp4
stereo_right.mp4
The public website also includes a Raw Sample Browser that lists every official
sample file, plays compact browser-preview clips derived from the official MP4
streams, exposes the audio track embedded in fisheye_cam0.mp4, links the full
raw Hugging Face source for each MP4/HDF5/RRD file, and describes the
annotation.hdf5 group organization without copying large raw files into this
repository. The same manifest also lists what the non-playable
annotation.hdf5 and visualization.rrd files contain, how each relates to
the synchronized MP4 streams and 20-frame windows, and which external tools can
open them.
The public sample dataset identifier is:
ropedia-ai/xperience-10m-sample
Hugging Face URL:
https://huggingface.co/datasets/ropedia-ai/xperience-10m-sample
From a workspace folder:
git clone https://github.com/Ropedia/HOMIE-toolkit.git
python3.12 -m venv .venv
source .venv/bin/activate
pip install -r HOMIE-toolkit/requirements.txt huggingface_hub hf_xet
Download the sample:
hf download ropedia-ai/xperience-10m-sample \
--repo-type dataset \
--local-dir data/sample/xperience-10m-sample
If Hugging Face access is unavailable in your environment, use ModelScope:
python scripts/omni/download_sample_modelscope.py \
--output-dir data/sample/xperience-10m-sample \
--mode minimal
--mode minimal downloads annotation.hdf5, README.md, and
fisheye_cam0.mp4. Use --mode all-training to add all six MP4 streams while
still skipping visualization.rrd.
Clone and run this repo:
git clone https://github.com/ChaoYue0307/ropedia-xperience-10m-task-suite.git
cd ropedia-xperience-10m-task-suite
python scripts/episode_task_suite.py --workspace /path/to/workspace
Run the public-sample task definitions with lightweight neural heads:
pip install torch
python scripts/episode_task_suite.py \
--workspace /path/to/workspace \
--include-neural
Then rebuild the unified 20-task index after the historical provenance bundle is regenerated:
python scripts/tier2_task_suite.py --workspace /path/to/workspace
python scripts/build_unified_task_suite.py
python scripts/build_evaluation_protocol.py
Run the smaller baselines:
python scripts/train_min_action_model.py --workspace /path/to/workspace
python scripts/train_all_modalities_model.py --workspace /path/to/workspace
This repo includes a first Qwen3-Omni fine-tuning path over Xperience-10M. The repository separates public-sample evidence from multi-episode fine-tuning artifacts. The selected-episode held-out package is now verified as a diagnostic result, not a strong final action/subtask model. The useful distinction is:

The figure shows the intended end-to-end training flow: raw valid episodes enter episode-level split validation, parallel media/sensor export creates Qwen-style JSONL records, Qwen3-Omni receives video/audio/text directly, the sensor bridge adds depth/pose/mocap/IMU features, LoRA adapters are trained on prepared train/val episodes, and sealed held-out test evaluation produces predictions, metrics, run reports, and upload-ready adapter artifacts.
The scale-up path requires valid prepared episodes, held-out episode splits,
training metadata, predictions, metrics, and a run report. A result is ready
for public README, website, or Hugging Face updates only after the validator
passes and scripts/omni/package_verified_omni_result.py creates a
public-safe derived-artifact package. The current verified package is listed in
docs/data/omni_finetune_verified_result.json.
The current cross-version comparison is generated at
docs/data/omni_model_comparison.json
and results/omni_finetune/OMNI_MODEL_COMPARISON.md;
it separates the single-episode task suite, 128-episode aligned simple/NN
baselines, Qwen3-Omni v6 LoRA, Cosmos3-Super Reasoner, and Cosmos3-Nano Future Window packages. The same generated
files also include model_groups: a model-first view that pairs 1-episode and
128-episode entries for the same family. Use that section when comparing task
heads against task heads, Qwen3-Omni smoke/LoRA against Qwen3-Omni LoRA, or
Cosmos3-Nano compatibility against future Cosmos weight releases. For
Qwen3-Omni specifically, read QWEN3_OMNI_RUN_LINEAGE.md: v1-v4 are
pipeline-hardening and ablation evidence, v5 is the pinned prior multiscale
release, and v6 is the current public 20-task Qwen row.
The no-new-episode enhancement plan is recorded in
docs/data/task_suite_enhancement_128.json
and TASK_SUITE_ENHANCEMENT_128.md. It keeps
the current Qwen3-Omni v6 and Cosmos3 packages as baselines, then defines dense-window
scenarios, hierarchical action/subtask targets, task bottlenecks, and experiment
cards for stronger selected-128 runs without overwriting earlier results.
Do not treat "10M" as a reason to start with the entire dataset. The engineering unit that matters first is diverse held-out episodes, not adjacent windows from one session.
| Phase | Episodes/samples | Approx windows at stride 5 | Purpose |
|---|---|---|---|
| Readiness | 1-3 | 1k-3k | Verify loaders, token alignment, and task heads |
| Pilot | 16-32 | 18k-37k | First held-out-episode evaluation |
| Useful LoRA run | 64-128 | 74k-149k | Train sensor adapters plus selected Qwen3-Omni LoRA |
| Storage-heavy run | 256+ | 297k+ | Only after download layout and checkpoint size are stable |
Use the budget helper before downloading:
python scripts/omni/plan_finetune_sample_budget.py \
--storage-root /path/to/storage \
--target-free-after-download-gb 800 \
--all-training-per-episode-gb 2.4 \
--full-preview-per-episode-gb 5.1
python scripts/omni/discover_xperience10m_sources.py \
--workspace /path/to/ropedia-xperience-10m-task-suite \
--data-root /path/to/xperience10m_data \
--output results/omni_finetune/source_discovery.json
Current status in this repo:
visualization.rrdXPERIENCE10M_128_EPISODE_FEATURE_INDEX.md and docs/data/xperience10m_128_episode_feature_index.jsonropedia-ai/xperience-10m episode pathsresults/omni_finetune/source_discovery.jsonresults/omni_finetune/DATA_ACCESS_STATUS.mdresults/omni_finetune/MULTI_EPISODE_ACCESS_STATUS.mdUse this gate before scheduling any full fine-tune run. The pilot should use
balanced held-out selection, not the first paths in repository order. The
current 128-episode selection filters for complete leaf episodes, excludes
visualization.rrd, balances episode-size bands, and preserves one selected
episode per top-level session UUID.
The selected 128-episode plan can be used before every episode has arrived by
training only on prepared train episodes and monitoring prepared val episodes.
The final test episodes stay sealed until the end, so early development does
not contaminate held-out evaluation.
python scripts/omni/build_selection_episode_manifest.py \
--workspace /path/to/ropedia-xperience-10m-task-suite \
--data-root /path/to/xperience10m_128 \
--selection-json results/omni_finetune/xperience10m_128_episode_selection.json \
--output results/omni_finetune/trainval_progressive/episode_manifest_trainval.json \
--include-split train \
--include-split val
scripts/omni/run_trainval_progressive_128.sh wraps the same guard, exports a
train/val-only Qwen3-Omni JSONL dataset, and launches LoRA training without
running final test evaluation. The exporter uses session-qualified episode IDs
and path-based split matching so repeated folder names such as ep1 cannot
collide across different sessions.
For larger prepared subsets, scripts/omni/run_trainval_parallel_export_8gpu.sh
uses the same split guard, exports episodes in parallel CPU shards, skips and
reports episodes that contain no labeled windows under the configured label
rule, then launches Qwen3-Omni LoRA with NUM_PROCESSES=8.
Once all selected episodes are complete, use the fixed selected-episode split:
The clean full-run launcher validates the selected split, exports all splits in parallel, trains Qwen3-Omni LoRA on train episodes while optionally monitoring validation loss, then evaluates on the held-out test split:
RUN_ID=xperience10m_qwen3_omni_128ep_fullsplit_fast8gpu \
DATA_ROOT=/path/to/xperience10m_128 \
SELECTION_JSON=results/omni_finetune/xperience10m_128_episode_selection.json \
MODEL_DIR=/path/to/Qwen__Qwen3-Omni-30B-A3B-Instruct \
NUM_PROCESSES=8 \
TRAIN_VAL_SPLIT=val \
MAX_VAL_SAMPLES=512 \
scripts/omni/run_128_fullsplit_parallel_export_8gpu.sh
The latest verified diagnostic package uses the same selected split and 8-GPU training path, includes the full held-out evaluation with 4,032 predictions and 99.90% JSON validity, and keeps raw data plus full Qwen weights out of the public repos. The next pass should keep this package contract while improving action/subtask target quality and error analysis.
Monitor the run with:
python scripts/omni/monitor_omni_progress.py \
--run-id xperience10m_qwen3_omni_128ep_fullsplit_fast8gpu
The monitor reads training progress.jsonl, new evaluator partial-prediction
progress, and legacy generation logs, so long held-out evals can still expose
sample-level progress even before final metrics are written.
Validate the run artifacts stage by stage:
python scripts/omni/validate_omni_finetune_run.py \
--run-id xperience10m_qwen3_omni_128ep_fullsplit_fast8gpu \
--require-stage manifest
python scripts/omni/validate_omni_finetune_run.py \
--run-id xperience10m_qwen3_omni_128ep_fullsplit_fast8gpu \
--require-stage eval \
--min-json-validity 0.98
After the eval validator passes, create the public-safe result package:
python scripts/omni/package_verified_omni_result.py \
--dataset-run-id xperience10m_qwen3_omni_128ep_fullsplit_fast8gpu \
--train-run-id <train_run_id> \
--eval-run-id <eval_run_id>
For long-running remote jobs, the packaging step can be watched automatically:
python scripts/omni/watch_verified_omni_package.py \
--dataset-run-id xperience10m_qwen3_omni_128ep_fullsplit_fast8gpu \
--train-run-id <train_run_id> \
--eval-run-id <eval_run_id>
While waiting, the watcher can append eval_progress_observed events from
partial prediction files or legacy generation logs. This keeps the package
status file useful during long held-out evaluations.
The package copies only small derived artifacts such as metrics, predictions,
confusion matrices, run reports, manifests, validation summaries, and training
metadata. The exact required eval files and primary metrics come from the
selected backbone contract in configs/omni_backbones, so Qwen3-Omni,
Cosmos-style world models, and VLA/policy tracks can share the same verified
publication gate once their model-specific evaluators exist. The package
excludes raw Xperience-10M files, base-model weights, adapter or checkpoint
weights, full checkpoints, and large archives.
For hardware setups that can run multiple eval workers, the Qwen evaluator also supports deterministic sample shards:
CUDA_DEVICE_GROUPS="0,1 2,3 4,5 6,7" \
SHARDS=4 \
RUN_ID=<merged_eval_run_id> \
scripts/omni/run_qwen3_omni_lora_eval_sharded.sh
Only the merged eval directory should be validated and reported publicly, because the merger checks coverage and recomputes the metrics from all held-out predictions.
After dataset export, a model-neutral window index can be created for future backbones:
python scripts/omni/export_model_neutral_window_index.py \
--dataset-jsonl results/omni_finetune/xperience10m_qwen3_omni_128ep_fullsplit_fast8gpu_dataset/dataset.jsonl
This produces window_index.jsonl and window_index_manifest.json so Cosmos-
style world models and VLA/policy tracks can reuse the same split-checked
windows without depending on Qwen chat-message records.
The public-safe verified package intentionally excludes raw data, base Qwen weights, LoRA weights, and full checkpoints. Adapter upload is a separate step: use it only when the intended adapter directory is present and the model card clearly distinguishes older smoke weights from the final selected-episode diagnostic run.
Keep weight-bearing repositories model-specific: the final 128-episode
Qwen3-Omni adapter belongs in cy0307/ropedia-qwen3-omni-lora-128ep, older
Qwen smoke material remains historical. Cosmos3-Nano remains an artifacts-only
compatibility result; Cosmos3-Super Forward-Dynamics now has a separate
weight-bearing model repo at
cy0307/ropedia-cosmos3-super-forward-dynamics-lora-128ep.
Metrics, predictions, audits, and reports stay in the artifact dataset.
python3 scripts/omni/upload_qwen3_omni_lora_to_hf.py \
--repo-id cy0307/ropedia-qwen3-omni-lora-128ep \
--source-dir /path/to/adapter_upload_package \
--message "Upload Xperience-10M Qwen3-Omni LoRA pilot"
This script requires a valid Hugging Face token via HF_TOKEN or --token.
Network availability to huggingface.co is required.
The next modeling plan tracks several foundation-model tracks instead of assuming one backbone solves every Xperience-10M objective.
| Branch | Current role | When to use it |
|---|---|---|
| Qwen3-Omni | First trainable multimodal LoRA pilot | Use for the selected 128-episode held-out baseline over video/audio/language plus sensor-bridge features. |
| Cosmos 3 | First world-model/action-generation track | Use now for future-window compatibility analysis and the verified Cosmos3-Super forward-dynamics LoRA artifact; compare its loss metrics separately from Qwen JSON-task accuracy. |
| GR00T | Humanoid/action-policy track | Use after mocap/contact retargeting creates well-defined humanoid action targets. |
| OpenVLA / openpi | Open VLA/policy baselines | Use after the project defines robot-compatible or action-token targets. |
| Gemini Robotics | External reasoning reference | Use only for qualitative comparison or annotation support unless local trainable access exists. |
| Xperience Embodied Foundation Model | Future Xperience-native pretraining goal | Use only after multi-episode pilots, full-corpus storage, distributed training infrastructure, and scaling evidence justify a from-scratch domain model. |
See FOUNDATION_MODEL_PLAN.md and
docs/data/foundation_model_plan.json
for the full selection matrix, source links, and model-specific evaluation
additions. See
XPERIENCE_EMBODIED_FOUNDATION_MODEL_PRETRAINING.md
for the long-term full-corpus pretraining plan.
The three headline foundation directions are also separated as pipeline tracks so each track is easy to read without mixing current results and future work:
| Pipeline track | First concrete pipeline | Current scope |
|---|---|---|
| Spatial intelligence models | Build scene/object memory targets from multiview RGB, depth, pose, calibration, object cues, and language prompts. | Ready as a geometry/reasoning pipeline; the next readout is held-out spatial QA, pose consistency, counting, and scene-memory metrics. |
| Human-video world models | Predict next action, next subtask, future object set, contact transition, and future state from observed interaction windows. | Partially evidenced by future-task probes and Cosmos-style artifacts; visual/latent future quality still needs stronger metrics. |
| Vision-language-action models | Convert egocentric video, captions, hand/body motion, contacts, and objects into action chunks or policy-compatible targets. | Feasible, but gated by action-token conversion, normalization, retargeting evidence, and held-out policy metrics. |
For the single public sample, each direction is now shown as an explicit training-pair recipe:
| Direction | One-sample input | One-sample output target |
|---|---|---|
| Spatial intelligence | 20-frame windows from windows.csv / shared_windows.npz, joined with six MP4 camera streams plus annotation.hdf5 depth, pose, SLAM/calibration, object/contact cues, and optional language questions. | Camera-view match, object relevance, object-set memory, depth/pose reconstruction proxy, caption-grounded retrieval, and spatial QA targets. |
| Human-video world model | Current observed window at time t: RGB/audio/sensor summaries, hand/body motion, camera pose, current object/contact state, and current action/subtask context only. | Shifted future targets: next action, next subtask, future object set, contact transition, time-to-transition, camera-motion delta, or latent/future feature. |
| Vision-language-action | Egocentric/fisheye video, caption/object context, hand/body mocap, contact state, and current subtask text as observation-language input. | Action-token proxies: current/next action, object-conditioned action relation, contact state, interaction-text class, subtask transition, or hand-trajectory/action-chunk proxy. |
High-resolution slide diagrams for the three tracks are published in
docs/assets/foundation-pipelines. Spatial
intelligence and human-video world modeling use the clean slide PNGs supplied
for publication and are exported as 2560-pixel public images. The 2026-06-19
refresh verified that the latest uploaded Spatial and Human-video PNGs are
byte-identical to the committed clean source cache. The VLA card now uses the
clean VLA slide PNG supplied afterward and is exported through the same
2560-pixel public path. These images are
communication assets, not completed model-quality evidence; the exact task,
training, and evaluation contracts remain in the Markdown and JSON files.
Spatial intelligence models

Human-video world models

Vision-language-action models

See THREE_FOUNDATION_PIPELINES.md and
docs/data/three_foundation_pipelines.json.
Backbone-specific contracts now live in configs/omni_backbones.
The extension contract is documented in
OMNI_MODEL_EXTENSION_CONTRACT.md, and the
registry can be checked with:
python scripts/omni/backbone_registry.py --validate --json
Verify that every configured backbone can pass the public-safe packaging contract on synthetic derived artifacts:
python scripts/omni/smoke_test_backbone_packaging.py
After a real held-out package is created, audit it before updating README, website, or Hugging Face pages:
python scripts/omni/audit_verified_omni_package.py \
--package-dir results/omni_finetune/verified_public/<eval_run_id>
Create a new planned backbone track from an existing contract template with:
python scripts/omni/scaffold_omni_backbone.py \
--template-backbone policy_vla_branch \
--id new_policy_branch \
--display-name "New Policy Branch" \
--model-family "Model family name" \
--dataset-contract xperience10m_observation_action_v1 \
--training-objective observation_to_action_policy \
--checkpoint-gate policy_checkpoint_action_space_and_normalizer \
--dry-run
Each backbone config declares the checkpoint gate, required train/eval files, allowed public artifacts, and forbidden private or heavyweight artifacts. This keeps Qwen3-Omni, Cosmos-style world models, and policy/VLA tracks on the same split, validation, and publication discipline even though their training targets are different.
Beyond backbone selection and fine-tuning, Xperience-10M supports several concrete research-development tracks:
| Direction | First useful artifact | Role in the project |
|---|---|---|
| Episode taxonomy and data engine | Episode atlas, balance report, and split builder | Select representative data before training. |
| Standardized benchmark protocol | Versioned train/val/test manifests and metric scripts | Make future model results comparable. |
| Multimodal representation learning | Contrastive and masked-window encoder objectives | Learn reusable video/audio/depth/pose/mocap/IMU/language features. |
| Skill and procedure graph mining | Step graph, transitions, preconditions, and effects | Connect perception to planning and long-horizon reasoning. |
| Human-object affordance modeling | Contact, reachable-object, tool-use, and next-affordance tasks | Model what actions the scene makes possible. |
| 3D/4D scene and object memory | Persistent scene/object maps from depth, pose, multiview video, and objects | Track world state beyond single frames. |
| Data-quality and synchronization diagnostics | Per-episode QA for drift, missing streams, calibration, and corrupted files | Keep large multimodal training trustworthy. |
| Policy, retargeting, and simulation transfer | Action-token conversion and robot-compatible imitation examples | Bridge human egocentric experience to robot policy work. |
See ADDITIONAL_DEVELOPMENT_DIRECTIONS.md
and docs/data/additional_development_directions.json.
The walkthrough-backed task contracts are organized against the four Ropedia research directions in a source-linked companion set:
The taxonomy uses two current baselines for every task:
| Baseline | Role |
|---|---|
| Minimal interpretable heads | Softmax, logistic, ridge, and retrieval heads over the 8,546-dimensional multimodal representation. These expose the input/output contract cleanly. |
| Neural MLP heads | Small PyTorch MLP classifiers/regressors on the same features and splits. These check whether nonlinear heads help before moving to Qwen/Omni fine-tuning. |
Current direction-level coverage:
| Direction | Current status | Covered task evidence | What is not solved yet |
|---|---|---|---|
| A. Human Modeling & Motion Understanding | Partially implemented | Hand Trajectory Forecasting and Contact State Prediction are direct; Action Recognition and Object Relevance Prediction are proxies. Neural MLP improves hand forecasting from 0.8647 to 0.1079 MPJPE. | No full body/shape model, SMPL/MANO target, deformation prior, or multi-episode motion-generation evaluation yet. |
| B. 3D/4D Reconstruction & Neural Rendering | Prerequisite evidence | Cross-Modal Retrieval, Cross-Modal Reconstruction, and Multimodal Synchronization Detection test alignment/reconstruction prerequisites. | No NeRF, Gaussian Splatting, TSDF, mesh, novel-view synthesis, or calibrated 4D reconstruction model yet. |
| C. Egocentric Vision & Interaction | Strongest implemented track | 6 direct tasks: action, subtask, transition, next-action, object relevance, and caption grounding, plus alignment/order diagnostics and audio ablation. | Single-episode chronological split limits generalization; stronger audio and video-language backbones still need multi-episode testing. |
| D. Scene Reconstruction & World Modeling | World-model prerequisite evidence | Procedure Step Recognition, Next-Action Prediction, Object Relevance Prediction, Cross-Modal Retrieval, Cross-Modal Reconstruction, Temporal Order Verification, and Multimodal Synchronization Detection provide state/world-model probes. | No persistent scene graph, object permanence task, long-term map, or held-out-episode world model yet. |
The important interpretation is that all four directions can be started from the Xperience-10M sample modalities, but only direction C is strongly represented by the current task evidence. Directions A, B, and D need additional targets and multi-episode training before they become full research deliverables.
Alongside the unified 20-task suite, the repo includes one data-backed probe for
each research direction. These probes are computed from the same
shared_windows.npz, windows.csv, and feature_manifest.json artifacts, so
the reported numbers are computed from sample-derived features and saved metric artifacts.
research_direction_extension_results.jsonresearch_direction_extension_summary.mddocs/data/research_direction_extensions.jsonresearch_direction_extension_tasks.svg| Direction | New extension task | Input | Output | Minimal | Neural MLP | Why it matters |
The model card is truncated. Read the rest on Hugging Face.