forked from Qiskit/qiskit
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Write module-level
qiskit.circuit
documentation (Qiskit#11904)
* Write module-level `qiskit.circuit` documentation I was pretty surprised to see that we had very little written for our principal module, and the first entry in our API docs. This is a totally new set of documentation for the `qiskit.circuit` module, including discussion of what circuits are, what they represent in Qiskit, how all the different data elements fit together, and where to go for more information on things. This commit is intended to be followed by a later one that does a similar rewrite for the whole `QuantumCircuit` class, including structuring its references to all its attributes and methods, and adding a holistic view of how the methods fit together. This is why there are some (hidden to Sphinx) `TODO` comments scattered throughout this documentation. * Apply suggestions from Sebastian's review Co-authored-by: Sebastian Brandhofer <[email protected]> * Move larger classes to separate pages This moves the larger class definitions (basically those that actually have any public methods) to separate pages, at the request of the docs team. Much of this is intended to be temporary, and for most of these classes to be moved back inline once the IBM docs platform can better support that. * Fix docs build with autosummary * Switch "near time"/"runtime" terminology to "real time" This avoids overloading "runtime" with too many meanings, and appears to be more consistent with other messaging coming out of IBM Quantum. * Remove misleading 'bitwise' terminology --------- Co-authored-by: Sebastian Brandhofer <[email protected]>
- Loading branch information
1 parent
2cbbe2b
commit 99c0497
Showing
26 changed files
with
1,337 additions
and
392 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.