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

Clifford optimize needs documentation #2961

Open
dabacon opened this issue May 4, 2020 · 0 comments
Open

Clifford optimize needs documentation #2961

dabacon opened this issue May 4, 2020 · 0 comments
Labels
area/clifford-optimizer area/contrib area/transformers complexity/low introduces/modifies 1-2 concepts, should take 1-2 days max for an advanced contributor kind/docs Documentation related problems, ideas, requests skill-level/advanced One or more of the areas need a solid understanding. triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on
Milestone
2025-T6: Code hea...

Comments

@dabacon
Copy link
Collaborator

dabacon commented May 4, 2020

It is a custom optimization routine. Does not appear to be connected to the body of work on optimizing Clifford circuits (see for example https://arxiv.org/abs/quant-ph/0304125 and papers that cite that one)
@balopat balopat added area/clifford-optimizer area/contrib area/transformers kind/docs Documentation related problems, ideas, requests triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on complexity/low introduces/modifies 1-2 concepts, should take 1-2 days max for an advanced contributor skill-level/advanced One or more of the areas need a solid understanding. labels Sep 1, 2020
This was referenced Mar 12, 2022
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/clifford-optimizer area/contrib area/transformers complexity/low introduces/modifies 1-2 concepts, should take 1-2 days max for an advanced contributor kind/docs Documentation related problems, ideas, requests skill-level/advanced One or more of the areas need a solid understanding. triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on
Projects
Cirq 2025 roadmap
Status: No status
Milestone
2025-T6: Code health and project main...
Development

No branches or pull requests
4 participants
@dabacon @balopat @mhucka @MichaelBroughton