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
The small code examples in the doc string of qiskit_algorithms/optimizers/spsa.py still show the old signature of optimizers in qiskit instead of the new scipy-style optimizers. This includes a method optimize that is now called minimize, returning point, value, niter instead of OptimizationResult objects, etc.
How can we reproduce the issue?
--
What should happen?
The code examples shout show the new way of using optimizers in qiskit.
Any suggestions?
No response
The text was updated successfully, but these errors were encountered:
Thanks for noticing and raising this issue. It is also using StateFn which was part of qiskit.opflow which was deprecated and will no longer be present in the upcoming Qiskit 1.0. The first part could be re-done showing it used with an Estimator. Though I do not know how much value there is in that given its usage is no different syntactically than any other optimizer in that regard.
Environment
What is happening?
The small code examples in the doc string of qiskit_algorithms/optimizers/spsa.py still show the old signature of optimizers in qiskit instead of the new scipy-style optimizers. This includes a method
optimize
that is now calledminimize
, returningpoint, value, niter
instead ofOptimizationResult
objects, etc.How can we reproduce the issue?
--
What should happen?
The code examples shout show the new way of using optimizers in qiskit.
Any suggestions?
No response
The text was updated successfully, but these errors were encountered: