-
Notifications
You must be signed in to change notification settings - Fork 19
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
Documentation missing Arguments #426
Comments
@Z035 Thanks for opening this issue! I tried to recreate the error using the AWS SV1 device from qbraid import device_wrapper
qdevice = device_wrapper("aws_sv_sim")
qdevice.run(qiskit_circuit) but instead got the following: ValueError: No result types specified for circuit and shots=0. See `braket.circuits.result_types Which quantum device were you targeting when this happened? |
Im using IronQ's Harmony
…On Sat, Sep 30, 2023 at 15:20 Ryan Hill ***@***.***> wrote:
@Z035 <https://github.com/Z035> Thanks for opening this issue! I tried to
recreate the error using the AWS SV1 device
from qbraid import device_wrapper
qdevice = device_wrapper("aws_sv_sim")
qdevice.run(qiskit_circuit)
but instead got the following:
ValueError: No result types specified for circuit and shots=0. See `braket.circuits.result_types
Which quantum device were you targeting when this happened?
—
Reply to this email directly, view it on GitHub
<#426 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5OYC5TODBNIG7YQF4QVV6LX5BWJXANCNFSM6AAAAAA5MSYQ7Y>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@Z035 Ahh, ok I was able to re-produce! The problem occurred when I tried submitting the task through the qBraid-SDK and through the Amazon Braket SDK directly. So it seems like this bug is caused by the order of error-handling in the qBraid Quantum Jobs API. I will open the necessary issue in the private qBraid API repository and close this issue when it is resolved. Thanks! |
😆
…On Mon, Oct 2, 2023 at 11:53 Ryan Hill ***@***.***> wrote:
@Z035 <https://github.com/Z035> Ahh, ok I was able to re-produce! The
problem occurred when I tried submitting the task through the qBraid-SDK
and through the Amazon Braket SDK directly. So it seems like this bug is
caused by the order of error-handling in the qBraid Quantum Jobs API.
I will open the necessary issue in the private qBraid API repository and
close this issue when it is resolved. Thanks!
—
Reply to this email directly, view it on GitHub
<#426 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5OYC5UCXR2C7LHLR2HZGLLX5LPQ7AVCNFSM6AAAAAA5MSYQ72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGI3TQMZUGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Environment
What happened?
in # Executing Circuit section
The qjobs are missing arguments ("shots"=50).
The problem is, when executing without specifying 'shots', the code result in an error:
which does not tell you that the real problem is missing shot counts.
What is the expected outcome?
Any suggestion?
The text was updated successfully, but these errors were encountered: