Skip to content
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

Add generic Fake Backends and update use in Qiskit unit tests #10954

Closed
7 tasks done
ElePT opened this issue Oct 3, 2023 · 1 comment · Fixed by #10918 or #10266
Closed
7 tasks done

Add generic Fake Backends and update use in Qiskit unit tests #10954

ElePT opened this issue Oct 3, 2023 · 1 comment · Fixed by #10918 or #10266
Assignees
Labels
type: feature request New feature or request
Milestone

Comments

@ElePT
Copy link
Contributor

ElePT commented Oct 3, 2023

What should we add?

In order to improve the user-friendliness of fake backends, #9553 presents a multi-step plan to migrate them to the provider. This plan includes the creation of new, non-provider specific fake backends to replace the provider-specific ones in our suite of unit tests, the migration of the provider-specific fake backends to qiskit-ibm-runtime, followed by their deprecation and removal in Qiskit.

Step 1: Introduce alternatives to provider-specific fake backends

The strategy to follow will be different for fake backends of type V1 and V2:

  • V2: Their use in tests can be replaced with a fake backend generator/ configurable fake backend. The ground work was laid out in a community PR, and I am taking over the task together with @HuangJunye.
  • V1: All uses of V1 backends will be replaced with a few representative fake backends, as the internal structure of BackendV1 does not easily allow for a backend generator.

To make the review process a bit more manageable, the work has now been divided into 3 PRs, where V1 and V2 changes can be reviewed independently:

Step 2: Migrate IBM-specific fake backends to qiskit-ibm-runtime, deprecate and remove in Qiskit 1.0

@mtreinish
Copy link
Member

This has been implemented since #11376 merged was the last step on this epic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request New feature or request
Projects
None yet
3 participants