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: docs/changelog.rst
+15-1
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,25 @@
1
1
Changelog
2
2
~~~~~~~~~
3
3
4
+
0.40.0 (June 2023)
5
+
------------------
6
+
7
+
* IBM devices are now accessed using the `qiskit-ibm-provider <https://github.com/Qiskit/qiskit-ibm-provider>`_ instead of the deprecated :py:class:`IBMQ`. This allows the newest IBM devices and simulators to be accessed through ``pytket-qiskit``. See the updated documentation on `credentials <https://cqcl.github.io/pytket-qiskit/api/index.html#access-and-credentials>`_.
8
+
* The parameters ``hub``, ``group`` and ``project`` are no longer handled as separate arguments in :py:class:`IBMQBackend` and :py:meth:`IBMQBackend.available_devices`. Use ``"instance=f"{hub}/{group}/{project}"`` instead.
9
+
* Added support for the {X, SX, Rz, ECR} in the default compilation pass for :py:class:`IBMQBackend` and :py:class:`IBMQEmulatorBackend`. This is the set of gates used by some of the new IBM devices.
10
+
* Fix to the :py:meth:`tk_to_qiskit` converter to prevent cancellation of redundant gates when converting to qiskit.
11
+
* Handle qiskit circuits with :py:class:`Initialize` and :py:class:`StatePreparation` instructions in the :py:meth:`qiskit_to_tk` converter. The :py:meth:`tk_to_qiskit` converter now handles :py:class:`StatePreparationBox`.
12
+
* Fix handling of control state in :py:meth:`qiskit_to_tk`.
13
+
* Update qiskit version to 0.43.1
14
+
* Update qiskit-ibm-runtime version to 0.11.1
15
+
* Update qiskit-ibm-provider version to 0.6.1
16
+
* Update pytket version to 1.16
17
+
4
18
0.39.0 (May 2023)
5
19
-----------------
6
20
7
21
* Updated pytket version requirement to 1.15.
8
-
* The get_compiled_circuit method now allows for optional arguments to override the default settings in the NoiseAwarePlacement
22
+
* The :py:meth:`IBMQBackend.get_compiled_circuit` method now allows for optional arguments to override the default settings in the :py:class:`NoiseAwarePlacement`.
Copy file name to clipboardexpand all lines: docs/intro.txt
+16-8
Original file line number
Diff line number
Diff line change
@@ -50,45 +50,53 @@ The :py:class:`AerBackend` also supports GPU simulation which can be configured
50
50
Access and Credentials
51
51
======================
52
52
53
-
With the exception of the Aer simulators, accessing devices and simulators through the ``pytket-qiskit`` extension requires an IBMQ account. An account can be set up here: https://quantum-computing.ibm.com/login.
53
+
With the exception of the Aer simulators, accessing devices and simulators through the ``pytket-qiskit`` extension requires an IBM account. An account can be set up here: https://quantum-computing.ibm.com/login.
54
54
55
55
Once you have created an account you can obtain an API token which you can use to configure your credentials locally.
56
56
57
+
.. note:: The documentation below is correct as of pytket-qiskit version 0.40.0. In the 0.40.0 release pytket-qiskit moved to using the `qiskit-ibm-provider <https://qiskit.org/ecosystem/ibm-provider/tutorials/Migration_Guide_from_qiskit-ibmq-provider.html>`_. In pytket-qiskit versions 0.39.0 and older the parameters ``hub``, ``group`` and ``project`` were handled separately instead of a single ``instance`` string as in 0.40.0 and newer.
58
+
57
59
::
58
60
59
61
from pytket.extensions.qiskit import set_ibmq_config
60
62
61
63
set_ibmq_config(ibmq_api_token=ibm_token)
62
64
63
-
This will save your IBMQ credentials locally. After saving your credentials you can access ``pytket-qiskit`` backend repeatedly without having to re-initialise your credentials.
65
+
After saving your credentials you can access ``pytket-qiskit`` backend repeatedly without having to re-initialise your credentials.
64
66
65
67
If you are a member of an IBM hub then you can add this information to ``set_ibmq_config`` as well.
66
68
67
69
::
68
70
69
71
from pytket.extensions.qiskit import set_ibmq_config
Alternatively you can use the following qiskit commands to save your credentials
74
76
locally without saving the token in pytket config:
75
77
78
+
.. note:: If using pytket-qiskit 0.39.0 or older you will have to use the deprecated :py:meth:`IBMQ.save_account` instead of :py:meth:`IBMProvider.save_account` in the code below.
79
+
76
80
::
77
81
78
-
from qiskit import IBMQ
82
+
from qiskit_ibm_provider import IBMProvider
79
83
from qiskit_ibm_runtime import QiskitRuntimeService
To see which devices you can access you can use the ``available_devices`` method on the :py:class:`IBMQBackend` or :py:class:`IBMQEmulatorBackend`. Note that it is possible to pass ``hub``, ``group`` and ``project`` parameters to this method. This allows you to see which devices are accessible through your IBM hub.
88
+
To see which devices you can access you can use the ``available_devices`` method on the :py:class:`IBMQBackend` or :py:class:`IBMQEmulatorBackend`. Note that it is possible to pass optional ``instance`` and ``provider`` arguments to this method. This allows you to see which devices are accessible through your IBM hub.
85
89
86
90
::
87
91
88
92
from pytket.extensions.qiskit import IBMQBackend
93
+
from qiskit_ibm_provider import IBMProvider
89
94
90
-
backend = IBMQBackend # Initialise backend for an IBM device
0 commit comments