-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
result.get_ran_qasm() not working #671
Comments
When we move to qobj why do we still want this option. This should be the output of the transpiler before qobj. Or are you thinking we make a qobj to qasm file |
Well, while implementing I realize two cases: If you use the wrapper shortcut Is it guaranteed that the backend will always execute the QASM sent in the Qobj? If not, you need the backend to return the actual QASM it ran. |
This seems related to #680, where running |
@delapuente I raised this bug mainly because the method is exposed in our API, but not working correctly at the moment. Going forward, QASM will not be included in Qobj at all (it is only included now because devices run QASM, and can't run Qobj directly). But even after we work with pure Qobj, it will still be very useful to see what Qobj was run after the run finished. For this, I think there should be a method Then we need two converter methods for converting from Does that make sense? |
Agree. I would simplify the method name, say |
What is the current behavior?
Result.get_ran_qasm()
seem to be broken due to PR #501. That's because the Result datastructure no longer has a copy of the qobj json inside it. We should see how/if this can be fixed with the recent introduction of Qobj class.Steps to reproduce the problem
The text was updated successfully, but these errors were encountered: