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
Copy file name to clipboardExpand all lines: doc/source/solver.rst
+17-3Lines changed: 17 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,23 @@ This is done by calling the ``set_as_default`` function and providing it with a
32
32
The ``set_as_default`` function changes several QuTiP defaults to route computations through the cuQuantum library.
33
33
This includes setting the default data format for quantum objects (``Qobj``) to ``CuOperator`` and configuring the solvers to use GPU-compatible integrators.
34
34
35
-
.. warning::
36
-
This operation is **not reversible** within the same Python session.
37
-
Once the cuQuantum backend is set, all subsequent compatible operations will be dispatched to the GPU.
35
+
This operation can be reversed with:
36
+
37
+
.. code-block:: python
38
+
39
+
qutip_cuquantum.set_as_default(reverse=True)
40
+
41
+
42
+
The backend can also be enabled with a context:
43
+
44
+
.. code-block:: python
45
+
46
+
with CuQuantumBackend(ctx):
47
+
...
48
+
49
+
However be careful when mixing core Qutip object and Qutip-cuQuantum's one.
50
+
Qutip's Qobj do not keep all the internal structure needed for cuQuantum's optimizations.
51
+
Qutip-cuQuantum's states can be distributed in multiple processes and unusable for many qutip's core features.
0 commit comments