-
Notifications
You must be signed in to change notification settings - Fork 69
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
Support b.num_qubits
for BackendV2
Qiskit objects
#332
Comments
Hi @JMuff22, thank you very much for opening this feature request! It's very helpful for us to improve the plugin. By the way, we have a new PennyLane survey. We would love to know your thoughts about PennyLane in order to keep bringing you amazing features ✨. |
Whilst some checks were added in #493 . To support all backends we have been using
to some success for some time now. So |
Hi @JMuff22, thank you for your comment! We'll add some improvements to the PennyLane-Qiskit plugin in the next release which should be released in about 3 weeks. |
My feature request is related to a problem of using Qiskit backends which only support
BackendV2
objects and don't support backwards compatibility forBackendV1
. This is described in the Qiskit documentation.The current issue is that when running with such a backend fails at this line due to calling
b.configuration().n_qubits
, for which the Backend object has noconfiguration()
method. The solution would be to usebackend.num_qubits
.The solution is not simple however, because many of the tests and backends support by pennylane-qiskit have the opposite functionality in that they don't support
BackendV2
andbackend.num_qubits
cannot be called. The solution should support bothBackendV1
andBackendV2
viabackend.configuration().n_qubits
andbackend.num_qubits.
I tried this solution but I considered it hacky.
Thanks!
The particular backend I am trying to use is
IQMBackend
.The text was updated successfully, but these errors were encountered: