Open nonhermitian opened 1 year ago
Any updates on this? It is a constant thorn when working with backends of various kinds
This issue has to move to qiskit-ibm-runtime. See a comment that I wrote in the PR: https://github.com/Qiskit/qiskit-ibm-runtime/pull/2005#issuecomment-2454755261.
Environment
What is happening?
Fake backends are just wrappers around the Aer simulator. However they themselves do not return
simulator=True
. This is problematic because there are cases where knowing if the execution is on a simulator, as opposed to a real device, can be used to select methods that are more efficient. Example, usingindependent
(single-qubit) calibrations in M3 vs. thebalanced
method used on real-hw.How can we reproduce the issue?
yields
False
. As a corollary, on V2 fake backends, there is noconfiguration
, so it is not clear how to determine if a V2 backend is a simulator or not.What should happen?
Being a simulator, the fake backends should indicate this in the configuration, or wherever the same info is found on V2 backends.
Any suggestions?
No response