Automate getting fake backend#113
Open
ashsaki wants to merge 2 commits into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, we used to get a FakeBackend object from a name using a hand-written and large dictionary named
STR_TO_IBM_FAKE_BACKEND. When a new FakeBackend is added to qiskit-ibm-runtime, we need to update this hard-coded dictionary manually. Also, it is prone to typos and rather large.This PR replaces the hard-coded fake backend dictionary with an automated appraoch. In the new approach, we gather available fake backend from their source qiskit-ibm-runtime (or qiskit in case someone is still benchmarking a very old <= 1.0 version of qiskit).
Aslo, now it supports setting the fake backend name in two formats: Both
fake_torinoor actual object nameFakeTorinoare supported in thedefault.conf.