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
Importing a module ideally would not log any messages.
Suggested solutions
The easiest option here would be to change the backend detection code to run when the list of backends is requested, rather when in the constructor - happy to put a PR together for that.
There was an alternative solution proposed in Qiskit/qiskit#7498 (comment) which suggested (if I understand correctly) removing the assembling of circuits in available_methods/available_devices and replacing it with some metadata on the binary.
The text was updated successfully, but these errors were encountered:
Instead of calling cpp_execute_qobj, calling cpp_execute_circuits will resolve this issue once #1717 is merged.
available_methods is constant for a binary. However, available_devices depends on environment: ["CPU"] or ["CPU", "GPU", "Thrust"]. But just for checking availability of GPU, calling CPU and GPU may be not-small overheads.
Informations
What is the current behavior?
Importing any qiskit.aer module will log several messages of the form:
Steps to reproduce the problem
Run the following Python program:
What is the expected behavior?
Importing a module ideally would not log any messages.
Suggested solutions
The easiest option here would be to change the backend detection code to run when the list of backends is requested, rather when in the constructor - happy to put a PR together for that.
There was an alternative solution proposed in Qiskit/qiskit#7498 (comment) which suggested (if I understand correctly) removing the assembling of circuits in
available_methods
/available_devices
and replacing it with some metadata on the binary.The text was updated successfully, but these errors were encountered: