You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
authored
Add cu130-torch213 dependency group (torch 2.13 on CUDA 13.0) (#134)
## What
Adds `cu130-torch213` and `cu130-torch213-train` dependency groups
pinning **torch 2.13.0+cu130** (with matching torchvision 0.28.0,
torchcodec 0.14.0, torchao 0.17.0, triton 3.7.1, `natten
0.21.6+cu130.torch213` on aarch64, and the cu13 NVIDIA runtime libs),
plus a `conflicts` entry making it mutually exclusive with the other
backend groups. `uv.lock` is regenerated for the new closure.
## Why the code change
torchvision 0.28 removed `torchvision.io.read_video`, so
`cosmos_framework/inference/vision.py` switches to a torchcodec-based
THWC uint8 decoder. It's forced onto CPU so an active default-CUDA
context during generation doesn't route torchcodec's internal
frame-index tensor to CUDA (which would raise `NotImplementedError`).
## Docs
Bumps the recommended NGC base image to
`nvcr.io/nvidia/pytorch:26.06-py3` in `README.md` and `docs/setup.md` to
match the torch 2.13 line.
## Verification
On 4× GB200 (aarch64):
- `uv sync --all-extras --group=cu130-torch213-train` resolves clean;
`torch.__version__ == 2.13.0+cu130`, `torch.version.cuda == 13.0`.
- Cosmos3-Nano `throughput` inference over **all 13**
`inputs/omni/*.json` samples (t2i, t2v, i2v, v2v, t2vs, i2vs, and the 6
action modes) produced valid outputs: videos decode with real pixel
variation (std 44–76, well above the degenerate floor), audio modes
carry an audio track, and all action arrays are non-empty and finite.
### Known limitations (in code comments)
- x86_64 has no torch2.13 wheels yet for flash-attn / TE / natten —
those are commented out / left on the torch2.10 build; this line is
validated on **aarch64**.
- torch 2.13.0+cu130 hard-pins cuDNN to 9.20.0.48; the cuDNN attention
backend wants ≥9.22 (else it falls back to NATTEN). Override at runtime
if needed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: lfengad <liangf@nvidia.com>
If you are starting from the recommended NGC image (`nvcr.io/nvidia/pytorch:25.09-py3`), see the [one-shot quickstart](./docs/setup.md#quickstart-from-the-recommended-base-image).
60
+
If you are starting from the recommended NGC image (`nvcr.io/nvidia/pytorch:26.06-py3`), see the [one-shot quickstart](./docs/setup.md#quickstart-from-the-recommended-base-image).
For CUDA 13 builds, the [NVIDIA NGC PyTorch container](https://catalog.ngc.nvidia.com/orgs/nvidia/containers/pytorch) is the recommended starting point — it bundles PyTorch + CUDA 13 + cuDNN + NCCL tuned for NVIDIA hardware, plus Apex, TransformerEngine, and Megatron utilities that training infra users commonly need.
47
47
48
48
```dockerfile
49
-
FROM nvcr.io/nvidia/pytorch:25.09-py3
49
+
FROM nvcr.io/nvidia/pytorch:26.06-py3
50
50
```
51
51
52
52
For CUDA 12.8 builds, pin to an earlier NGC tag (e.g. `nvcr.io/nvidia/pytorch:25.06-py3`) that still ships CUDA 12.
@@ -70,7 +70,7 @@ The two supported install paths are the recommended base image and the Docker co
70
70
71
71
### Quickstart: From the Recommended Base Image
72
72
73
-
If you started from the [recommended base image](#recommended-base-image) (`nvcr.io/nvidia/pytorch:25.09-py3`), the following commands set up the full environment in one go. Run them **from the root of this repository** (i.e. inside the `Cosmos/` directory you just cloned):
73
+
If you started from the [recommended base image](#recommended-base-image) (`nvcr.io/nvidia/pytorch:26.06-py3`), the following commands set up the full environment in one go. Run them **from the root of this repository** (i.e. inside the `Cosmos/` directory you just cloned):
0 commit comments