Abstract / Overview

Cosmos Transfer 2.5, Cosmos Predict 2.5, and Cosmos Reason 2 together form a practical world-modeling stack for physical AI. They address three core needs: scalable realistic data generation, future world prediction, and grounded spatio-temporal reasoning. Isaac GR00T N1.6 complements this stack by converting multimodal observations and language into executable robot actions.

Used together, these systems enable a closed-loop workflow:

The result is an end-to-end pipeline from simulation to real-world robot execution.

Conceptual Background

Model Roles at a Glance

  1. Cosmos Transfer 2.5
    Transforms structured simulation outputs into photorealistic videos using multi-control conditioning such as depth, segmentation, and edges.

  2. Cosmos Predict 2.5
    Acts as a learned world model that predicts future video trajectories from text, images, or videos.

  3. Cosmos Reason 2
    Provides spatio-temporal visual reasoning, localization, and structured explanations over images and video sequences.

  4. Isaac GR00T N1.6
    A vision-language-action robot foundation model that outputs manipulation actions from multimodal inputs.

Why This Stack Works Together

Each stage feeds the next, forming a feedback loop that continuously improves policy quality.

Step-by-Step Walkthrough

Environment Prerequisites

Cosmos Transfer 2.5

Installation

git clone [email protected]:nvidia-cosmos/cosmos-transfer2.5.git
cd cosmos-transfer2.5

curl -LsSf https://astral.sh/uv/install.sh | sh
source $HOME/.local/bin/env

uv sync
source .venv/bin/activate

uv tool install -U "huggingface_hub[cli]"
hf auth login

Running Inference

Single GPU

python examples/inference.py \
  --params_file assets/robot_example/depth/robot_depth_spec.json

Multi-GPU

torchrun --nproc_per_node=8 \
  -m examples.inference \
  --params_file assets/robot_example/vis/robot_vis_spec.json \
  --num_gpus=8

Control Best Practices

Cosmos Predict 2.5

First Rollout

python examples/inference.py \
  -i assets/base/robot_pouring.json \
  -o outputs/base_video2world \
  --inference-type=video2world

Inference Modes

Minimal Input JSON

{
  "inference_type": "video2world",
  "name": "robot_pouring",
  "prompt": "A robotic arm pours liquid into a cup on a workbench.",
  "input_path": "robot_pouring.mp4"
}

Cosmos Reason 2

Installation

git clone https://github.com/nvidia-cosmos/cosmos-reason2.git
cd cosmos-reason2

sudo apt-get install -y curl ffmpeg git git-lfs

curl -LsSf https://astral.sh/uv/install.sh | sh
source $HOME/.local/bin/env

uv sync
hf auth login

Serving with vLLM

uv run vllm serve nvidia/Cosmos-Reason2-2B \
  --allowed-local-media-path "$(pwd)" \
  --max-model-len 8192 \
  --media-io-kwargs '{"video": {"num_frames": -1}}' \
  --reasoning-parser qwen3 \
  --port 8000

Typical Outputs Used in Robotics

Isaac GR00T N1.6

Repository Setup

git clone --recurse-submodules https://github.com/NVIDIA/Isaac-GR00T
cd Isaac-GR00T
git submodule update --init --recursive

Recommended Workflow

Why N1.6 Matters

End-to-End Integration Pipeline

cosmos-transfer-predict-reason-groot-pipeline

Workflow Manifest Example

{
  "run_name": "robotics-world-modeling-to-policy-v1",
  "transfer25": { "model": "Cosmos-Transfer2.5" },
  "predict25": { "inference_type": "video2world" },
  "reason2": { "serve_port": 8000 },
  "groot_n16": { "finetune": true }
}

Use Cases

Limitations and Considerations

Common Fixes

FAQs

  1. Do I need all four models?
    No. Start with Transfer + GR00T, then add Predict and Reason as complexity grows.

  2. What is the fastest proof of value?
    Fine-tune GR00T on Transfer-generated photoreal data and compare against zero-shot performance.

  3. How should this be deployed?
    Transfer and Predict as offline batch jobs, Reason as a service, GR00T close to the robot controller.

Conclusion

Cosmos Transfer 2.5, Cosmos Predict 2.5, Cosmos Reason 2, and Isaac GR00T N1.6 together form a complete physical AI pipeline. Transfer scales realism, Predict explores futures, Reason enforces understanding, and GR00T executes actions. When connected through reproducible specs and validated datasets, this stack enables robust robot learning from simulation to real-world deployment.