Allow Optimizers as input to VQEProgram
#290
Conversation
Cryoris
requested review from
manoelmarques,
mrossinek,
pbark,
stefan-woerner and
woodsp-ibm
as code owners
|
So this is a feature rather than any bug fix then. I see you put a high priority label on the issue which is why I am asking. As a feature this would go out in the next release unless somehow its creating critical problems/issues out there now. I assume you will be updating the optimization repo equivalently. If we need these to stay the same out there so users can use the one in Nature and/or the one in Optimization the same way then I guess things need to be coordinated/sorted out, since I presently would have expected a Nature release in advance of the next Optimization one - unless we start talking bug fix releases. |
|
It would be better to get this out before the next feature release, right, so it seems more like a bugfix 😉 I synced with @pbark and looks like we can do a minor/bugfix release soon. |
* allow Optimizers as optimizer inputs * Update releasenotes/notes/vqeprogram-optimizers-cd23307c10fcd15b.yaml Co-authored-by: Panagiotis Barkoutsos <pbarkoutsos@gmail.com> (cherry picked from commit e6a2dfd)
* allow Optimizers as optimizer inputs * Update releasenotes/notes/vqeprogram-optimizers-cd23307c10fcd15b.yaml Co-authored-by: Panagiotis Barkoutsos <pbarkoutsos@gmail.com> (cherry picked from commit e6a2dfd) Co-authored-by: Julien Gacon <jules.gacon@googlemail.com>
* allow Optimizers as optimizer inputs * Update releasenotes/notes/vqeprogram-optimizers-cd23307c10fcd15b.yaml Co-authored-by: Panagiotis Barkoutsos <pbarkoutsos@gmail.com>
Summary
Fixes #289.
Details and comments
Dictionaries are still supported since some tutorials first need to be updated to use optimizers.