diff --git a/.gitignore b/.gitignore index 3105d955d78..59fabd792d2 100644 --- a/.gitignore +++ b/.gitignore @@ -21,3 +21,4 @@ poetry.lock Untitled*.ipynb *.tar *.tar.gz +test.ipynb diff --git a/docs/guides/_toc.json b/docs/guides/_toc.json index ffb8fbf5105..7b344cc8c1a 100644 --- a/docs/guides/_toc.json +++ b/docs/guides/_toc.json @@ -525,13 +525,9 @@ "url": "/docs/guides/processor-types" }, { - "title": "QPU information", + "title": "View backend details", "url": "/docs/guides/qpu-information" }, - { - "title": "Get backend information with Qiskit", - "url": "/docs/guides/get-qpu-information" - }, { "title": "Monitoring, calibrations, and benchmarking", "url": "/docs/guides/calibration-jobs" @@ -920,4 +916,4 @@ ] } ] -} +} \ No newline at end of file diff --git a/docs/guides/calibration-jobs.mdx b/docs/guides/calibration-jobs.mdx index db0e080bd62..0270a072511 100644 --- a/docs/guides/calibration-jobs.mdx +++ b/docs/guides/calibration-jobs.mdx @@ -71,13 +71,12 @@ Daily benchmarking gives a comprehensive view of quantum computer performance an ### Single-qubit performance * [Randomized benchmarking](/docs/guides/qpu-information#median-sx-error) (RB) in batched groups -* Coherence times for [$T_1$](/docs/guides/qpu-information#median-t1-relaxation-time) and [$T_2$](/docs/guides/qpu-information#median-t2-dephasing-time) +* Coherence times for [$T_1$](/docs/guides/qpu-information#t1) and [$T_2$](/docs/guides/qpu-information#t2) * [Measurement-fidelity metrics](/docs/guides/qpu-information#median-readout-error) ### Two-qubit performance -* [CZ and RZZ fractional gate EPG (Heron), ECR (Eagle)](/docs/guides/qpu-information#median-2q-error-heron-cz-eagle-ecr -) as measured by RB on those gates +* [CZ and RZZ fractional gate EPG (Heron), ECR (Eagle)](/docs/guides/qpu-information#2q-error-median) as measured by RB on those gates ### System-level metrics diff --git a/docs/guides/get-qpu-information.ipynb b/docs/guides/get-qpu-information.ipynb deleted file mode 100644 index d8a68fe3bb7..00000000000 --- a/docs/guides/get-qpu-information.ipynb +++ /dev/null @@ -1,522 +0,0 @@ -{ - "cells": [ - { - "cell_type": "markdown", - "id": "cbac187d-c590-404f-b451-8f4ec2292278", - "metadata": {}, - "source": [ - "---\n", - "title: Get backend information with Qiskit\n", - "description: Find and filter available backends, get configuration and calibration data programmatically.\n", - "---\n", - "\n", - "\n", - "# Get backend information with Qiskit" - ] - }, - { - "cell_type": "markdown", - "id": "b47b9112-316b-46fd-9b23-e3a8245428fb", - "metadata": { - "tags": [ - "version-info" - ] - }, - "source": [ - "{/*\n", - " DO NOT EDIT THIS CELL!!!\n", - " This cell's content is generated automatically by a script. Anything you add\n", - " here will be removed next time the notebook is run. To add new content, create\n", - " a new cell before or after this one.\n", - "*/}\n", - "\n", - "\n", - "\n", - "\n", - "The code on this page was developed using the following requirements.\n", - "We recommend using these versions or newer.\n", - "\n", - "```\n", - "qiskit-ibm-runtime~=0.43.1\n", - "```\n", - "\n", - "" - ] - }, - { - "cell_type": "markdown", - "id": "c05364ae-48e2-439e-8074-3a053731c744", - "metadata": {}, - "source": [ - "This page explains how to use Qiskit to find information about your available backends." - ] - }, - { - "cell_type": "markdown", - "id": "c9aec913-438d-4849-9ee1-ca531264b50e", - "metadata": {}, - "source": [ - "## List backends\n", - "\n", - "To view the backends you have access to, you can either view a list on the [Compute resources page,](https://quantum.cloud.ibm.com/computers) or you can use the [`QiskitRuntimeService.backends()`](../api/qiskit-ibm-runtime/qiskit-runtime-service#backends) method. This method returns a list of [`IBMBackend`](../api/qiskit-ibm-runtime/ibm-backend) instances:\n", - "\n", - "\n", - "- If you are logged in to a specific instance or region, or if you initialized the service with a specific instance or region by using `QiskitRuntimeService()`, only the backends available to you on that instance or region are returned. Otherwise, all backends available to you on any instance and in any region are returned.\n", - "- The list of backends returned might not be the same as those shown on the IBM Quantum Platform [Compute resources](https://quantum.cloud.ibm.com/computers) page. The list on the Compute resources page is always filtered by the region selected at the top of the page.\n", - "" - ] - }, - { - "cell_type": "markdown", - "id": "61cf3942-2070-4917-90ab-44afdcbde92f", - "metadata": {}, - "source": [ - "To run the following code, be sure you have already authenticated to the service. See [Set up your IBM Cloud account](/docs/guides/cloud-setup) for more details." - ] - }, - { - "cell_type": "code", - "execution_count": 1, - "id": "b169fd5c-5132-47ed-9baf-eecd37f8f668", - "metadata": {}, - "outputs": [ - { - "data": { - "text/plain": [ - "[,\n", - " ,\n", - " ,\n", - " ,\n", - " ,\n", - " ,\n", - " ]" - ] - }, - "execution_count": 1, - "metadata": {}, - "output_type": "execute_result" - } - ], - "source": [ - "# Initialize your account\n", - "from qiskit_ibm_runtime import QiskitRuntimeService\n", - "\n", - "service = QiskitRuntimeService()\n", - "\n", - "service.backends()" - ] - }, - { - "cell_type": "markdown", - "id": "546f7270-66b9-43eb-a445-731ffa06a33f", - "metadata": {}, - "source": [ - "The [`QiskitRuntimeService.backend()`](../api/qiskit-ibm-runtime/qiskit-runtime-service#backend) method (note that this is singular: *backend*) takes the name of the backend as the input parameter and returns an [`IBMBackend`](../api/qiskit-ibm-runtime/ibm-backend) instance representing that particular backend:" - ] - }, - { - "cell_type": "code", - "execution_count": 2, - "id": "424a7f11-6fd1-4599-a6e7-6fa722234b9a", - "metadata": {}, - "outputs": [ - { - "data": { - "text/plain": [ - "" - ] - }, - "execution_count": 2, - "metadata": {}, - "output_type": "execute_result" - } - ], - "source": [ - "service.backend(\"ibm_fez\")" - ] - }, - { - "cell_type": "markdown", - "id": "2a9fa4a7-4f2a-47ef-be70-b1e100b20d2a", - "metadata": {}, - "source": [ - "## Filter backends\n", - "\n", - "You can also filter the available backends by their properties. For more general filters, set the `filters` argument to a function that accepts a backend object and returns `True` if it meets your criteria. Refer to the [API documentation](../api/qiskit-ibm-runtime/qiskit-runtime-service#backends) for more details.\n", - "\n", - "The following code returns only backends that fit these criteria and are available to you _on your currently selected instance_:\n", - "\n", - "* Are real quantum devices (`simulator=False`)\n", - "* Are currently operational (`operational=True`)\n", - "* Have at least 5 qubits (`min_num_qubits=5`)" - ] - }, - { - "cell_type": "code", - "execution_count": 3, - "id": "cc7b0879-feaa-42da-955a-775b456198a1", - "metadata": {}, - "outputs": [ - { - "data": { - "text/plain": [ - "[,\n", - " ,\n", - " ,\n", - " ,\n", - " ,\n", - " ,\n", - " ]" - ] - }, - "execution_count": 3, - "metadata": {}, - "output_type": "execute_result" - } - ], - "source": [ - "# Optionally pass in an instance, region, or both, to\n", - "# further filter the backends.\n", - "service = QiskitRuntimeService()\n", - "\n", - "service.backends(simulator=False, operational=True, min_num_qubits=5)" - ] - }, - { - "cell_type": "markdown", - "id": "37fbdbc1-9f24-491b-8352-e56d767a5acd", - "metadata": {}, - "source": [ - "Use these keyword arguments to filter by any attribute in backend configuration or status. A similar method is [`QiskitRuntimeService.least_busy()`](../api/qiskit-ibm-runtime/qiskit-runtime-service#least_busy), which takes the same filters as `backends()` but returns the backend that matches the filters and has the least number of jobs pending in the queue:" - ] - }, - { - "cell_type": "code", - "execution_count": 4, - "id": "846dfe4b-def3-49c1-9d2a-906fd2dc55de", - "metadata": {}, - "outputs": [ - { - "data": { - "text/plain": [ - "" - ] - }, - "execution_count": 4, - "metadata": {}, - "output_type": "execute_result" - } - ], - "source": [ - "service.least_busy(operational=True, min_num_qubits=5)" - ] - }, - { - "cell_type": "markdown", - "id": "3b34bb71-b8cf-415f-9901-a5970997ee15", - "metadata": {}, - "source": [ - "## Static backend information\n", - "\n", - "Some information about a backend does not change regularly, such as its name, version, the number of qubits it has, and the types of features it supports. This information is available as attributes of the `backend` object.\n", - "\n", - "The following cell builds a description of a backend." - ] - }, - { - "cell_type": "code", - "execution_count": 5, - "id": "8d070b69-1b6d-4faa-9a4a-d12aba47d0b7", - "metadata": {}, - "outputs": [ - { - "name": "stdout", - "output_type": "stream", - "text": [ - "Name: ibm_fez\n", - "Version: 2\n", - "No. of qubits: 156\n", - "\n" - ] - } - ], - "source": [ - "backend = service.backend(\"ibm_fez\")\n", - "\n", - "print(\n", - " f\"Name: {backend.name}\\n\"\n", - " f\"Version: {backend.version}\\n\"\n", - " f\"No. of qubits: {backend.num_qubits}\\n\"\n", - ")" - ] - }, - { - "cell_type": "markdown", - "id": "1fc62b0b-1975-4bdc-a968-fa5bff92a893", - "metadata": {}, - "source": [ - "For a full list of attributes, see the [`IBMBackend` API documentation](/docs/api/qiskit-ibm-runtime/ibm-backend)." - ] - }, - { - "cell_type": "markdown", - "id": "6a055938-0a1d-46ef-ae9c-60a7960d6d73", - "metadata": {}, - "source": [ - "## Native gates and operations\n", - "\n", - "Each [processor family](/docs/guides/processor-types) has a native gate set. By default, the QPUs in each family only support running the gates and operations in the native gate set. Thus, every gate in the circuit must be translated (by the transpiler) to the elements of this set.\n", - "\n", - "You can view the native gates and operations for a QPU either [with Qiskit](#native-gates-with-qiskit), or on the IBM Quantum® Platform [Compute resources page](/docs/guides/qpu-information#native-gates-on-platform).\n", - "\n", - "\n", - "```python\n", - "\n", - "from qiskit_ibm_runtime import QiskitRuntimeService\n", - "\n", - "service = QiskitRuntimeService()\n", - "\n", - "for backend in service.backends():\n", - " config = backend.configuration()\n", - " if \"simulator\" in config.backend_name:\n", - " continue\n", - " print(f\"Backend: {config.backend_name}\")\n", - " print(f\" Processor type: {config.processor_type}\")\n", - " print(f\" Supported instructions:\")\n", - " for instruction in config.supported_instructions:\n", - " print(f\" {instruction}\")\n", - " print()\n", - "```" - ] - }, - { - "cell_type": "markdown", - "id": "48cf020c-24eb-49dd-a417-7196d036b0e8", - "metadata": {}, - "source": [ - "## Dynamic backend information\n", - "\n", - "Backends can also have properties that change whenever the backed is calibrated, such as qubit frequency and operation error rates. Backends are usually calibrated every 24 hours, and their properties update after the calibration sequence completes. These properties can be used when optimizing quantum circuits or to construct noise models for a classical simulator.\n", - "\n", - "\n", - "### Qubit properties\n", - "\n", - "\n", - "The `backend.properties().qubit_property()` returns information about the qubits' physical attributes. It contains a dictionary of various properties of the qubit, each paired with its value and the timestamp of the last calibration.\n", - "\n", - "- `T1 (Relaxation Time)`: The T1 time represents the average duration a qubit remains in its excited state $|1\\rangle$ before decaying to its ground state $|0\\rangle$ due to energy relaxation. This parameter is used to characterize the qubit's energy relaxation behavior, and is expressed in units of seconds (s).\n", - "\n", - "- `T2 (Dephasing Time)`: The T2 time denotes the timescale over which a qubit maintains phase coherence of a superposition between the $|0\\rangle$ and $|1\\rangle$ states. It accounts for both energy relaxation and pure dephasing processes, providing insight into the qubit's coherence properties.\n", - "\n", - "- `frequency`: This parameter specifies the resonant frequency of the qubit, indicating the energy difference between the $|0\\rangle$ and $|1\\rangle$ states, expressed in hertz (Hz).\n", - "\n", - "- `anharmonicity`: Anharmonicity is the difference in energy between the first and second excited states of the qubit, also expressed in hertz (Hz).\n", - "\n", - "- `readout_error`: The readout error quantifies the average probability of incorrectly measuring a qubit's state. It is commonly calculated as the mean of prob_meas0_prep1 and prob_meas1_prep0, providing a single metric for measurement fidelity.\n", - "\n", - "- `prob_meas0_prep1`: This parameter indicates the probability of measuring a qubit in the 0 state when it was intended to be prepared in the $|1\\rangle$ state, denoted as $P(0 | 1)$. It reflects errors in state preparation and measurement (SPAM), particularly measurement errors in superconducting qubits.\n", - "\n", - "- `prob_meas1_prep0`: Similarly, this parameter represents the probability of measuring a qubit in the 1 state when it was intended to be prepared in the $|0\\rangle$ state, denoted as $P(1 | 0)$. Like prob_meas0_prep1, it reflects SPAM errors, with measurement errors being the predominant contributor in superconducting qubits.\n", - "\n", - "- `readout_length`: The readout_length specifies the duration of the readout operation for a qubit. It measures the time from the initiation of the measurement pulse to the completion of signal digitization, after which the system is ready for the next operation. Understanding this parameter is crucial for optimizing circuit execution, especially when incorporating mid-circuit measurements." - ] - }, - { - "cell_type": "code", - "execution_count": 6, - "id": "74b54d1b-7db8-4879-b51f-d307f023c535", - "metadata": {}, - "outputs": [ - { - "data": { - "text/plain": [ - "QubitProperties(t1=0.0001741868812945201, t2=0.00019188671049850405, frequency=None)" - ] - }, - "execution_count": 6, - "metadata": {}, - "output_type": "execute_result" - } - ], - "source": [ - "# fundamental physical properties of qubit 1\n", - "backend.qubit_properties(1)" - ] - }, - { - "cell_type": "code", - "execution_count": 7, - "id": "cdca7a53-9101-48f1-bddc-48c393b56b85", - "metadata": {}, - "outputs": [ - { - "data": { - "text/plain": [ - "{'T1': (5.183159049067906e-05,\n", - " datetime.datetime(2026, 3, 1, 4, 46, 55, tzinfo=tzlocal())),\n", - " 'T2': (4.7341240665109036e-05,\n", - " datetime.datetime(2026, 3, 1, 4, 47, 32, tzinfo=tzlocal())),\n", - " 'readout_error': (0.0169677734375,\n", - " datetime.datetime(2026, 3, 1, 0, 56, 40, tzinfo=tzlocal())),\n", - " 'prob_meas0_prep1': (0.029296875,\n", - " datetime.datetime(2026, 3, 1, 0, 56, 40, tzinfo=tzlocal())),\n", - " 'prob_meas1_prep0': (0.004638671875,\n", - " datetime.datetime(2026, 3, 1, 0, 56, 40, tzinfo=tzlocal())),\n", - " 'readout_length': (1.56e-06,\n", - " datetime.datetime(2026, 3, 1, 0, 56, 40, tzinfo=tzlocal()))}" - ] - }, - "execution_count": 7, - "metadata": {}, - "output_type": "execute_result" - } - ], - "source": [ - "# calibration data with detailed properties of qubit 0\n", - "backend.properties().qubit_property(0)" - ] - }, - { - "cell_type": "code", - "execution_count": 8, - "id": "1379efb5-359a-4246-9603-fa5d007f9f8a", - "metadata": {}, - "outputs": [ - { - "name": "stdout", - "output_type": "stream", - "text": [ - "Qubit 126 Properties:\n", - " T1: 0.0001071144943420668 seconds\n", - " T2: 7.209579718640725e-05 seconds\n", - " Frequency: None Hz\n", - " Anharmonicity: None Hz\n", - " Readout Error: 0.0067138671875\n", - " P(0 | 1): 0.009521484375\n", - " P(1 | 0): 0.00390625\n", - " Readout Length: 1.56e-06 seconds\n" - ] - } - ], - "source": [ - "# Retrieve qubit properties\n", - "qubit_index = 126 # Replace with your qubit index\n", - "qubit_props = backend.properties().qubit_property(qubit_index)\n", - "\n", - "# Access specific properties\n", - "t1 = qubit_props.get(\"T1\", (None,))[0]\n", - "t2 = qubit_props.get(\"T2\", (None,))[0]\n", - "frequency = qubit_props.get(\"frequency\", (None,))[0]\n", - "anharmonicity = qubit_props.get(\"anharmonicity\", (None,))[0]\n", - "readout_error = qubit_props.get(\"readout_error\", (None,))[0]\n", - "prob_meas0_prep1 = qubit_props.get(\"prob_meas0_prep1\", (None,))[0]\n", - "prob_meas1_prep0 = qubit_props.get(\"prob_meas1_prep0\", (None,))[0]\n", - "readout_length = qubit_props.get(\"readout_length\", (None,))[0]\n", - "\n", - "print(f\"Qubit {qubit_index} Properties:\")\n", - "print(f\" T1: {t1} seconds\")\n", - "print(f\" T2: {t2} seconds\")\n", - "print(f\" Frequency: {frequency} Hz\")\n", - "print(f\" Anharmonicity: {anharmonicity} Hz\")\n", - "print(f\" Readout Error: {readout_error}\")\n", - "print(f\" P(0 | 1): {prob_meas0_prep1}\")\n", - "print(f\" P(1 | 0): {prob_meas1_prep0}\")\n", - "print(f\" Readout Length: {readout_length} seconds\")" - ] - }, - { - "cell_type": "markdown", - "id": "67525443-070e-4798-99b3-72a599bf96c8", - "metadata": {}, - "source": [ - "### Instruction properties\n", - "\n", - "The `backend.target` attribute is a `qiskit.transpiler.Target` object: an object that contains all the information needed to transpile a circuit for that backend. This includes instruction errors and durations. For example, the following cell gets the properties for a [`cz` gate](/docs/api/qiskit/qiskit.circuit.library.CZGate) acting between qubits 1 and 0." - ] - }, - { - "cell_type": "code", - "execution_count": 9, - "id": "64fc70f8-d848-45f2-aa25-9af10c315e1b", - "metadata": {}, - "outputs": [ - { - "data": { - "text/plain": [ - "InstructionProperties(duration=6.8e-08, error=0.007490502086578504)" - ] - }, - "execution_count": 9, - "metadata": {}, - "output_type": "execute_result" - } - ], - "source": [ - "backend.target[\"cz\"][(1, 0)]" - ] - }, - { - "cell_type": "markdown", - "id": "f89c0fb8-7fe0-46fc-8f8b-fed5b4aba8b7", - "metadata": {}, - "source": [ - "The following cell shows the properties for a measurement operation (including the readout error) on qubit 0." - ] - }, - { - "cell_type": "code", - "execution_count": 10, - "id": "412fec92-7a4b-41ff-b278-48e1bbcdaf3f", - "metadata": {}, - "outputs": [ - { - "data": { - "text/plain": [ - "InstructionProperties(duration=1.56e-06, error=0.0169677734375)" - ] - }, - "execution_count": 10, - "metadata": {}, - "output_type": "execute_result" - } - ], - "source": [ - "backend.target[\"measure\"][(0,)]" - ] - }, - { - "cell_type": "markdown", - "id": "89918e29-ee80-4c5e-9d25-c9331fa2f27e", - "metadata": {}, - "source": [ - "## Next steps\n", - "\n", - "\n", - " - Try the [Grover's algorithm](/docs/tutorials/grovers-algorithm) tutorial.\n", - " - Review the [QiskitRuntime backend API](/docs/api/qiskit-ibm-runtime/qiskit-runtime-service#backend) reference.\n", - "" - ] - } - ], - "metadata": { - "kernelspec": { - "display_name": "Python 3", - "language": "python", - "name": "python3" - }, - "language_info": { - "codemirror_mode": { - "name": "ipython", - "version": 3 - }, - "file_extension": ".py", - "mimetype": "text/x-python", - "name": "python", - "nbconvert_exporter": "python", - "pygments_lexer": "ipython3", - "version": "3" - } - }, - "nbformat": 4, - "nbformat_minor": 4 -} diff --git a/docs/guides/processor-types.mdx b/docs/guides/processor-types.mdx index 4276a79e3e2..82c7a46906c 100644 --- a/docs/guides/processor-types.mdx +++ b/docs/guides/processor-types.mdx @@ -8,8 +8,8 @@ description: Information on IBM Quantum hardware and features of different proce Processor types are named for the general technology qualities that go into builds, consisting of the family and revision. Family (for example, Heron) refers to the size and scale of circuits possible on the chip. This is primarily determined by the number of qubits and the connectivity graph. Revisions (for example, r3) are design variants within a given family, often leading to performance improvements or tradeoffs. - -To find the native gates and operations of a backend, use [this code](/docs/guides/get-qpu-information#native-gates-with-qiskit). You can see all native gates and operations in [this table](/docs/guides/qpu-information#native-gates). + +To find the supported instruction set for a backend, use [this code](/docs/guides/qpu-information#native-gates-ops). You can see all supported instructions in [this table](/docs/guides/qpu-information#native-gates). As new processor families are added, older families are retired. See the [Retired processor families](retired-qpus#families) section to learn more. diff --git a/docs/guides/qpu-information.ipynb b/docs/guides/qpu-information.ipynb new file mode 100644 index 00000000000..7dd1a365e5c --- /dev/null +++ b/docs/guides/qpu-information.ipynb @@ -0,0 +1,1092 @@ +{ + "cells": [ + { + "cell_type": "markdown", + "id": "c8e557e7-e1f9-4429-80ad-2907871c704d", + "metadata": {}, + "source": [ + "---\n", + "title: View backend details\n", + "description: List and filter available backends, and find QPU details such as configuration and calibration data.\n", + "---\n", + "\n", + "# View backend details" + ] + }, + { + "cell_type": "markdown", + "id": "bb84ab8e-6db9-45d6-bb59-2f06f38d9965", + "metadata": { + "tags": [ + "version-info" + ] + }, + "source": [ + "
\n", + "Package versions\n", + "\n", + "The code on this page was developed using the following requirements.\n", + "We recommend using these versions or newer.\n", + "\n", + "```\n", + "qiskit-ibm-runtime~=0.43.1\n", + "```\n", + "
" + ] + }, + { + "cell_type": "markdown", + "id": "d76db591-d53c-4753-ab4f-8d6e80bbc39e", + "metadata": {}, + "source": [ + "This page explains how to find information about your available backends." + ] + }, + { + "cell_type": "markdown", + "id": "1215b9ee-c32f-42db-a1e0-24d62175ab88", + "metadata": {}, + "source": [ + "## List or filter backends\n", + "\n", + "\n", + "### List backends available to you\n", + "\n", + "You can use either Qiskit or IBM Quantum Platform to view a list of backends available to you, or to search for a particular backend.\n", + "\n", + "\n", + " QPUs hosted on IBM Cloud® have names that begin with `ibm_*`. All QPUs are given a city name - for example, `ibm_kingston`. This name does not indicate where the actual QPU is hosted.\n", + "\n", + "\n", + "\n", + " \n", + " Use the [`QiskitRuntimeService.backends()`](/docs/api/qiskit-ibm-runtime/qiskit-runtime-service#backends) method, as shown in the next code block. This method returns a list of [`IBMBackend`](/docs/api/qiskit-ibm-runtime/ibm-backend) instances.\n", + "\n", + " To run the following code, be sure you have already authenticated to the service. See [Set up your IBM Cloud account](/docs/guides/cloud-setup) for more details.\n", + "\n", + " \n", + "\n", + " To search for a specific backend, use the [`QiskitRuntimeService.backend()`](/docs/api/qiskit-ibm-runtime/qiskit-runtime-service#backend) method (note that this is singular: *backend*), which takes the name of the backend as the input parameter and returns an [`IBMBackend`](/docs/api/qiskit-ibm-runtime/ibm-backend) instance representing that particular backend:\n", + "\n", + " \n", + " \n", + " \n", + " To view the backends you have access to, navigate to the list of backends on the [Compute resources page](https://quantum.cloud.ibm.com/computers) (note that your selected region might impact the QPUs listed). Click the filter icon and choose either \"All my instances\" or a specific instance name to see the available QPUs.\n", + " \n", + "" + ] + }, + { + "cell_type": "code", + "execution_count": null, + "id": "068f58ca-bff4-4138-8b75-b6a67e1e9e37", + "metadata": { + "tags": [ + "id-initialize" + ] + }, + "outputs": [ + { + "data": { + "text/plain": [ + "[,\n", + " ,\n", + " ]" + ] + }, + "execution_count": 1, + "metadata": {}, + "output_type": "execute_result" + } + ], + "source": [ + "# Initialize your account\n", + "from qiskit_ibm_runtime import QiskitRuntimeService\n", + "\n", + "service = QiskitRuntimeService()\n", + "\n", + "service.backends()" + ] + }, + { + "cell_type": "code", + "execution_count": 2, + "id": "0fc28230-3036-44ea-b933-8a9dda548b38", + "metadata": { + "tags": [ + "id-search" + ] + }, + "outputs": [ + { + "data": { + "text/plain": [ + "" + ] + }, + "execution_count": 2, + "metadata": {}, + "output_type": "execute_result" + } + ], + "source": [ + "service.backend(\"ibm_fez\")" + ] + }, + { + "cell_type": "code", + "execution_count": null, + "id": "3a28c031-e306-4cd2-aacb-f007b564ce96", + "metadata": { + "tags": [ + "id-filter" + ] + }, + "outputs": [ + { + "data": { + "text/plain": [ + "[,\n", + " ,\n", + " ]" + ] + }, + "execution_count": 3, + "metadata": {}, + "output_type": "execute_result" + } + ], + "source": [ + "# Optionally pass in an instance, region, or both, to\n", + "# further filter the backends.\n", + "service = QiskitRuntimeService()\n", + "\n", + "service.backends(simulator=False, operational=True, min_num_qubits=100)" + ] + }, + { + "cell_type": "markdown", + "id": "aefe61eb-27fd-4689-b16e-458a9681c066", + "metadata": {}, + "source": [ + "\n", + " If you are logged in to a specific instance or region, or if you initialized the service with a specific instance or region by using `QiskitRuntimeService()`, only the backends available to you on that instance or region are returned.\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "e6d4dafc-33f1-4010-a8fa-33bf37e7f98f", + "metadata": {}, + "source": [ + "### Filter backends\n", + "\n", + "\n", + "\n", + " \n", + " You can filter the available backends by their [configuration](/docs/api/qiskit-ibm-runtime/models-backend-configuration) or [status](/docs/api/qiskit-ibm-runtime/models-backend-status). For more general filters, set the `filters` argument to a function that accepts a backend object and returns `True` if it meets your criteria. Refer to the [API documentation](/docs/api/qiskit-ibm-runtime/qiskit-runtime-service#backends) for more details.\n", + "\n", + " The following code returns only backends that fit these criteria and are available to you _on your currently selected instance_:\n", + "\n", + " * Are real quantum devices (`simulator=False`)\n", + " * Are currently operational (`operational=True`)\n", + " * Have at least a hundred qubits (`min_num_qubits=100`)\n", + "\n", + " \n", + "\n", + " A similar method is [`QiskitRuntimeService.least_busy()`](/docs/api/qiskit-ibm-runtime/qiskit-runtime-service#least_busy), which takes the same filters as `backends()` but returns the backend that matches the filters and has the least number of jobs pending in the queue:\n", + "\n", + " \n", + "\n", + " \n", + " \n", + " To view the backends you have access to, view the table on the [Compute resources page](https://quantum.cloud.ibm.com/computers). Click the filter icon to see filter options. You can filter by processor type and status. Note also that you can sort the table by any column by hovering over a column title, and then clicking the arrows that appear.\n", + " \n", + "" + ] + }, + { + "cell_type": "code", + "execution_count": null, + "id": "7493d247-ade9-4dd2-8bdf-11e332bd6939", + "metadata": { + "tags": [ + "id-least-jobs" + ] + }, + "outputs": [ + { + "data": { + "text/plain": [ + "" + ] + }, + "execution_count": 4, + "metadata": {}, + "output_type": "execute_result" + } + ], + "source": [ + "service.least_busy(operational=True, min_num_qubits=100)" + ] + }, + { + "cell_type": "markdown", + "id": "1a0c9cbe-48e6-499e-bfb2-ed8bbdbeb38e", + "metadata": {}, + "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", + "\n", + "A backend's region (the location of the data center where your data and experiments will be hosted and processed) is listed in its detailed information card on the [Compute resources](https://quantum.cloud.ibm.com/computers) page on IBM Quantum Platform.\n", + "\n", + "\n", + " \n", + "\n", + " \n", + "\n", + " \n", + " \n", + "\n", + " Navigate to the [Compute resources](https://quantum.cloud.ibm.com/computers) page to view a table of all QPUs, then click the name of any QPU to open its detailed information card. Find backend information under the Details section of the card.\n", + "\n", + " \n", + "" + ] + }, + { + "cell_type": "code", + "execution_count": 4, + "id": "c15c53ef-301e-47b6-9931-bb5ae1f200dd", + "metadata": { + "tags": [ + "id-version" + ] + }, + "outputs": [ + { + "name": "stdout", + "output_type": "stream", + "text": [ + "Name: ibm_fez\n", + "Version: 1.3.37\n", + "No. of qubits: 156\n", + "Processor type: {'family': 'Heron', 'revision': '2'}\n", + "\n" + ] + } + ], + "source": [ + "backend = service.backend(\"ibm_fez\")\n", + "\n", + "print(\n", + " f\"Name: {backend.name}\\n\"\n", + " f\"Version: {backend.backend_version}\\n\"\n", + " f\"No. of qubits: {backend.num_qubits}\\n\"\n", + " f\"Processor type: {backend.processor_type}\\n\"\n", + ")" + ] + }, + { + "cell_type": "markdown", + "id": "99f2db6d-9d77-4330-9e3c-293153cd2f80", + "metadata": {}, + "source": [ + "### QPU versioning\n", + "\n", + "Each QPU has a version number in the form X.Y.Z (major.minor.revision). A circuit compiled for a given version number is guaranteed to run on that QPU. If the revision number changes, the circuit will continue to run. If the major or minor number changes, the circuit is not guaranteed to run, although it may do so.\n", + "\n", + "The revision version number will increment for fixes that do not break the existing compiled circuit.\n", + "\n", + "The code example earlier in [this section](#static-backend-information) demonstrates how to find a backend's version. On IBM Quantum Platform, you can view the version on a QPU's detailed information card (click the QPU's name on the [Compute resources](https://quantum.cloud.ibm.com/computers) table to open the card).\n", + "\n", + "The conditions under which a version or revision number can change are listed in the following table.\n", + "\n", + "| Major version | Minor version | Revision version |\n", + "| --- | --- | --- |\n", + "|Sample changes| Warmup / cool-down cycles | QPU software updates |\n", + "|Major changes to the control electronics| Swapping out some electronics, if the replacement appreciably affects operation| Manual calibrations to improve fidelities |\n", + "|Moving the QPU to a new location, if significant behavior changes result| Dropping a gate for some duration of time due to calibration issues, and corrections cannot readily be done in software| Small electronics changes that don’t affect operation |\n", + "| |Changing the direction of a CNOT gate | |" + ] + }, + { + "cell_type": "markdown", + "id": "42d83190-198e-4696-acb6-9cc5e57c49ab", + "metadata": {}, + "source": [ + "\n", + "### Supported instructions\n", + "\n", + "Each [processor family](/docs/guides/processor-types) natively supports a limited set of instructions. This set includes single- and two-qubit gates, as well as non-unitary operations such as measure and reset. Every gate in the circuit must be translated (by the transpiler) to the elements of a QPU's supported instruction set before it can run on the QPU.\n", + "\n", + "You can view the supported instruction sets for a QPU with Qiskit. The IBM Quantum Platform Compute resources page lists only the supported unitary gates (basis gates) for a QPU.\n", + "\n", + "\n", + " \n", + " \n", + "\n", + " \n", + "\n", + " \n", + " \n", + "\n", + " Navigate to the [Compute resources](https://quantum.cloud.ibm.com/computers) page to view a table of all QPUs, then click the name of any QPU to open its detailed information card. The basis gates for that QPU are listed in the Details section.\n", + " \n", + "\n", + "\n", + "\n", + "### Table of supported instructions\n", + "\n", + "| Operation category | Name |\n", + "| :--- | :--- |\n", + "| Single-qubit gates | [`RZ`](/docs/api/qiskit/qiskit.circuit.library.RZGate), [`SX`](/docs/api/qiskit/qiskit.circuit.library.SXGate), [`X`](/docs/api/qiskit/qiskit.circuit.library.XGate), [`ID`](/docs/api/qiskit/qiskit.circuit.library.IGate), [`delay`](/docs/api/qiskit/circuit#qiskit.circuit.Delay) |\n", + "| Two-qubit gates | [`CZ`](/docs/api/qiskit/qiskit.circuit.library.CZGate), [`ECR`](/docs/api/qiskit/qiskit.circuit.library.ECRGate)|\n", + "| Fractional gates | [`RX`](/docs/api/qiskit/qiskit.circuit.library.RXGate) (single-qubit), [`RZZ`](/docs/api/qiskit/qiskit.circuit.library.RZZGate) (two-qubit) |\n", + "| Non-unitary instructions | [`measure`](/docs/api/qiskit/circuit#qiskit.circuit.Measure), [`reset`](/docs/api/qiskit/circuit#qiskit.circuit.Reset), [`measure_*`](/docs/guides/measure-qubits#mid-circuit-measurements), [`delay`](/docs/api/qiskit/circuit#delay) |\n", + "| Control flow | [`if_else`](/docs/api/qiskit/qiskit.circuit.IfElseOp) (classical feedforward) |" + ] + }, + { + "cell_type": "code", + "execution_count": 2, + "id": "1471a0cb-faf5-419d-9437-b9ecc9a87541", + "metadata": { + "tags": [ + "id-gates" + ] + }, + "outputs": [ + { + "name": "stdout", + "output_type": "stream", + "text": [ + "Backend: ibm_kingston\n", + " Processor type: {'family': 'Heron', 'revision': '2'}\n", + " Supported instructions: ['cz', 'id', 'delay', 'measure', 'measure_2', 'reset', 'rz', 'sx', 'x', 'if_else']\n" + ] + } + ], + "source": [ + "from qiskit_ibm_runtime import QiskitRuntimeService\n", + "\n", + "service = QiskitRuntimeService()\n", + "backend = service.backend(\"ibm_kingston\")\n", + "\n", + "print(f\"Backend: {backend.name}\")\n", + "print(f\" Processor type: {backend.processor_type}\")\n", + "print(f\" Supported instructions: {backend.supported_instructions}\")" + ] + }, + { + "cell_type": "markdown", + "id": "693a91b6-5bd0-411f-ba83-be72d3732402", + "metadata": {}, + "source": [ + "## Dynamic backend information\n", + "\n", + "Backends also have properties that change whenever the backend is calibrated, such as qubit frequency and operation error rates. Backend properties update after the calibration sequence completes. These properties can be used when optimizing quantum circuits or to construct noise models for a classical simulator. See the [Calibration jobs](/docs/guides/calibration-jobs) guide for more information.\n", + "\n", + "On IBM Quantum Platform, you can download calibration data as a CSV file. Click a QPU on the [Compute resources](https://quantum.cloud.ibm.com/computers) page to view its detailed information card, then click the download icon in the upper right corner of the Calibration data section.\n", + "\n", + "\n", + " You can retrieve historical backend properties data in Qiskit with the following code:\n", + "\n", + " ```python\n", + " backend.properties(datetime=)\n", + " ```\n", + "\n", + "\n", + "\n", + "### Qubit properties\n", + "\n", + "[Jump to the list of qubit properties](#view-qubit-properties)\n", + "\n", + "`backend.properties().qubit_property()` returns information about the qubits' physical attributes. It contains a dictionary of various properties of the qubit, each paired with its value and the timestamp of the last calibration.\n", + "\n", + "The following code examples demonstrate how to list all properties, or retrieve specific properties, of a particular qubit.\n", + "\n", + " \n", + " \n", + "\n", + "#### View qubit properties\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "The $T_1$ time represents the average duration a qubit remains in its excited state $|1\\rangle$ before decaying to its ground state $|0\\rangle$ due to energy relaxation. This parameter is used to characterize the qubit's energy relaxation behavior, and is expressed in units of seconds (s).\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`backend.properties().t1()`
View on IBM Quantum PlatformCalibration data section, Qubit dropdown menu; find the *$T_1$ median* value in the Details section
\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "The $T_2$ time denotes the timescale over which a qubit maintains phase coherence of a superposition between the $|0\\rangle$ and $|1\\rangle$ states. It accounts for both energy relaxation and pure dephasing processes, providing insight into the qubit's coherence properties. $T_2$ is reported from a Hahn echo sequence.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`backend.properties().t2()`
View on IBM Quantum PlatformCalibration data section, Qubit dropdown menu; find the *$T_2$ median* value in the Details section
\n", + "\n", + "" + ] + }, + { + "cell_type": "code", + "execution_count": null, + "id": "852d47b7-50c6-4fde-9d59-603825b3ec97", + "metadata": { + "tags": [ + "id-properties" + ] + }, + "outputs": [ + { + "data": { + "text/plain": [ + "QubitProperties(t1=0.00020833187791710663, t2=0.00023395229316289175, frequency=None)" + ] + }, + "execution_count": 6, + "metadata": {}, + "output_type": "execute_result" + } + ], + "source": [ + "# fundamental physical properties of qubit 1\n", + "\n", + "backend = service.backend(\"ibm_fez\")\n", + "\n", + "backend.qubit_properties(1)" + ] + }, + { + "cell_type": "code", + "execution_count": null, + "id": "6ec8f609-9542-4f9e-8a68-0829627211b7", + "metadata": { + "tags": [ + "id-properties2" + ] + }, + "outputs": [ + { + "name": "stdout", + "output_type": "stream", + "text": [ + "Qubit 126 Properties:\n", + " T1: 0.00011004519582612597 seconds\n", + " T2: 6.519695327562977e-05 seconds\n", + " Readout Error: 0.003662109375\n", + " P(0 | 1): 0.0048828125\n", + " P(1 | 0): 0.00244140625\n", + " Readout Length: 1.56e-06 seconds\n" + ] + } + ], + "source": [ + "# Retrieve qubit properties\n", + "qubit_index = 126 # Replace with your qubit index\n", + "qubit_props = backend.properties().qubit_property(qubit_index)\n", + "\n", + "# Access specific properties\n", + "t1 = qubit_props.get(\"T1\", (None,))[0]\n", + "t2 = qubit_props.get(\"T2\", (None,))[0]\n", + "readout_error = qubit_props.get(\"readout_error\", (None,))[0]\n", + "prob_meas0_prep1 = qubit_props.get(\"prob_meas0_prep1\", (None,))[0]\n", + "prob_meas1_prep0 = qubit_props.get(\"prob_meas1_prep0\", (None,))[0]\n", + "readout_length = qubit_props.get(\"readout_length\", (None,))[0]\n", + "\n", + "print(f\"Qubit {qubit_index} Properties:\")\n", + "print(f\" T1: {t1} seconds\")\n", + "print(f\" T2: {t2} seconds\")\n", + "print(f\" Readout Error: {readout_error}\")\n", + "print(f\" P(0 | 1): {prob_meas0_prep1}\")\n", + "print(f\" P(1 | 0): {prob_meas1_prep0}\")\n", + "print(f\" Readout Length: {readout_length} seconds\")" + ] + }, + { + "cell_type": "markdown", + "id": "2d045537-c8f4-4297-852f-b26311d4640d", + "metadata": {}, + "source": [ + "### Instruction properties\n", + "\n", + "[Jump to the list of instruction properties](#view-instruction-properties)\n", + "\n", + "The `backend.target` attribute is a [`qiskit.transpiler.Target`](/docs/api/qiskit/qiskit.transpiler.Target) object: an object that contains all the information needed to transpile a circuit for that backend. This includes instruction errors and durations. For example, the following cell gets the properties for a [`cz` gate](/docs/api/qiskit/qiskit.circuit.library.CZGate) acting between qubits 1 and 0.\n", + "\n", + " \n", + "\n", + "The following cell shows the properties for a measurement operation (including the readout error) on qubit 0.\n", + "\n", + " \n", + "\n", + "\n", + "#### View instruction properties\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "This parameter indicates the probability of measuring a qubit in the 0 state when it was intended to be prepared in the $|1\\rangle$ state, denoted as $P(0 | 1)$. It reflects errors in state preparation and measurement (SPAM), particularly measurement errors in superconducting qubits.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`backend.properties().qubit_property(, 'prob_meas0_prep1')`
View on IBM Quantum PlatformCalibration data section, Qubit dropdown menu
\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "Similarly, this parameter represents the probability of measuring a qubit in the 1 state when it was intended to be prepared in the $|0\\rangle$ state, denoted as $P(1 | 0)$. Like `prob_meas0_prep1`, it reflects SPAM errors, with measurement errors being the predominant contributor in superconducting qubits.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`backend.properties().qubit_property(, 'prob_meas0_prep0')`
View on IBM Quantum PlatformCalibration data section, Qubit dropdown menu
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "f601cb5c-ae7d-4d7b-9666-24b029711b38", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "The two-qubit error per edge from the same batch of measurements used to calculate the [2Q median](#2q-error-median) error. **2Q error (best)** refers to the lowest two-qubit error on any edge of the device, also from this batch of measurements.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`backend.target[''][, ]`
View on IBM Quantum PlatformCalibration section: hover over the qubit connection in Map view, or find the value in Table view under the CZ error (Heron and Nighthawk) or ECR error (Eagle) column; find the value for *2Q error (best)* in the Details section
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "430e075e-063f-4f66-bd74-cd820c54ffbc", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "[Average gate fidelity](/docs/api/qiskit/quantum_info#average_gate_fidelity) of the two-qubit operation from randomized benchmarking. Measured in \"isolation\": batches with a minimum separation of two qubits between edges. This randomized benchmarking uses alternating layers of single-qubit Cliffords and two-qubit gates, and thus the final 2Q error value includes the error of the layer of single-qubit Cliffords.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
Calculate with QiskitFollow the example in this [Qiskit Community GitHub notebook](https://github.com/qiskit-community/qiskit-device-benchmarking/blob/main/notebooks/device_rb_w_lf.ipynb)
View on IBM Quantum PlatformDetails section; also find per-edge data in the Calibration data section
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "236de191-d823-493f-b0c3-981843794e35", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "Average error per layered gate (EPLG) in a chain of 100 qubits. Average EPLG measures the average gate error in a layered chain of $N$ qubits ($N$=100 here). It is derived from a similar quantity known as the layer fidelity (LF) where EPLG$_{100}$ = 4/5(1-LF$^{\\frac{1}{99}}$) and layer fidelity is the process fidelity of the layered chain of $N$ qubits. For details, see the paper [Benchmarking quantum processor performance at scale](https://arxiv.org/abs/2311.05933). Note that in the paper EPLG is defined for process error, but for consistency with the individually reported gate errors here it is quoted for average gate error, thus the factor of 4/5.\n", + "\n", + "\n", + "On IBM Quantum Platform, the detailed information card for each QPU has a section called Two-qubit gate error (layered), which provides the expanded view of the lowest `two-qubit gate error (layered)` measured as a function of the number of qubits in the chain. The final value, at chain length 100, is the value presented in the Details section. In practice, six 100-qubit chains (pre-selected based on expected optimal performance) are measured, and the value reported for number of qubits `N` is the lowest error found in a subset length `N` chain searching over the six 100-qubit chains.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
Calculate with QiskitFollow the example in this [Qiskit Community GitHub notebook](https://github.com/qiskit-community/qiskit-device-benchmarking/blob/main/notebooks/layer_fidelity_single_chain.ipynb)
View on IBM Quantum PlatformDetails section, and an expanded view in the Two-qubit gate error (layered) section
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "d17ebdaf-5bab-4079-bda3-96731a73ce75", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "Error in the RZZ gate averaged over the RZZ angles using a variant of randomized benchmarking for arbitrary unitaries.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with QiskitImportant: Be sure you have set `use_fractional_gates=True` when you load the backend, then you can use `backend.target['rzz'][, ]`
View on IBM Quantum PlatformCalibration section: Select RZZ in the Connection dropdown menu and hover over the qubit connection in Map view. You can also select RZZ error in the Graph output dropdown menu in Graph view, or find the value in Table view under the RZZ error column
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "75a130f0-59f7-4fe3-9947-8feff4c65281", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "Error in the finite-duration discrete one-qubit gates, measured from randomized benchmarking. The randomized benchmarking sequence includes SX, ID, and X gates, and it is assumed their errors are the same. The ID gate is a delay of duration equal to the duration of the √X and X gates. The RX gate is also the same duration as the √X and X gates with variable amplitude, and so it is reported as having the same error as these gates.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`backend.target[''][, ]`
View on IBM Quantum PlatformCalibration section: Qubit dropdown menu
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "242a0ef0-dd7f-4361-b3a0-9b6c8df49f80", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "[Average gate fidelity](/docs/api/qiskit/quantum_info#average_gate_fidelity) of the √X (SX) gate from randomized benchmarking, measured simultaneously on all qubits. The randomized benchmarking sequence includes SX, ID, and X gates, and it is assumed their errors are the same.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View on IBM Quantum PlatformDetails section
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "b4b702f9-e694-4942-aab4-cbdc46f6b7f7", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "Error in the virtual RZ gate. Reported as all 0 since these are performed in software.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit `backend.target[''][, ]`
View on IBM Quantum PlatformCalibration section: Connection dropdown menu
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "5e1e4053-0c2f-4b8d-9cc0-3f25c7fdb981", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "The readout error quantifies the average probability of incorrectly measuring a qubit's state. It is commonly calculated as the mean of `prob_meas0_prep1` and `prob_meas1_prep0`, providing a single metric for measurement fidelity.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`backend.properties().readout_error()`
View on IBM Quantum PlatformCalibration data section, Qubit dropdown menu
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "d8660efa-fc48-467e-acd8-d0fe6041f309", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "Fidelity of the readout operation. Readout error is measured by preparing the qubit in the 0 (1) state and measuring the probability of an output in the 1 (0) state. The reported value is the average of these two errors. The median is taken over all qubits.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View on IBM Quantum PlatformCalibration data section, Details section
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "9e566d6a-cef8-40ee-b80e-182e834bcde3", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "Duration of a single-qubit gate operation. Note that values shown on IBM Quantum Platform are in nanoseconds. Values returned in Qiskit are in seconds.\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`backend.target[''][, ].duration`
View on IBM Quantum PlatformCalibration section: Qubit dropdown menu
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "08d4f1f1-52d6-43fc-82a1-05e627da5159", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "Duration of the two-qubit gate operation. Note that values shown on IBM Quantum Platform are in nanoseconds. Values returned in Qiskit are in seconds.\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`backend.target[''][, ].duration`
View on IBM Quantum PlatformCalibration section: Qubit dropdown menu
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "397d1189-484e-4f13-9146-7b8dc24c0f21", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "The readout length specifies the duration of the readout operation for a qubit. It measures the time from the initiation of the measurement pulse to the completion of signal digitization, after which the system is ready for the next operation. Understanding this parameter is crucial for optimizing circuit execution, especially when incorporating mid-circuit measurements.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit
  • For `measure`: `backend.properties().readout_length()`
  • For `measure_2`: `backend.target['measure_2'][, ].duration`
View on IBM Quantum PlatformCalibration data section, Qubit dropdown menu
\n", + "\n", + "" + ] + }, + { + "cell_type": "code", + "execution_count": 9, + "id": "af5e4fc7-8c6c-4f8a-acc9-2a40802d2fa9", + "metadata": { + "tags": [ + "id-instructions" + ] + }, + "outputs": [ + { + "data": { + "text/plain": [ + "InstructionProperties(duration=6.8e-08, error=0.007854516178238763)" + ] + }, + "execution_count": 9, + "metadata": {}, + "output_type": "execute_result" + } + ], + "source": [ + "backend.target[\"cz\"][(1, 0)]" + ] + }, + { + "cell_type": "code", + "execution_count": 10, + "id": "9837a240-b649-4117-b795-22c47c2a9b6a", + "metadata": { + "tags": [ + "id-instructions1" + ] + }, + "outputs": [ + { + "data": { + "text/plain": [ + "InstructionProperties(duration=1.56e-06, error=0.01416015625)" + ] + }, + "execution_count": 10, + "metadata": {}, + "output_type": "execute_result" + } + ], + "source": [ + "backend.target[\"measure\"][(0,)]" + ] + }, + { + "cell_type": "markdown", + "id": "251f8748-7a6d-4e87-b0f5-8acb91048b36", + "metadata": {}, + "source": [ + "### Additional properties\n", + "\n", + "\n", + "\n", + "\n", + "\n", + "Circuit layer operations per second (CLOPS) is a measure of how many layers of a 100x100 circuit (hardware-aware circuit) a QPU can execute per unit of time.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
Calculate with QiskitFind the [CLOPS code](https://github.com/qiskit-community/qiskit-device-benchmarking/tree/main/qiskit_device_benchmarking/clops#readme) in the Qiskit Community GitHub
View on IBM Quantum PlatformDetails section
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "f350f7db-4797-46e1-a10c-d0b6af8f68ac", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "With [`BackendStatus`](/docs/api/qiskit-ibm-runtime/models-backend-status), you can find the QPU status (for example, `Active`, `Paused`, `Offline`) as well as the number of pending jobs.\n", + "\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`print(backend.status().status_msg)`, `print(backend.status().pending_jobs)`
View on IBM Quantum PlatformDetails section
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "0a2bf11b-16a5-48cf-a146-88539b3fd552", + "metadata": {}, + "source": [ + "\n", + "\n", + "\n", + "\n", + "A diagram that indicates the pairs of qubits that support two-qubit gate operations between them. This is also called the coupling map or connectivity. Qubits are represented as circles and the supported two-qubit gate operations are displayed as lines connecting the qubits.\n", + "\n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + " \n", + "
View with Qiskit`from qiskit.visualization import plot_gate_map` then `plot_gate_map(backend)`
View on IBM Quantum PlatformCalibration data section; Click on Expand for a larger view
\n", + "\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "b054f39f-d3fc-4060-81c6-6ceba4bf8045", + "metadata": {}, + "source": [ + "\n", + " If the benchmarking of a qubit or edge does not succeed over the course of several days, whether due to poor data quality or other internal factors, the reported error value is considered stale and will be reported as 1. This is not an indication that the qubit or edge is necessarily non-working or that the error is 1; rather, the error is considered undefined and you should proceed with caution when operating that qubit or gate.\n", + "" + ] + }, + { + "cell_type": "markdown", + "id": "ddeb876a-5260-4b32-83d6-b954c1bd2b9f", + "metadata": {}, + "source": [ + "## Next steps\n", + "\n", + "\n", + " - Learn how to [build noise models](/docs/guides/build-noise-models) to do noisy classical simulation.\n", + " - Review the [Transpiler stages](/docs/guides/transpiler-stages) topic to learn about how the transpiler uses backend properties for circuit optimization.\n", + " - Review the [QiskitRuntime backend API](/docs/api/qiskit-ibm-runtime/qiskit-runtime-service#backend) reference.\n", + "" + ] + } + ], + "metadata": { + "in_page_toc_max_heading_level": 2, + "in_page_toc_min_heading_level": 2, + "kernelspec": { + "display_name": "Python 3", + "language": "python", + "name": "python3" + }, + "language_info": { + "codemirror_mode": { + "name": "ipython", + "version": 3 + }, + "file_extension": ".py", + "mimetype": "text/x-python", + "name": "python", + "nbconvert_exporter": "python", + "pygments_lexer": "ipython3", + "version": "3" + } + }, + "nbformat": 4, + "nbformat_minor": 4 +} diff --git a/docs/guides/qpu-information.mdx b/docs/guides/qpu-information.mdx deleted file mode 100644 index fd507400425..00000000000 --- a/docs/guides/qpu-information.mdx +++ /dev/null @@ -1,210 +0,0 @@ ---- -title: QPU information -description: Information about QPU calibration, properties, and versioning -in_page_toc_min_heading_level: 2 -in_page_toc_max_heading_level: 2 ---- - -# QPU information - -IBM® offers access to a wide variety of quantum processing units (QPUs). All QPUs deployed by IBM are based on superconducting qubit technology, as the control and scalability of this technology pave a clear path to achieving quantum advantage with these QPUs. - -Explore all public IBM QPUs by navigating to the [Compute resources](https://quantum.cloud.ibm.com/computers) page on IBM Quantum® Platform. Click any QPU to open its detailed information card. - -This page describes the detailed information you will find on the QPU information card. - -## QPU versioning - -Each QPU has a version number in the form X.Y.Z (major.minor.revision). A circuit compiled for a given version number is guaranteed to run on that QPU. If the revision number changes, the circuit will continue to run. If the major or minor number changes, the circuit is not guaranteed to run, although it may do so. The conditions under which a version number may change are listed below: - -### Major version - -The major version will increment for changes such as: - -* Sample changes. -* Major changes to the control electronics. -* Moving the QPU to a new location, if significant behavior changes result. - -### Minor version - -The minor version will increment for changes such as: - -* Warmup / cool-down cycles. -* Swapping out some electronics, if the replacement appreciably affects operation. -* Changing the direction of a controlled-NOT gate. -* Dropping a gate for some duration of time due to calibration issues, and corrections cannot readily be done in software. - -### Revision version - -The revision version number will increment for fixes that do not break the existing compiled circuit. These changes include: - -* Manual calibrations to improve fidelities. -* Small electronics changes that don’t affect operation. -* QPU software updates. - -## QPU details - -The first section of the QPU information card provides the following QPU details: - -[Name](#name) | [Qubits](#qubits) | [2Q error (best)](#2q-error-best) | [2Q error (layered)](#2q-error-layered) | [CLOPS (or CLOPS_h)](#clops-or-clops_h) | [Status](#status) | [Region](#region) | [QPU version](#qpu-version) | [Processor type](#processor-type) | [Basis gates](#native-gates-on-platform) | [Total pending jobs](#total-pending-jobs) | [Median 2Q error](#median-2q-error-heron-cz-eagle-ecr) | -[Median SX error](#median-sx-error) | [Median readout error](#median-readout-error) | [Median T1 (relaxation time)](#median-t1-relaxation-time) | [Median T2 (dephasing time)](#median-t2-dephasing-time) - -### Name - -The unique name assigned to a specific QPU. QPUs hosted on IBM Cloud® have names that begin with `ibm_*`. All QPUs are given a city name, e.g., `ibm_kingston`. This name does not indicate where the actual QPU is hosted. They are named after IBM® locations around the world. - -### Qubits - -The number of physical qubits in a QPU. - -### 2Q error (best) - -The lowest two-qubit (2Q) error on any edge of the device from the same batch of measurements used to calculate the median (see [Median 2Q error](#median-2q-error-heron-cz-eagle-ecr)). - -### 2Q error (layered) - -Average error per layered gate (EPLG) in a chain of 100 qubits. Average EPLG measures the average gate error in a layered chain of $N$ qubits ($N$=100 here). It is derived from a similar quantity known as the layer fidelity (LF) where EPLG$_{100}$ = 4/5(1-LF$^{\frac{1}{99}}$) and layer fidelity is the process fidelity of the layered chain of $N$ qubits. For details, see the paper [Benchmarking quantum processor performance at scale](https://arxiv.org/abs/2311.05933). Note that in the paper EPLG is defined for process error, but for consistency with the individually reported gate errors here it is quoted for average gate error, thus the factor of 4/5. Find an [example notebook](https://github.com/qiskit-community/qiskit-device-benchmarking/blob/main/notebooks/layer_fidelity_single_chain.ipynb) in the Qiskit Community GitHub. - -### CLOPS (or CLOPS_h) - -Circuit layer operations per second, is a measure of how many layers of a 100x100 circuit (hardware-aware circuit) a QPU (quantum processing unit) can execute per unit of time. Find the [CLOPS code](https://github.com/qiskit-community/qiskit-device-benchmarking/tree/main/qiskit_device_benchmarking/clops#readme) in the Qiskit Community GitHub. - -### Status - -The QPU status; for example, `Online`, `Paused`, `Offline`, and so on. - -### Region - -Location of the data center where your data and experiments will be hosted and processed. - -### QPU version - -The version number of a QPU in the form `major.minor.revision`. See [QPU versioning](#qpu-versioning) for details on how this number is assigned. - -### Processor type - -Reflects the [topology](#coupling-map) and indicates the approximate qubit count. - - -### Basis gates - -Each [processor family](/docs/guides/processor-types) has a native gate set. By default, the QPUs in each family only support running the gates and operations in the native gate set. Thus, every gate in the circuit must be translated (by the transpiler) to the elements of this set. Note that the non-unitary operations are not listed here; use the [method in Qiskit](/docs/guides/get-qpu-information#native-gates-with-qiskit) to see all native gates and operations for a QPU. See a list of all native gates in [this table](#native-gates). - -### Total pending jobs - -The total number of jobs that you have submitted to this QPU. - -### Median 2Q error (Heron: CZ, Eagle: ECR) - -[Average gate fidelity](/docs/api/qiskit/quantum_info#average_gate_fidelity) of the two-qubit operation from randomized benchmarking. Measured in "isolation": batches with a minimum separation of two qubits between edges. This randomized benchmarking uses alternating layers of single-qubit Cliffords and two-qubit gates, and thus the final 2Q error value includes the error of the layer of single-qubit Cliffords. Find an [example notebook](https://github.com/qiskit-community/qiskit-device-benchmarking/blob/main/notebooks/device_rb_w_lf.ipynb) in the Qiskit Community GitHub. Find per-edge data in the [calibration data](#calibration-data) section of the QPU information card. - -### Median SX error - -[Average gate fidelity](/docs/api/qiskit/quantum_info#average_gate_fidelity) of the √X (SX) gate from randomized benchmarking, measured simultaneously on all qubits. The randomized benchmarking sequence includes SX, ID, and X gates, and it is assumed their errors are the same. - -### Median readout error - -Fidelity of the readout operation. Readout error is measured by preparing the qubit in the 0 (1) state and measuring the probability of an output in the 1 (0) state. The reported value is the average of these two errors. The median is taken over all qubits. - -### Median T1 (relaxation time) - -The T1 time represents the average duration a qubit remains in its excited state $|1\rangle$ before decaying to its ground state $|0\rangle$ due to energy relaxation. This parameter is used to characterize the qubit's energy relaxation behavior, and is expressed in units of seconds (s). - -### Median T2 (dephasing time) - -The T2 time denotes the timescale over which a qubit maintains phase coherence of a superposition between the $|0\rangle$ and $|1\rangle$ states. It accounts for both energy relaxation and pure dephasing processes, providing insight into the qubit's coherence properties. T2 is reported from a Hahn echo sequence. - -## Calibration data - - -If the benchmarking of a qubit or edge does not succeed over the course of several days, whether due to poor data quality or other internal factors, the reported error value is considered stale and will be reported as 1. This is not an indication that the qubit or edge is necessarily non-working or that the error is 1; rather, the error is considered undefined and you should proceed with caution when operating that qubit or gate. - - -The second section, Calibration data, provides qubit, connectivity, and gate data. You can choose to visualize the information as a map, graph, or table. - -You can customize the data that is shown in each view, using the drop-down menus. For example, in the map view, you can choose the data you want to see for qubits and connections. The colored bars associated with the diagram or graph indicate the range that is shown, with the average value marked. The color maximum and minimum change depending on the QPU. - -To download calibration data as a CSV file, click the download icon in the upper right corner of the Calibration data section. - -In addition to the information provided in the Details section of the card, the Calibration data section also includes the following: - -[Topology diagram or coupling map](#coupling-map) | [Readout assignment error](#readout-assignment-error) | [Prob meas0 prep1](#prob-meas0-prep1) | [Prob meas1 prep0](#prob-meas1-prep0) | [Readout length (ns)](#readout-length-ns) | [ID error / √x (sx) error / Pauli-X error / RX error](#finite-duration-discrete) | [Single-qubit gate length (ns)](#single-qubit-gate-length-ns)| [Z-axis rotation (RZ) error](#z-axis-rotation-rz-error) | [Operational](#operational) | [Gate length (ns)](#gate-length-ns) | [2Q error](#2q-error) | [RZZ error](#rzz-error-heron) - - -### Topology diagram or coupling map - -A diagram that indicates the pairs of qubits that support two-qubit gate operations between them. This is also called the coupling map or connectivity. Qubits are represented as circles and the supported two-qubit gate operations are displayed as lines connecting the qubits. - -### Readout assignment error - -The readout error quantifies the average probability of incorrectly measuring a qubit's state. It is commonly calculated as the mean of prob_meas0_prep1 and prob_meas1_prep0, providing a single metric for measurement fidelity. - -### Prob meas0 prep1 - -This parameter indicates the probability of measuring a qubit in the $|0\rangle$ state when it was intended to be prepared in the $|1\rangle$ state, denoted as $P(0|1)$. It reflects errors in state preparation and measurement (SPAM), particularly measurement errors in superconducting qubits. - -### Prob meas1 prep0 - -Similarly, this parameter represents the probability of measuring a qubit in the $|1\rangle$ state when it was intended to be prepared in the $|0\rangle$ state, denoted as $P(1|0)$. Like prob_meas0_prep1, it reflects SPAM errors, with measurement errors being the predominant contributor in superconducting qubits. - -### Readout length (ns) - -The readout_length specifies the duration of the readout operation for a qubit. It measures the time from the initiation of the measurement pulse to the completion of signal digitization, after which the system is ready for the next operation. Understanding this parameter is crucial for optimizing circuit execution, especially when incorporating mid-circuit measurements. - - -### ID error / √x (sx) error / Pauli-X error / RX error - -Error in the finite-duration discrete one-qubit gates, measured from randomized benchmarking. The randomized benchmarking sequence includes SX, ID, and X gates, and it is assumed their errors are the same. The ID gate is a delay of duration equal to the duration of the √X and X gates. The RX gate is also the same duration as the √X and X gates with variable amplitude, and so it is reported as having the same error as these gates. - -### Single-qubit gate length (ns) - -Duration of a single-qubit gate operation. - -### Z-axis rotation (RZ) error - -Error in the virtual RZ gate. Reported as all 0 since these are performed in software. - -### Operational - -Indicates whether the qubit can be utilized in circuits. - -### Gate length (ns) - -Duration of the two-qubit gate operation. - - -### 2Q error (Heron: CZ, Eagle: ECR) - -The 2Q error per edge from the same batch of measurements used to calculate the [2Q median](#median-2q-error-heron-cz-eagle-ecr) and [2Q best](#2q-error-best) errors. - -### RZZ error (Heron) - -Error in the RZZ gate averaged over the RZZ angles using a variant of randomized benchmarking for arbitrary unitaries. - - -## Two-qubit gate error (layered) - -The third section provides the expanded view of the lowest `two-qubit gate error (layered)` measured as a function of the number of qubits in the chain. The final value, at chain length 100, is the value presented in the Details section. In practice, six 100-qubit chains (pre-selected based on expected optimal performance) are measured, and the value reported for number of qubits `N` is the lowest error found in a subset length `N` chain searching over the six 100-qubit chains. - - -## View your resources - -To find your available QPUs, open the [Compute resources](https://quantum.cloud.ibm.com/computers) page (make sure you are signed in). Note that your selected region might impact the QPUs listed. Click a QPU to view its details. - -You can also view your available QPUs by using the [backends API.](/docs/api/qiskit-ibm-runtime/qiskit-runtime-service#backends) For example, the following code will return all of the backends that the specified instance (`my_instance`) can access: - -```python - QiskitRuntimeService(instance="my_instance_CRN") - service.backends() -``` - - -## Table of native gates and operations - -| Operation category | Name | -| :--- | :--- | -| Single-qubit gates | [`RZ`](/docs/api/qiskit/qiskit.circuit.library.RZGate), [`SX`](/docs/api/qiskit/qiskit.circuit.library.SXGate), [`X`](/docs/api/qiskit/qiskit.circuit.library.XGate), [`ID`](/docs/api/qiskit/qiskit.circuit.library.IGate), [`delay`](/docs/api/qiskit/circuit#qiskit.circuit.Delay) | -| Two-qubit gates | [`CZ`](/docs/api/qiskit/qiskit.circuit.library.CZGate), [`ECR`](/docs/api/qiskit/qiskit.circuit.library.ECRGate)| -| Fractional gates | [`RX`](/docs/api/qiskit/qiskit.circuit.library.RXGate) (single-qubit), [`RZZ`](/docs/api/qiskit/qiskit.circuit.library.RZZGate) (two-qubit) | -| Non-unitary instructions | [`measure`](/docs/api/qiskit/circuit#qiskit.circuit.Measure), [`reset`](/docs/api/qiskit/circuit#qiskit.circuit.Reset) | -| Control flow | [`if_else`](/docs/api/qiskit/qiskit.circuit.IfElseOp) (classical feedforward) | \ No newline at end of file diff --git a/docs/guides/represent-quantum-computers.ipynb b/docs/guides/represent-quantum-computers.ipynb index 3d91a9e0f95..7a9695a9845 100644 --- a/docs/guides/represent-quantum-computers.ipynb +++ b/docs/guides/represent-quantum-computers.ipynb @@ -51,8 +51,8 @@ "source": [ "To convert an abstract circuit to an ISA circuit that can run on a specific QPU (quantum processing unit), the transpiler needs certain information about the QPU. This information is found in two places: the `BackendV2` (or legacy `BackendV1`) object you plan to submit jobs to, and the backend's `Target` attribute.\n", "\n", - "- The [`Target`](../api/qiskit/qiskit.transpiler.Target) contains all the relevant constraints of a device, such as its native basis gates, qubit connectivity, and pulse or timing information.\n", - "- The [`Backend`](../api/qiskit/qiskit.providers.BackendV2) possesses a `Target` by default, contains additional information -- such as the [`InstructionScheduleMap`](/docs/api/qiskit/1.4/qiskit.pulse.InstructionScheduleMap), and provides the interface for submitting quantum circuit jobs.\n", + "- The [`Target`](/docs/api/qiskit/qiskit.transpiler.Target) contains all the relevant constraints of a device, such as its supported instruction set, qubit connectivity, and pulse or timing information.\n", + "- The [`Backend`](/docs/api/qiskit/qiskit.providers.BackendV2) possesses a `Target` by default, contains additional information -- such as the [`InstructionScheduleMap`](/docs/api/qiskit/1.4/qiskit.pulse.InstructionScheduleMap), and provides the interface for submitting quantum circuit jobs.\n", "\n", "You can also explicitly provide information for the transpiler to use, for example, if you have a specific use case, or if you believe this information will help the transpiler generate a more optimized circuit.\n", "\n", @@ -163,7 +163,7 @@ "id": "2ad3848d", "metadata": {}, "source": [ - "This example is used in later sections of this topic to illustrate that the coupling map and basis gates are the essential pieces of information to pass to the transpiler for optimal circuit construction. The QPU can usually select default settings for other information that is not passed in, such as timing and scheduling." + "This example is used in later sections of this topic to illustrate that the coupling map and supported instruction set are the essential pieces of information to pass to the transpiler for optimal circuit construction. The QPU can usually select default settings for other information that is not passed in, such as timing and scheduling." ] }, { @@ -319,9 +319,9 @@ "id": "f62e0541", "metadata": {}, "source": [ - "## Basis gates\n", + "## Supported instructions\n", "\n", - "Every quantum computer supports a limited instruction set, called its _basis gates_. Every gate in the circuit must be translated to the elements of this set. This set should consist of single- and two-qubit gates that provide a universal gates set, meaning that any quantum operation can be decomposed into those gates. This is done by the [BasisTranslator](../api/qiskit/qiskit.transpiler.passes.BasisTranslator), and the basis gates can be specified as a keyword argument to the transpiler to provide this information." + "Every quantum computer supports a limited instruction set. Every gate in the circuit must be translated to the elements of this set. This set should consist of single- and two-qubit gates that provide a universal gate set, meaning that any quantum operation can be decomposed into those gates. This is done by the [BasisTranslator](/docs/api/qiskit/qiskit.transpiler.passes.BasisTranslator), and `basis_gates` can be specified as a keyword argument to the transpiler to provide this information." ] }, { diff --git a/qiskit_bot.yaml b/qiskit_bot.yaml index efb34a999a5..d75ab25daa5 100644 --- a/qiskit_bot.yaml +++ b/qiskit_bot.yaml @@ -138,11 +138,7 @@ notifications: "docs/guides/fractional-gates": - "@kaelynj" "docs/guides/measure-qubits": - - "`@beckykd`" - "docs/guides/get-qpu-information": - - "@frankharkins" - - "`@abbycross`" - - "`@mtreinish`" + - "@beckykd" "docs/guides/get-started-with-primitives": - "@ElePT" - "@jyu00" diff --git a/scripts/config/notebook-testing.toml b/scripts/config/notebook-testing.toml index d213eca0597..1cfd242889d 100644 --- a/scripts/config/notebook-testing.toml +++ b/scripts/config/notebook-testing.toml @@ -26,7 +26,7 @@ notebooks = [ "docs/guides/dynamical-decoupling-pass-manager.ipynb", "docs/guides/error-mitigation-and-suppression-techniques.ipynb", "docs/guides/execution-modes-rest-api.ipynb", - "docs/guides/get-qpu-information.ipynb", + "docs/guides/qpu-information.ipynb", "docs/guides/interoperate-qiskit-qasm2.ipynb", "docs/guides/interoperate-qiskit-qasm3.ipynb", "docs/guides/local-testing-mode.ipynb",