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

Raise early if circuit uses faulty qubits or gates #792

Closed
kdk opened this issue Apr 5, 2023 · 1 comment · Fixed by #794
Closed

Raise early if circuit uses faulty qubits or gates #792

kdk opened this issue Apr 5, 2023 · 1 comment · Fixed by #794
Labels
enhancement New feature or request

Comments

@kdk
Copy link
Member

kdk commented Apr 5, 2023

What is the expected feature or enhancement?

Currently, if a user submits a circuit which uses gates or qubits which are marked as faulty, they will get an opaque IBMJobFailureError due to an error in transpilation.

It should be possible, when backends have faulty qubits or gates, to scan submitted circuits and raise early if there is an instruction on a faulty gate or qubit. This can help users avoid waiting in the queue for jobs which cannot run successfully, and gives an opportunity to inform the user to either use different physical qubits, or re-transpile their circuit with a different seed or settings .

N.B. Qiskit/qiskit-ibm-provider#568 raises the same concern for qiskit-ibm-provider, but as far as I can tell, this would have to be addressed in both the provider and the runtime. Feel free to close one of them if that's not the case.

Acceptance criteria

@kdk kdk added the enhancement New feature or request label Apr 5, 2023
@blakejohnson
Copy link
Contributor

I believe we should do this check whenever skip_transpilation=True for either the Sampler or Estimator.

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

Successfully merging a pull request may close this issue.

2 participants