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.

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

Support a wider variety of Qiskit gates for automatic, optimal decomposition #288

Closed
11 tasks done
caleb-johnson opened this issue Jun 26, 2023 · 2 comments · Fixed by #302
Closed
11 tasks done

Support a wider variety of Qiskit gates for automatic, optimal decomposition #288

caleb-johnson opened this issue Jun 26, 2023 · 2 comments · Fixed by #302
Labels
cutting QPD-based circuit cutting code enhancement New feature or request

Comments

@caleb-johnson
Copy link
Collaborator

caleb-johnson commented Jun 26, 2023

@garrison
Copy link
Member

garrison commented Jun 26, 2023

Thanks, I hadn't thought of this yet. I think it would be relatively simple to add support for ECRGate. We could add support for RZXGate, too, while we are at it.

@garrison garrison added enhancement New feature or request cutting QPD-based circuit cutting code labels Jun 26, 2023
@garrison
Copy link
Member

garrison commented Jun 26, 2023

Here's a list of gates that I believe we could support pretty easily: [the list is now in the top post.]

Even if we eventually implement general unitaries (#186), having more gates may be useful once we figure out a way to implement adjusting parameters in reconstruction (#256).

@caleb-johnson caleb-johnson changed the title Understand whether we should handle ECR gates directly Support a wider variety of Qiskit gates for automatic, optimal decomposition Jun 27, 2023
@garrison garrison linked a pull request Jul 24, 2023 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cutting QPD-based circuit cutting code enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants