-
Notifications
You must be signed in to change notification settings - Fork 12
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.
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
remove remote simulator #301
Changes from all commits
9807e3f
6b7aa63
3d10ed3
195c8e7
7c6d0b3
b1c8ba9
b3598ac
bff3e00
b17a67e
a7a2470
6a3f76d
12eb951
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,7 +29,6 @@ Available IBM Backends | |
|
||
IBMQBackend | ||
IBMQEmulatorBackend | ||
IBMQLocalEmulatorBackend | ||
AerBackend | ||
AerStateBackend | ||
AerUnitaryBackend | ||
|
@@ -95,7 +94,7 @@ to disk: | |
IBMProvider.save_account(token=ibm_token) | ||
QiskitRuntimeService.save_account(channel="ibm_quantum", token=ibm_token) | ||
|
||
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. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The local emulator was not listed here? Is this functionality available with the local setup? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
No, it's just a class method on |
||
To see which devices you can access you can use the ``available_devices`` method on the :py:class:`IBMQBackend`. 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. | ||
|
||
:: | ||
|
||
|
@@ -160,7 +159,7 @@ Default Compilation | |
|
||
Every :py:class:`Backend` in pytket has its own ``default_compilation_pass`` method. This method applies a sequence of optimisations to a circuit depending on the value of an ``optimisation_level`` parameter. This default compilation will ensure that the circuit meets all the constraints required to run on the :py:class:`Backend`. The passes applied by different levels of optimisation are specified in the table below. | ||
|
||
.. list-table:: **Default compilation pass for the IBMQBackend, IBMQEmulatorBackend and IBMQLocalEmulatorBackend** | ||
.. list-table:: **Default compilation pass for the IBMQBackend and IBMQEmulatorBackend** | ||
:widths: 25 25 25 | ||
:header-rows: 1 | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add that simulatons that used
IBMQEmulatorBackend
previously will now run locally. Just to be explcit.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done in a7a2470