npx skills add ...
npx skills add orchestra-research/ai-research-skills --skill evaluating-cosmos-policy
Evaluates NVIDIA Cosmos Policy on LIBERO and RoboCasa simulation environments. Use when setting up cosmos-policy for robot manipulation evaluation, running headless GPU evaluations with EGL rendering, or profiling inference latency on cluster or local GPU machines.
npx skills add orchestra-research/ai-research-skills --skill evaluating-cosmos-policy
Evaluation workflows for NVIDIA Cosmos Policy on LIBERO and RoboCasa simulation environments from the public cosmos-policy repository. Covers blank-machine setup, headless GPU evaluation, and inference profiling.
Run a minimal LIBERO evaluation using the official public eval module:
What Cosmos Policy is: NVIDIA Cosmos Policy is a vision-language-action (VLA) model that uses Cosmos Tokenizer to encode visual observations into discrete tokens, then predicts robot actions conditioned on language instructions and visual context.
Key architecture choices:
| Component | Design |
|---|---|
| Visual encoder | Cosmos Tokenizer (discrete tokens) |
| Language conditioning | Cross-attention to language embeddings |
| Action prediction | Autoregressive action token generation |
Public command surface: The supported evaluation entrypoints are cosmos_policy.experiments.robot.libero.run_libero_eval and cosmos_policy.experiments.robot.robocasa.run_robocasa_eval. Keep reproduction notes anchored to these public modules and their documented flags.
| Task | GPU | VRAM | Typical wall time |
|---|---|---|---|
| LIBERO smoke eval (1 trial) | 1x A40/A100 | ~16 GB | 5-10 min |
| LIBERO full eval (50 trials) | 1x A40/A100 | ~16 GB | 2-4 hours |
| RoboCasa single-task (2 trials) | 1x A40/A100 | ~18 GB | 10-15 min |
| RoboCasa all-tasks | 1x A40/A100 | ~18 GB | 4-8 hours |
Use this skill when:
Use alternatives when:
fine-tuning-openvla-oft)fine-tuning-serving-openpi)Copy this checklist and track progress:
Step 1: Install environment
Step 2: Configure headless rendering
Step 3: Run smoke evaluation
Step 4: Validate and parse results
Step 5: Scale up
Run across all four LIBERO task suites with 50 trials:
Copy this checklist and track progress:
Step 1: Install RoboCasa
This fork installs the robocasa Python package expected by Cosmos Policy while preserving the patched environment changes used in the public RoboCasa eval path. Verify macros_private.py exists and paths are correct.
Step 2: Single-task smoke evaluation
Step 3: Validate outputs
Success rate: line in the log.Step 4: Expand scope
Increase --num_trials_per_task or add more tasks. Keep --obj_instance_split fixed across repeated runs for comparability.
Step 1: Clone and enter the supported runtime
Step 2: Sync dependencies
Step 3: Export runtime environment
Reference values from official evaluation (tied to specific setup and seeds):
| Task Suite | Success Rate | Notes |
|---|---|---|
| LIBERO-Spatial | 98.1% | Official LIBERO spatial result |
| LIBERO-Object | 100.0% | Official LIBERO object result |
| LIBERO-Goal | 98.2% | Official LIBERO goal result |
| LIBERO-Long | 97.6% | Official LIBERO long-horizon result |
| LIBERO-Average | 98.5% | Official average across LIBERO suites |
| RoboCasa | 67.1% | Official RoboCasa average result |
Reproduction note: Published success rates still depend on checkpoint choice, task suite, seeds, and simulator setup. Record the exact command and environment alongside any reported number.
CUDA_VISIBLE_DEVICES, MUJOCO_EGL_DEVICE_ID, MUJOCO_GL=egl, and PYOPENGL_PLATFORM=egl together on headless GPU nodes.SETUP.md before debugging package internals.Issue: binary compatibility or loader failures on host Python
Fix: rerun inside the official container/runtime from SETUP.md. Do not assume host-package rebuilds will match the public release environment.
Issue: LIBERO prompts for config path in a non-interactive shell
Fix: pre-create LIBERO_CONFIG_PATH/config.yaml:
Issue: EGL initialization or shutdown noise
Fix: align EGL environment variables first. Treat teardown-only EGL_NOT_INITIALIZED warnings as low-signal unless the job exits non-zero.
Issue: Kitchen object sampling NaNs or asset lookup failures in RoboCasa
Fix: rerun asset setup and confirm the patched robocasa install is intact:
Issue: MuJoCo rendering mismatch
Fix: verify GPU device alignment:
LIBERO command matrix: See references/libero-commands.md RoboCasa command matrix: See references/robocasa-commands.md