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
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.
The text was updated successfully, but these errors were encountered:
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...};
andparallel.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.
The text was updated successfully, but these errors were encountered: