forked from Qiskit/qiskit
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
21 additions
and
0 deletions.
There are no files selected for viewing
21 changes: 21 additions & 0 deletions
21
releasenotes/notes/qubit-properties-target-6b1fb155a46cb942.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
--- | ||
features: | ||
- | | ||
Added a new attribute, :attr:`~.Target.qubit_properties` to the | ||
:class:`~.Target` class. This attribute contains a list of | ||
:class:`~.QubitProperties` objects for each qubit in the target. | ||
For example:: | ||
target.qubit_properties[2] | ||
will contain the :class:`~.QubitProperties` for qubit number 2 in the | ||
target. | ||
For :class:`~.BackendV2` authors, if you were previously defining | ||
:class:`~.QubitProperties` directly on your :class:`~.BackendV2` | ||
implementation by overriding :meth:`.BackendV2.qubit_properties` this | ||
will still work fine. However, if you do move the definition to the | ||
underlying :class:`~.Target` object and remove the specialized | ||
:meth:`.BackendV2.qubit_properties` implementation which will enable | ||
using qubit properties in the transpiler and also maintain API compatibility | ||
with your previous implementation |