We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I propose to add GHZ states as benchmarks. They are easy to encode and are a maximally entangled state.
They are present also in mitiq benchmarks, https://github.com/unitaryfund/mitiq/blob/main/mitiq/benchmarks/ghz_circuits.py and https://mitiq.readthedocs.io/en/stable/apidoc.html#module-mitiq.benchmarks.ghz_circuits
The text was updated successfully, but these errors were encountered:
https://www.linkedin.com/posts/jay-gambetta-a274753a_the-preparation-of-ghz-states-is-a-common-activity-7302459921470550016-kjGR
Sorry, something went wrong.
Note that the above uses a particular method to get those results. The GHZ state here https://github.com/unitaryfund/mitiq/blob/main/mitiq/benchmarks/ghz_circuits.py is also a less than ideal way to generate the state for everyone except perhaps IonQ, who can only run gates in serial.
No branches or pull requests
I propose to add GHZ states as benchmarks. They are easy to encode and are a maximally entangled state.
They are present also in mitiq benchmarks, https://github.com/unitaryfund/mitiq/blob/main/mitiq/benchmarks/ghz_circuits.py and https://mitiq.readthedocs.io/en/stable/apidoc.html#module-mitiq.benchmarks.ghz_circuits
The text was updated successfully, but these errors were encountered: