-
Notifications
You must be signed in to change notification settings - Fork 333
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
The FidelityQuantumKernel cannot be executed on the hardware for larger problems. #701
Comments
Had you tried raising an issue against IBM Runtime https://github.com/Qiskit/qiskit-ibm-runtime/issues For the defined Sampler interface there is no common notion of any max circuits limit - the only limitation, as such, to calling run, as its defined, would be machine memory to hold all the circuits. I would have expected this as such to work and internally if for some reason it needed to split them to smaller batches for some internal limits it (the Sampler) should do that itself. |
Number of maximum circuits for backend added to solve qiskit-community#701.
@OkuyanBoga can this issue be closed now? |
I believe Extended sessions and #772 will solve the issue. |
…ntum kernel trainer fixing #701 and #600 (#772) * Added an option for num_circuits per job for kernels to fix #701 * Updated documentation and format the style. * Removed deepcopy dependency in quantum_kernel_trainer.py * Added release notes * quick fix for spell test * Added unit tests for max_circuits_per_job * Update fix-701-max_circuits_per_job-and-600-deepcopy-dependency-e6eda2e5b986c1be.yaml Small release note bugfix * Update fix-701-max_circuits_per_job-and-600-deepcopy-dependency-e6eda2e5b986c1be.yaml * Minor modifications for the unit test * Removed copy of TrainableKernel --------- Co-authored-by: oscar-wallis <[email protected]>
…ntum kernel trainer fixing #701 and #600 (#772) * Added an option for num_circuits per job for kernels to fix #701 * Updated documentation and format the style. * Removed deepcopy dependency in quantum_kernel_trainer.py * Added release notes * quick fix for spell test * Added unit tests for max_circuits_per_job * Update fix-701-max_circuits_per_job-and-600-deepcopy-dependency-e6eda2e5b986c1be.yaml Small release note bugfix * Update fix-701-max_circuits_per_job-and-600-deepcopy-dependency-e6eda2e5b986c1be.yaml * Minor modifications for the unit test * Removed copy of TrainableKernel --------- Co-authored-by: oscar-wallis <[email protected]> (cherry picked from commit 2f49e9e)
…ntum kernel trainer fixing #701 and #600 (#772) (#780) * Added an option for num_circuits per job for kernels to fix #701 * Updated documentation and format the style. * Removed deepcopy dependency in quantum_kernel_trainer.py * Added release notes * quick fix for spell test * Added unit tests for max_circuits_per_job * Update fix-701-max_circuits_per_job-and-600-deepcopy-dependency-e6eda2e5b986c1be.yaml Small release note bugfix * Update fix-701-max_circuits_per_job-and-600-deepcopy-dependency-e6eda2e5b986c1be.yaml * Minor modifications for the unit test * Removed copy of TrainableKernel --------- Co-authored-by: oscar-wallis <[email protected]> (cherry picked from commit 2f49e9e) Co-authored-by: M. Emre Sahin <[email protected]>
Environment
Using IBM Lab:
What is happening?
Hi,
I think there is a problem with the way
_get_kernel_entries
handles the jobs sent to hardware.The error is:
I think the problem stems from
qiskit-machine-learning/qiskit_machine_learning/kernels/fidelity_quantum_kernel.py
Lines 203 to 212 in b4402c2
Also, it is really hard to train quantum fidelity kernel on the hardware with the sessions:
IBMRuntimeError: 'Failed to run program: \'400 Client Error: Bad Request for url: https://api.quantum-computing.ibm.com/runtime/jobs. {"errors":[{"code":1217,"message":"Session has been closed.","solution":"Reduce time between submitting subsequent jobs in a session.","more_info":"https://docs.quantum-computing.ibm.com/errors"}]}\''
How can we reproduce the issue?
What should happen?
Any suggestions?
I made a workaround and I can submit a PR regarding this.:
The text was updated successfully, but these errors were encountered: