Skip to content

Docs: Clarify lack of adjoint/MCM support in default.qubit #7365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Docs: Clarify lack of adjoint/MCM support in default.qubit #7365

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
21 changes: 21 additions & 0 deletions pennylane/devices/default_qubit.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -301,6 +301,27 @@ class DefaultQubit(Device):
only the current process executes tapes. If you experience any
issue, say using JAX, TensorFlow, Torch, try setting ``max_workers`` to ``None``.

.. note::
Adjoint differentiation (``diff_method="adjoint"``) is not currently supported
by this device. Supported analytic methods include ``"parameter-shift"``.
Finite difference (``"finite-diff"``) is also available.

.. note::
Native mid-circuit measurements and conditional operations (using
:func:`~.pennylane.measure` and :func:`~.pennylane.cond`) are not
supported by ``default.qubit`` in simulation workflows that require
gradients or specific state preparations dependent on measurement outcomes.
For simple sampling workflows, measurement may return values, but
dynamic circuit execution is limited. Consider devices explicitly
supporting dynamic circuits if required.


**Example:** # This existing section follows the notes

>>> dev = qml.device("default.qubit", wires=2)
[...]


**Example:**

.. code-block:: python
Expand Down