Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -409,6 +409,11 @@ For a CUDA 12 environment, replace `cu13` with `cu12`:
uv sync --extra cu12 --extra nn-extras
```

> **Note:** If you encounter a CUDA version mismatch (e.g., "The detected
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should refine the language here - --no-build-isolation should be the way to install these packages correctly. Without that, it can cause a version mismatch.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about this?

Note: Extras such as gnns, nn-extras, and transformer-engine pull in packages that either ship only source distributions or require wheels built for a specific PyTorch and CUDA version. These should be installed with --no-build-isolation, e.g. uv sync --extra cu13 --extra gnns --no-build-isolation.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this better, thanks!

CUDA version mismatches the version that was used to compile PyTorch") when
installing extras such as `gnns`, try adding the `--no-build-isolation` flag:
`uv sync --extra cu13 --extra gnns --no-build-isolation`.

### NVCR Container

The recommended PhysicsNeMo Docker image can be pulled from the
Expand Down