Skip to content

Create a Jupyter notebook with gates worked out explicitly #852

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

Closed
dabacon opened this issue Aug 10, 2018 · 6 comments
Closed

Create a Jupyter notebook with gates worked out explicitly #852

dabacon opened this issue Aug 10, 2018 · 6 comments
Assignees
Labels
area/docs area/examples area/gates triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on

Comments

@dabacon
Copy link
Collaborator

dabacon commented Aug 10, 2018

This would help clarify some of the "half angle" confusions.

@vtomole
Copy link
Collaborator

vtomole commented Nov 6, 2018

What's the update on this?

@vtomole
Copy link
Collaborator

vtomole commented Apr 24, 2019

We couldn't find this because Jupyter is misspelled (juptyer). @dabacon what's the context on this? Could be a two birds one stone with: #1564

@dabacon dabacon changed the title Create a juptyer notebook with gates worked out explicitly Create a Jupyter notebook with gates worked out explicitly May 1, 2020
@dabacon
Copy link
Collaborator Author

dabacon commented May 1, 2020

A possible documentation page to think about @karlunho a notebook or page with all of the gates (gate zoo)

@balopat balopat added area/examples area/gates kind/docs triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on labels Sep 22, 2020
@dabacon dabacon self-assigned this Apr 12, 2022
CirqBot pushed a commit that referenced this issue Apr 26, 2022
This PR updates the doc strings for single qubit gates.  These gates now all render correctly on quantumai.google.  

* This moves over to using LaTeX for the documentation. In some cases this makes the code doc string less readable, in some case it makes it is more readable.  It renders nicely on quantumai.google

This also starts #852 for single qubit gates. Adding two and higher qubit gates will come in a follow up PR assuming the pattern in this PR is good.
@MichaelBroughton
Copy link
Collaborator

Is this still in flight @dabacon ? Is this relevant : https://quantumai.google/cirq/gates ?

@dabacon
Copy link
Collaborator Author

dabacon commented May 10, 2022

Still in flight, doing two qubit gates next.

@dabacon
Copy link
Collaborator Author

dabacon commented May 12, 2022

Fixed in #5344

@dabacon dabacon closed this as completed May 12, 2022
rht pushed a commit to rht/Cirq that referenced this issue May 1, 2023
…ntumlib#5246)

This PR updates the doc strings for single qubit gates.  These gates now all render correctly on quantumai.google.  

* This moves over to using LaTeX for the documentation. In some cases this makes the code doc string less readable, in some case it makes it is more readable.  It renders nicely on quantumai.google

This also starts quantumlib#852 for single qubit gates. Adding two and higher qubit gates will come in a follow up PR assuming the pattern in this PR is good.
harry-phasecraft pushed a commit to PhaseCraft/Cirq that referenced this issue Oct 31, 2024
…ntumlib#5246)

This PR updates the doc strings for single qubit gates.  These gates now all render correctly on quantumai.google.  

* This moves over to using LaTeX for the documentation. In some cases this makes the code doc string less readable, in some case it makes it is more readable.  It renders nicely on quantumai.google

This also starts quantumlib#852 for single qubit gates. Adding two and higher qubit gates will come in a follow up PR assuming the pattern in this PR is good.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs area/examples area/gates triage/accepted A consensus emerged that this bug report, feature request, or other action should be worked on
Projects
None yet
Development

No branches or pull requests

6 participants