Consolidate two similar pages (get-qpu-information and qpu-information)#4313
Consolidate two similar pages (get-qpu-information and qpu-information)#4313
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
abbycross
changed the title
jyu00
left a comment
jyu00
left a comment
There was a problem hiding this comment.
Sorry if I reviewed too early... didn't realize it's still in draft!
…documentation into ajc/consolidate-qpu-info
|
One or more of the following people are relevant to this code:
|
docs/guides/qpu-information.ipynb
Outdated
| "source": [ | ||
| "## Static backend information\n", | ||
| "\n", | ||
| "Some information about a backend does not change regularly, such as its name, (version)(#qpu-versioning), the number of qubits it has, its processor type (the bird family name, which indicates the [topology](#coupling-map) and approximate qubit count), and the types of features it supports. This information is available as attributes of the `backend` object. For a full list of attributes, see the [`IBMBackend` API documentation](/docs/api/qiskit-ibm-runtime/ibm-backend). Find more information on versioning in the [QPU versioning](#qpu-versioning) section below.\n", |
There was a problem hiding this comment.
such as its name, (version)(#qpu-versioning),
Is this a typo?
| "</Tabs>\n", | ||
| "\n", | ||
| "<span id=\"native-gates\"></span>\n", | ||
| "### Table of supported instructions\n", |
There was a problem hiding this comment.
What you did is fine, but we can also consolidate a bit by putting both delay and measure_* in the Non-unitary instructions row.
| } | ||
| ], | ||
| "source": [ | ||
| "# calibration data with detailed properties of qubit 0\n", |
There was a problem hiding this comment.
Can we change this to something like
# calibration data with detailed properties of qubit 0, including its physical properties and some instruction properties (see the section below for more information)
Since the output show attributes like prob_meas0_prep1 that won't be explained until later.
| "frequency = qubit_props.get(\"frequency\", (None,))[0]\n", | ||
| "anharmonicity = qubit_props.get(\"anharmonicity\", (None,))[0]\n", |
There was a problem hiding this comment.
We should remove these 2 since they are only available on Eagles.
| } | ||
| ], | ||
| "source": [ | ||
| "# Retrieve qubit properties\n", |
There was a problem hiding this comment.
I feel this code block is a duplicate of the one above but better formatted. The one above shows a timestamp but doesn't explain what the timestamp is for. Maybe we can just keep this one?
| "\n", | ||
| "| | |\n", | ||
| "| --- | --- |\n", | ||
| "| **View with Qiskit** | `backend.target['<instruction>'][<qubit 1>, <qubit 2> ].duration`|\n", |
There was a problem hiding this comment.
| "| **View with Qiskit** | `backend.target['<instruction>'][<qubit 1>, <qubit 2> ].duration`|\n", | |
| "| **View with Qiskit** | `backend.target['<instruction>'][<qubit 1>, ]`|\n", |
RZ is a single qubit gate, and .duration reports just the duration, not error
| "| **View with Qiskit** | `backend.target['<instruction>'][<qubit 1>, <qubit 2> ].duration`|\n", | ||
| "| **View on IBM Quantum Platform** | Calibration section: Qubit dropdown menu |\n", | ||
| "\n", | ||
| "#### `readout_length`\n", |
There was a problem hiding this comment.
Why is readout length in `` ?
| "\n", | ||
| "| | |\n", | ||
| "| --- | --- |\n", | ||
| "| **View with Qiskit** | `backend.properties().readout_length(<qubit>)`|\n", |
There was a problem hiding this comment.
So, this is only for the measure instruction. To get the duration for measure_2 you need to follow the Single-qubit gate length code - i.e. backend.target['measure_2'][<qubit 1>, ].duration
| "\n", | ||
| "| | |\n", | ||
| "| --- | --- |\n", | ||
| "| **View with Qiskit** | Find the [CLOPS code](https://github.com/qiskit-community/qiskit-device-benchmarking/tree/main/qiskit_device_benchmarking/clops#readme) in the Qiskit Community GitHub |\n", |
There was a problem hiding this comment.
| "| **View with Qiskit** | Find the [CLOPS code](https://github.com/qiskit-community/qiskit-device-benchmarking/tree/main/qiskit_device_benchmarking/clops#readme) in the Qiskit Community GitHub |\n", | |
| "| **Calculate with Qiskit** | Find the [CLOPS code](https://github.com/qiskit-community/qiskit-device-benchmarking/tree/main/qiskit_device_benchmarking/clops#readme) in the Qiskit Community GitHub |\n", |
| "<Admonition type=\"tip\" title=\"Recommendations\">\n", | ||
| " - Try the [Grover's algorithm](/docs/tutorials/grovers-algorithm) tutorial.\n", |
There was a problem hiding this comment.
Having grovers here seems a bit out of place. How about
- Learn how to Build noise models to do noisy classical simulation.
- Review the Transpiler stages topic to learn about how the transpiler uses backend properties for circuit optimization.
3 participants
CC: @jyu00
Consolidate two files containing similar/overlapping content: Get backend information with Qiskit and QPU information.
@Eric-Arellano @frankharkins @arnaucasau FYI: when it is time to merge, can you please set up a redirect from
qpu-information.mdxtoget-qpu-information.ipynb?Closes #4249