-
Notifications
You must be signed in to change notification settings - Fork 85
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
Generate Provider 0.8 and 0.9 docs #784
Conversation
|
||
Backend class interfacing with an IBM Quantum device. | ||
|
||
You can run experiments on a backend using the [`run()`](qiskit_ibm_provider.IBMBackend#run "qiskit_ibm_provider.IBMBackend.run") method. The [`run()`](qiskit_ibm_provider.IBMBackend#run "qiskit_ibm_provider.IBMBackend.run") method takes one or more [`QuantumCircuit`](/api/qiskit/qiskit.circuit.QuantumCircuit "(in Qiskit v0.45)") and returns an `IBMJob` instance that represents the submitted job. Each job has a unique job ID, which can later be used to retrieve the job. An example of this flow: | ||
You can run experiments on a backend using the [`run()`](#qiskit_ibm_provider.IBMBackend.run "qiskit_ibm_provider.IBMBackend.run") method. The [`run()`](#qiskit_ibm_provider.IBMBackend.run "qiskit_ibm_provider.IBMBackend.run") method takes one or more [`QuantumCircuit`](https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.QuantumCircuit "(in Qiskit v0.46)") and returns an `IBMJob` instance that represents the submitted job. Each job has a unique job ID, which can later be used to retrieve the job. An example of this flow: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this URL is no longer relative. I think it's because intersphinx now uses docs.quantum.ibm.com in Provider. #493 will fix this.
I don't think we should block this PR on #493. But I'll bump it in priority. Relative links are better because our link checker can check them much more quickly. The good news is that the platform at least doesn't add the arrow suggesting it's an external link; i.e. it detects it's an internal link.
1. Uploaded artifacts to Box and added to `api-html-artifacts.json` 2. `npm run make-historical -- -p qiskit-ibm-provider` 3. `npm run gen-api -- -p qiskit-ibm-provider -v 0.8.0 --historical` 4. `npm run gen-api -- -p qiskit-ibm-provider -v 0.9.0` This our first time having historical API docs for Provider, so it required changing our link checker to load Qiskit docs.
api-html-artifacts.json
npm run make-historical -- -p qiskit-ibm-provider
npm run gen-api -- -p qiskit-ibm-provider -v 0.8.0 --historical
npm run gen-api -- -p qiskit-ibm-provider -v 0.9.0
This our first time having historical API docs for Provider, so it required changing our link checker to load Qiskit docs.