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
It seems that the job is actually run, and shows on the UI. It is also possible to retrieve the results with pytket-quantinuum by setting use_websocket=False in get_result(). But when using websockets (the default), we get no response.
@cqc-alec any chance you have the job id(s) from this testing?
Sure. From a run just now (QA env), using websockets:
3632 shots: successful, job ID f621f33ceeae4779a03f569b7eb478b4
3633 shots: unsuccessful (no reply on websocket), job ID a500119299084e10b74ed3b7689f50cd
For the circuit below, it looks like N=3632; I don't know if the limit depends on the circuit.
Output:
No problems with QASM submission.
The text was updated successfully, but these errors were encountered: