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
> **Note:** Starting with cuQuantum Python v25.06, cuQuantum C libraries including cuDensityMat, cuStateVec and cuTensorNet are no longer build-time dependencies. However, they are still required at runtime.
25
+
27
26
Except for CUDA and Python, the rest of the build-time dependencies are handled by the new PEP-517-based build system (see Step 7 below).
28
27
29
28
To compile and install cuQuantum Python from source, please follow the steps below:
@@ -56,14 +55,14 @@ Runtime dependencies of the cuQuantum Python package include:
56
55
* An NVIDIA GPU with compute capability 7.0+
57
56
* Driver: Linux (450.80.02+ for CUDA 11, 525.60.13+ for CUDA 12)
58
57
* CUDA Toolkit 11.x or 12.x
59
-
* cuStateVec 1.8.0+
60
-
* cuTensorNet 2.6.0+
61
-
* cuDensityMat >=0.0.5, <0.1.0
62
-
* Python 3.10+
58
+
* cuStateVec 1.9.0+
59
+
* cuTensorNet 2.8.0+
60
+
* cuDensityMat >=0.2.0, <0.3.0
61
+
* Python >=3.11, <3.14
63
62
* NumPy v1.21+
64
63
* CuPy v13.0.0+ (see [installation guide](https://docs.cupy.dev/en/stable/install.html))
65
64
* PyTorch v1.10+ (optional, see [installation guide](https://pytorch.org/get-started/locally/))
66
-
* Qiskit v0.24.0+ (optional, see [installation guide](https://qiskit.org/documentation/getting_started.html))
65
+
* Qiskit v1.4.2+ (optional, see [installation guide](https://qiskit.org/documentation/getting_started.html))
67
66
* Cirq v0.6.0+ (optional, see [installation guide](https://quantumai.google/cirq/install))
68
67
* mpi4py v3.1.0+ (optional, see [installation guide](https://mpi4py.readthedocs.io/en/stable/install.html))
69
68
@@ -77,7 +76,6 @@ to your `LD_LIBRARY_PATH` environment variable, and that a compatible CuPy is in
77
76
78
77
Known issues:
79
78
- If a system has multiple copies of cuTENSOR, one of which is installed in a default system path, the Python runtime could pick it up despite cuQuantum Python is linked to another copy installed elsewhere, potentially causing a version-mismatch error. The proper fix is to remove cuTENSOR from the system paths to ensure the visibility of the proper copy. **DO NOT ATTEMPT** to use `LD_PRELOAD` to overwrite it --- it could cause hard to debug behaviors!
80
-
- In certain environments, if PyTorch is installed `import cuquantum` could fail (with a segmentation fault). It is currently under investigation and a temporary workaround is to import `torch` before importing `cuquantum`.
81
79
- Please ensure that you use consistent binaries and packages for either CUDA 11 or 12. Mixing-and-matching will result in undefined behavior.
0 commit comments