Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove opflow dependency in EvolvedOperatorAnsatz #9516

Closed
Tracked by #9518
ElePT opened this issue Feb 2, 2023 · 0 comments · Fixed by #9537
Closed
Tracked by #9518

Remove opflow dependency in EvolvedOperatorAnsatz #9516

ElePT opened this issue Feb 2, 2023 · 0 comments · Fixed by #9537
Assignees
@Cryoris
Labels
type: feature request New feature or request
Milestone
0.24.0

Comments

@ElePT
Copy link
Contributor

ElePT commented Feb 2, 2023

What should we add?

The EvolvedOperatorAnsatz class still depends on opflow expectations, and is not compatible with the new primitive-based workflow. This WIP PR #7275 already proposes an alternative to replace EvolvedOperatorAnsatz with EvolutionGates, so it might be a good starting point to realize this task.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Cryoris Cryoris

Labels
type: feature request New feature or request
Projects
None yet
Milestone
0.24.0
Development

Successfully merging a pull request may close this issue.

Leverage EvolutionSynthesis in the EvolvedOperatorAnsatz Cryoris/qiskit-terra
2 participants
@Cryoris @ElePT