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

qBraid API - QASM Variant Incompatibility #38

Open
johnzl-777 opened this issue Feb 5, 2025 · 1 comment
Open

qBraid API - QASM Variant Incompatibility #38

johnzl-777 opened this issue Feb 5, 2025 · 1 comment
Assignees
Labels
bug Something isn't working upstream not our fault 🤷‍♂️

Comments

@johnzl-777
Copy link
Contributor

This problem came up while I was attempting to implement the qBraid emitter requested in #3 , tagging @weinbe58 here because he requested I open this issue as well.

The approach I'm taking here is to basically just obtain the QASM2 string generated from our existing QASM emitting infrastructure and submit it to the QuEra QASM simulator which will return a standard QbraidJob users can just interact with directly.

The problem is that we emit a QASM2 variant (With things like KIRIN {py.ilist,qasm2.indexing,qasm2.inline,qasm2.glob,func,qasm2.core...}; and parallel.CZ { qreg[0], qreg[2]; qreg[1], qreg[3]; } which are certainly not standard QASM) that under the hood, the qBraid SDK attempts to translate into standard QASM2 before submission (even though I indicate things should be submitted to OUR QASM simulator) and then chokes.

I've been told by Phillip we will need to potentially meet with the qBraid team to allow for our version of QASM to be permitted to pass through.

@johnzl-777 johnzl-777 self-assigned this Feb 5, 2025
@weinbe58
Copy link
Member

weinbe58 commented Feb 5, 2025

There is no extra code we need to do on our end. @johnzl-777 is designing the qbraid target to be integrated regardless of this issue.

@Roger-luo Roger-luo added upstream not our fault 🤷‍♂️ bug Something isn't working labels Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream not our fault 🤷‍♂️
Projects
None yet
Development

No branches or pull requests

3 participants