You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there are two Qiskit "providers" for Qiskit Runtime - qiskit-ibm-runtime and qiskit-ibm-provider. The former supports all channels but does not support backend.run (i.e. primitives only). The latter supports backend.run but only supports IQP channel.
Since we are adding backend.run() to this repo, we will merge the two providers since they'd essentially do the same thing.
This means we will also deprecate and eventually archive qiskit-ibm-provider
Make sure there are no instances/uses of qiskit-ibm-provider in this repo
The text was updated successfully, but these errors were encountered:
@1ucian0 The plan is to hold off until v2 Sampler becomes available, which will replace backend.run. So people can migrate from backend.run in ibm-provider directly to Sampler in ibm-runtime.
1ucian0
added a commit
to 1ucian0/qiskit-ibm-runtime
that referenced
this issue
Feb 1, 2024
Currently there are two Qiskit "providers" for Qiskit Runtime -
qiskit-ibm-runtime
andqiskit-ibm-provider
. The former supports all channels but does not supportbackend.run
(i.e. primitives only). The latter supportsbackend.run
but only supports IQP channel.Since we are adding
backend.run()
to this repo, we will merge the two providers since they'd essentially do the same thing.This means we will also deprecate and eventually archive
qiskit-ibm-provider
qiskit-ibm-provider
in this repoThe text was updated successfully, but these errors were encountered: