-
Notifications
You must be signed in to change notification settings - Fork 1k
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 reset operation in QASM importer #6704
Comments
@pavoljuhas please take a look |
@natestemen - having interest to support it. Am building the equivalent thing for us planning to cover QASMv3. |
what type of reset do you support? wait, preselection, some dissipative gate? any pointers for a starter? Given:
This should be quick. I add the operation to the |
To me it looks like that reset is already somewhat prepared in the code. See:
|
@natestemen - I think #6710 should solve your issue. It's been an interesting exercise to get into |
Is your feature request related to a use case or problem? Please describe.
We’ve encountered at least two cases where Mitiq users were unable to apply an error mitigation technique because their Qiskit circuits could not be converted to Cirq. Mitiq internally represents circuits as
cirq.Circuit
objects and relies on Cirq’s QASM importer for this conversion.While I recognize that this might not be directly the responsibility of Cirq developers, I wanted to raise this issue for consideration. The QASM importer (#1548) was developed before the reset operation was introduced (#1774), so it’s possible that the reset operation was unintentionally omitted from the importer. It would be helpful to understand whether this is an area Cirq plans to address or if we should explore alternative workarounds.
Describe the solution you’d like
When converting a QASM circuit containing a reset operation, the resulting
cirq.Circuit
should include an instance ofcirq.R
to represent the reset operation.[Optional] Additional context
Here’s a minimal reproducible example:
The text was updated successfully, but these errors were encountered: