-
Notifications
You must be signed in to change notification settings - Fork 92
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
Cannot submit list of circuits via AzureQuantumBackend.run #224
Comments
@guenp We were recently debugging the submission of StateTomography in qiskit-experiments and found that the problem was not a lack of support for job batching as the qiskit-experiment module takes care of submitting all the necessary jobs and keep track of their state; the problem was that the experiments depend on the circuit metadata to be part of the job's result object. This is fixed in #278; with this StateTomography is working correctly (albeit a couple of submission warnings for unsupported parameters). With the change in place I've also tested the QAOA and VQE examples in qiskit-tutorials and they also ran successfully. So, I'm thinking we should close this enhancement since the main scenarios you were trying to cover are working correctly. Thoughts? |
Great, glad to hear that the workaround already exists in qiskit! I'll close this issue then. |
After some more investigation as per @anpaz's comment above, we figured out that what is missing in the above example is not batch job support, but metadata on the submitted Jobs. This is addressed in this PR #278. |
Currently, to submit multiple circuits, users have to submit each circuit individually, e.g.
Iterative algorithms require being able to submit a batch of circuits at the same time. There are several Qiskit libraries that depend on support for
backend.run(circuits: List[QuantumCircuit])
, such as qiskit-experiments and qiskit-aqua. See also: https://qiskit.org/documentation/stubs/qiskit.providers.ibmq.managed.IBMQJobManager.html#qiskit.providers.ibmq.managed.IBMQJobManagerThis would require being able to submit multiple circuits and get a single job ID back to fetch the results, similar to the IBMQ experience. However, this is currently not something our service supports; Azure Quantum's Backend currently only accepts a single circuit or a list of circuits of length one, see this line: ionq.py#L70.
For instance, Tomography uses the
backend.run()
method under the hood which returns a single job: base_experiment.py#L345.The text was updated successfully, but these errors were encountered: