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
- Update GPU/CUDA step to note that PyTorch wheels bundle the CUDA
runtime and do not require manual CUDA download or CUDA_PATH.
- Replace the statement that CuPy is installed via the cucim extra;
CuPy is now installed via the dedicated monai[cupy] extra. The
cucim extra only installs cuCIM.
- Update CuPy example versions to cupy-cuda13x for CUDA 13.x.
- Quote .[all,testing] in editable-install example.
- Fix --no-build-isoloation typo.
Signed-off-by: Lanre Shittu <136805224+Shizoqua@users.noreply.github.com>
Copy file name to clipboardExpand all lines: docs/source/installation.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Ignite](https://pytorch.org/ignite/), please follow the instructions:
38
38
The installation commands below usually end up installing the CPU variant of PyTorch. To install GPU-enabled PyTorch:
39
39
40
40
1. Install the latest NVIDIA driver.
41
-
1. Check [PyTorch Official Guide](https://pytorch.org/get-started/locally/) for the recommended CUDA versions. For Pip package, the user needs to download the CUDA manually, install it on the system, and ensure CUDA_PATH is set properly.
41
+
1. Check the [PyTorch Official Guide](https://pytorch.org/get-started/locally/) for the recommended CUDA versions. For Pip packages, PyTorch wheels already bundle the CUDA runtime, so you only need to pick the CUDA version matching your driver from the selector and install with the provided command. You do not need to manually download CUDA or set `CUDA_PATH`.
42
42
1. Continue to follow the guide and install PyTorch.
43
43
1. Install MONAI using one of the ways described below.
44
44
@@ -47,15 +47,18 @@ however, additionally use [CuPy](https://cupy.dev/) for GPU-accelerated array op
47
47
when a transform converts a CUDA tensor via `convert_to_cupy`). If CuPy is not installed, these code
48
48
paths raise `OptionalImportError: import cupy (No module named 'cupy')`.
49
49
50
-
CuPy is provided through the `cucim` extra, so installing MONAI with that extra pulls in a compatible
51
-
CuPy build:
50
+
MONAI provides a dedicated `cupy` extra that installs a compatible CuPy build:
52
51
53
52
```bash
54
-
pip install 'monai[cucim]'
53
+
pip install 'monai[cupy]'
55
54
```
56
55
56
+
The `cucim` extra installs [cuCIM](https://github.com/rapidsai/cucim) (`cucim-cu12` or `cucim-cu13`
57
+
depending on your Python version), which is a separate GPU image-processing library and does not
58
+
install CuPy.
59
+
57
60
If you prefer to install CuPy directly, note that the PyPI package name is CUDA-version specific
58
-
(e.g. `cupy-cuda12x` for CUDA 12.x, `cupy-cuda11x` for CUDA 11.x) rather than plain `cupy`. See the
61
+
(e.g. `cupy-cuda12x` for CUDA 12.x, `cupy-cuda13x` for CUDA 13.x) rather than plain `cupy`. See the
59
62
[CuPy installation guide](https://docs.cupy.dev/en/stable/install.html) for the correct package for
60
63
your CUDA toolkit.
61
64
@@ -206,7 +209,7 @@ You can install it by running:
206
209
```bash
207
210
cd MONAI/
208
211
pip install -e .
209
-
# or pip install -e .[all,testing] to include most of the dependencies
212
+
# or pip install -e '.[all,testing]' to include most of the dependencies
210
213
```
211
214
212
215
or, to build with MONAI C++/CUDA extensions and install:
@@ -234,7 +237,7 @@ $env:BUILD_MONAI="1"
234
237
pip install -e .
235
238
```
236
239
237
-
If the compiled extensions were built by pip against a different version of PyTorch than the one in your environment, you may need to run the above with the `--no-build-isoloation` flag to force the use of that version, or use the `--build-constraint` method.
240
+
If the compiled extensions were built by pip against a different version of PyTorch than the one in your environment, you may need to run the above with the `--no-build-isolation` flag to force the use of that version, or use the `--build-constraint` method.
0 commit comments