diff --git a/README.md b/README.md index 3d0ff44b4f..40df6c0c86 100644 --- a/README.md +++ b/README.md @@ -599,9 +599,10 @@ Some companies require a special attribution notice. View a list of the companie - IBM® - IBM Cloud® - IBM Quantum™ -- Qiskit® +**Note**: Although Qiskit is a registered trademark of IBM, we do not mark it as such. + See the Usage section of the IBM Quantum Experience Guide for guidance on when to use IBM and when to use IBM Quantum. ### Trademark symbols @@ -612,6 +613,4 @@ Use `®` to get ® for registered trademarks. use `™` to get ™ for nonregistered trademarks. - - Do not include trademarks in headings. The code will display rather than the symbol. - Do not try to upgrade an existing Python virtual environment to Qiskit 1.0 in-place. diff --git a/docs/api/migration-guides/qiskit-1.0.mdx b/docs/api/migration-guides/qiskit-1.0.mdx index 7c3212ab46..e0f605abab 100644 --- a/docs/api/migration-guides/qiskit-1.0.mdx +++ b/docs/api/migration-guides/qiskit-1.0.mdx @@ -5,7 +5,7 @@ description: How to update your project so that it works with Qiskit 1.0. # Qiskit 1.0 migration guide -Qiskit® 1.0 brings new stability guarantees and performance improvements, but it +Qiskit 1.0 brings new stability guarantees and performance improvements, but it does break compatibility with all previous versions of Qiskit. See the following guides on updating your environment and code to work with Qiskit 1.0. diff --git a/docs/api/migration-guides/qiskit-algorithms-module.mdx b/docs/api/migration-guides/qiskit-algorithms-module.mdx index 96f820028b..e918158161 100644 --- a/docs/api/migration-guides/qiskit-algorithms-module.mdx +++ b/docs/api/migration-guides/qiskit-algorithms-module.mdx @@ -5,7 +5,7 @@ description: How to update your code to use the new interface for `qiskit.algori # Algorithms migration guide - In Qiskit® 0.44 and later releases, the `qiskit.algorithms` module has been superseded by a new standalone library, `qiskit_algorithms`, + In Qiskit 0.44 and later releases, the `qiskit.algorithms` module has been superseded by a new standalone library, `qiskit_algorithms`, available on [GitHub](https://github.com/qiskit-community/qiskit-algorithms) and [PyPi](https://pypi.org/project/qiskit-algorithms). The `qiskit.algorithms` module was migrated to a separate package in order to clarify the purpose of Qiskit and make a distinction between the tools and libraries built on top of it. diff --git a/docs/api/migration-guides/qiskit-opflow-module.mdx b/docs/api/migration-guides/qiskit-opflow-module.mdx index 94df99c3ef..ca8343eb98 100644 --- a/docs/api/migration-guides/qiskit-opflow-module.mdx +++ b/docs/api/migration-guides/qiskit-opflow-module.mdx @@ -8,7 +8,7 @@ description: How to update your code to stop using the deprecated `qiskit.opflow The new [`qiskit.primitives`](../qiskit/primitives), in combination with the [`qiskit.quantum_info`](../qiskit/quantum_info) module, have superseded functionality of [`qiskit.opflow`](../qiskit/0.46/opflow), which is being deprecated. -This migration guide contains instructions and code examples to migrate Qiskit® code that uses +This migration guide contains instructions and code examples to migrate Qiskit code that uses the [`qiskit.opflow`](../qiskit/0.46/opflow) module to the [`qiskit.primitives`](../qiskit/primitives) and [`qiskit.quantum_info`](../qiskit/quantum_info) modules. diff --git a/docs/api/migration-guides/qiskit-quantum-instance.mdx b/docs/api/migration-guides/qiskit-quantum-instance.mdx index 652a2008b9..1b9cdef156 100644 --- a/docs/api/migration-guides/qiskit-quantum-instance.mdx +++ b/docs/api/migration-guides/qiskit-quantum-instance.mdx @@ -28,7 +28,7 @@ The remainder of this guide focused on the [`qiskit.utils.QuantumInstance.execut [`qiskit.primitives`](../qiskit/primitives) migration path. - **Background on the Qiskit® primitives** + **Background on the Qiskit primitives** The Qiskit primitives are algorithmic abstractions that encapsulate system or simulator access for easy integration into algorithm workflows. diff --git a/docs/api/migration-guides/qiskit-runtime-examples.mdx b/docs/api/migration-guides/qiskit-runtime-examples.mdx index 66d2b4701c..4293dd6732 100644 --- a/docs/api/migration-guides/qiskit-runtime-examples.mdx +++ b/docs/api/migration-guides/qiskit-runtime-examples.mdx @@ -6,7 +6,7 @@ description: Examples of migrating from using backend.run to using Qiskit Runtim # Migration examples -Follow these examples to design a Qiskit® Runtime algorithm. +Follow these examples to design a Qiskit Runtime algorithm. ## Use Estimator to design an algorithm diff --git a/docs/api/migration-guides/qiskit-runtime-from-provider.mdx b/docs/api/migration-guides/qiskit-runtime-from-provider.mdx index fc867cbd93..149c8856a4 100644 --- a/docs/api/migration-guides/qiskit-runtime-from-provider.mdx +++ b/docs/api/migration-guides/qiskit-runtime-from-provider.mdx @@ -5,7 +5,7 @@ description: How to migrate `backend.run()` from Qiskit IBM Provider to Qiskit I # Migrate `backend.run()` from `qiskit_ibm_provider` to `qiskit_ibm_runtime` -The Qiskit® Runtime interface includes two packages: +The Qiskit Runtime interface includes two packages: Qiskit IBM Provider (the [`qiskit_ibm_provider`](../qiskit-ibm-provider) package) and Qiskit IBM Runtime (the [`qiskit_ibm_runtime`](../qiskit-ibm-runtime) package). Until now, primitives (`Sampler` and `Estimator`) diff --git a/docs/api/migration-guides/qiskit-runtime.mdx b/docs/api/migration-guides/qiskit-runtime.mdx index 8227c9c1a2..6e8b49274d 100644 --- a/docs/api/migration-guides/qiskit-runtime.mdx +++ b/docs/api/migration-guides/qiskit-runtime.mdx @@ -11,7 +11,7 @@ in_page_toc_max_heading_level: 2 This guide describes key patterns of behavior and use cases with code examples to help you migrate code from the legacy `qiskit-ibmq-provider` -package to use the Qiskit® Runtime primitives. +package to use the Qiskit Runtime primitives. ## Overview diff --git a/docs/build/bit-ordering.mdx b/docs/build/bit-ordering.mdx index 91742f9fb4..4305d0f5da 100644 --- a/docs/build/bit-ordering.mdx +++ b/docs/build/bit-ordering.mdx @@ -11,7 +11,7 @@ these bits both in computer memory and when displayed on-screen. ## Qiskit conventions -Here's how Qiskit® orders bits in different scenarios. +Here's how Qiskit orders bits in different scenarios. ### Quantum circuits diff --git a/docs/build/circuit-construction.ipynb b/docs/build/circuit-construction.ipynb index 972a6a3b0d..368af1e373 100644 --- a/docs/build/circuit-construction.ipynb +++ b/docs/build/circuit-construction.ipynb @@ -13,7 +13,7 @@ "id": "c50d8e43-ae82-4e41-8d17-a37332d1bf6d", "metadata": {}, "source": [ - "This page takes a closer look at the [`QuantumCircuit`](/api/qiskit/qiskit.circuit.QuantumCircuit) class in Qiskit®, including some more advanced methods you can use to create quantum circuits." + "This page takes a closer look at the [`QuantumCircuit`](/api/qiskit/qiskit.circuit.QuantumCircuit) class in Qiskit, including some more advanced methods you can use to create quantum circuits." ] }, { diff --git a/docs/build/circuit-library.ipynb b/docs/build/circuit-library.ipynb index 56564a764c..d88b517a2a 100644 --- a/docs/build/circuit-library.ipynb +++ b/docs/build/circuit-library.ipynb @@ -14,7 +14,7 @@ "id": "6f257ff9-15c4-48d8-9503-7f0ab16a91b2", "metadata": {}, "source": [ - "Qiskit® includes a library of popular circuits to use as building blocks in your own programs. Using pre-defined circuits saves time researching, writing code, and debugging. The library includes popular circuits in quantum computing, circuits that are difficult to simulate classically, and circuits useful for quantum hardware benchmarking.\n", + "Qiskit includes a library of popular circuits to use as building blocks in your own programs. Using pre-defined circuits saves time researching, writing code, and debugging. The library includes popular circuits in quantum computing, circuits that are difficult to simulate classically, and circuits useful for quantum hardware benchmarking.\n", "\n", "This page lists the different circuit categories the library provides. For a full list of circuits, see the [circuit library API documentation](/api/qiskit/circuit_library)." ] diff --git a/docs/build/circuit-visualization.ipynb b/docs/build/circuit-visualization.ipynb index f2ba950549..86467a4526 100644 --- a/docs/build/circuit-visualization.ipynb +++ b/docs/build/circuit-visualization.ipynb @@ -13,7 +13,7 @@ "id": "6cab750e-ca5d-48c0-b69b-040eee04a506", "metadata": {}, "source": [ - "A visualization is useful while working with quantum circuits. Below find options in Qiskit® for drawing circuits, plotting data from executed jobs, seeing the state of a quantum computer, and more." + "A visualization is useful while working with quantum circuits. Below find options in Qiskit for drawing circuits, plotting data from executed jobs, seeing the state of a quantum computer, and more." ] }, { diff --git a/docs/build/classical-feedforward-and-control-flow.ipynb b/docs/build/classical-feedforward-and-control-flow.ipynb index 773777e9e3..c476005184 100644 --- a/docs/build/classical-feedforward-and-control-flow.ipynb +++ b/docs/build/classical-feedforward-and-control-flow.ipynb @@ -7,7 +7,7 @@ "source": [ "# Classical feedforward and control flow\n", "\n", - "This guide demonstrates the functionality available in Qiskit® for performing classical feedforward and control flow. These features are sometimes referred to collectively as \"dynamic circuits.\" Classical feedforward refers to the ability to measure qubits in the middle of a circuit and perform additional quantum operations that depend on the measurement outcome. Qiskit supports four control flow constructs for classical feedforward, each implemented as a method on [`QuantumCircuit`](../api/qiskit/qiskit.circuit.QuantumCircuit). The constructs and their corresponding methods are:\n", + "This guide demonstrates the functionality available in Qiskit for performing classical feedforward and control flow. These features are sometimes referred to collectively as \"dynamic circuits.\" Classical feedforward refers to the ability to measure qubits in the middle of a circuit and perform additional quantum operations that depend on the measurement outcome. Qiskit supports four control flow constructs for classical feedforward, each implemented as a method on [`QuantumCircuit`](../api/qiskit/qiskit.circuit.QuantumCircuit). The constructs and their corresponding methods are:\n", "\n", "- If statement - [`QuantumCircuit.if_test`](../api/qiskit/qiskit.circuit.QuantumCircuit#if_test)\n", "- Switch statement - [`QuantumCircuit.switch`](../api/qiskit/qiskit.circuit.QuantumCircuit#switch)\n", diff --git a/docs/build/index.mdx b/docs/build/index.mdx index ba5e878950..0241e460aa 100644 --- a/docs/build/index.mdx +++ b/docs/build/index.mdx @@ -10,7 +10,7 @@ In the build phase, you create quantum programs that represent the problem you a All tasks require building one or more [quantum circuits](circuit-construction). Some tasks additionally require constructing [quantum operators](operators-overview) to define properties of quantum states that you want to estimate or measure. -Qiskit® enables working with circuits (and, to some extent, operators) at various abstraction levels: abstract, virtual, physical, scheduled, and pulse programs. At the most abstract level is a task-oriented lens in the [circuit library](circuit-library). You can also express operations in abstract mathematical terms using operators, isometries, and classical/Boolean functions. For virtual circuits, mathematical abstractions take on a concrete representation in terms of a concrete gate set. At the physical level, those instructions are mapped to specific physical qubits, and instructions are re-written to reflect the connectivity and native gate set of a target hardware platform. Scheduled circuits introduce timing information, and [pulse programs](pulse) represent signals on channels. +Qiskit enables working with circuits (and, to some extent, operators) at various abstraction levels: abstract, virtual, physical, scheduled, and pulse programs. At the most abstract level is a task-oriented lens in the [circuit library](circuit-library). You can also express operations in abstract mathematical terms using operators, isometries, and classical/Boolean functions. For virtual circuits, mathematical abstractions take on a concrete representation in terms of a concrete gate set. At the physical level, those instructions are mapped to specific physical qubits, and instructions are re-written to reflect the connectivity and native gate set of a target hardware platform. Scheduled circuits introduce timing information, and [pulse programs](pulse) represent signals on channels. Qiskit and [OpenQASM](introduction-to-qasm) further support the notion of extended circuits, which expand the set of allowed operations to include real-time computations on classical values. Qiskit's tooling for working with this richer family of circuits is found in the section on [Classical feedforward and control flow](classical-feedforward-and-control-flow). diff --git a/docs/build/interoperate-qiskit-qasm2.mdx b/docs/build/interoperate-qiskit-qasm2.mdx index e850088738..fc9010e655 100644 --- a/docs/build/interoperate-qiskit-qasm2.mdx +++ b/docs/build/interoperate-qiskit-qasm2.mdx @@ -6,7 +6,7 @@ description: How to convert code between OpenQASM 2 and Qiskit. # OpenQASM 2 and Qiskit -Qiskit® provides some tools for converting between OpenQASM representations of quantum programs, and the [QuantumCircuit](../api/qiskit/qiskit.circuit.QuantumCircuit) class. +Qiskit provides some tools for converting between OpenQASM representations of quantum programs, and the [QuantumCircuit](../api/qiskit/qiskit.circuit.QuantumCircuit) class. ## Import an OpenQASM 2 program into Qiskit diff --git a/docs/build/interoperate-qiskit-qasm3.mdx b/docs/build/interoperate-qiskit-qasm3.mdx index bce2327346..c54e6251d1 100644 --- a/docs/build/interoperate-qiskit-qasm3.mdx +++ b/docs/build/interoperate-qiskit-qasm3.mdx @@ -6,7 +6,7 @@ description: How to convert code between OpenQASM 3 and Qiskit. # OpenQASM 3 and Qiskit -Qiskit® provides some tools for converting between OpenQASM representations of quantum programs, and the QuantumCircuit class. Note these tools are still in an exploratory phase of development and will continue to evolve as Qiskit’s support for dynamic circuit capabilities expressed by OpenQASM 3 increases. +Qiskit provides some tools for converting between OpenQASM representations of quantum programs, and the QuantumCircuit class. Note these tools are still in an exploratory phase of development and will continue to evolve as Qiskit’s support for dynamic circuit capabilities expressed by OpenQASM 3 increases. This function is still in the exploratory phase. Therefore, it is likely that the syntax and capabilities will evolve. diff --git a/docs/build/introduction-to-qasm.mdx b/docs/build/introduction-to-qasm.mdx index 4de1e8365d..f0ce9d6973 100644 --- a/docs/build/introduction-to-qasm.mdx +++ b/docs/build/introduction-to-qasm.mdx @@ -15,7 +15,7 @@ OpenQASM is the choice for a variety of audiences because of its versatility. Th OpenQASM is the common interchange format among independent quantum software tools. For developers that prefer one tool for circuit construction, another for transpilation, and so forth, OpenQASM is the *lingua franca* that acts as a bridge among them. - Qiskit® provides ways to convert between OpenQASM and the [`QuantumCircuit`](../api/qiskit/qiskit.circuit.QuantumCircuit) class (see [OpenQASM 2 and Qiskit](interoperate-qiskit-qasm2) and [OpenQASM 3 and Qiskit](interoperate-qiskit-qasm3) for instructions). + Qiskit provides ways to convert between OpenQASM and the [`QuantumCircuit`](../api/qiskit/qiskit.circuit.QuantumCircuit) class (see [OpenQASM 2 and Qiskit](interoperate-qiskit-qasm2) and [OpenQASM 3 and Qiskit](interoperate-qiskit-qasm3) for instructions). For more information, view the [OpenQASM live specification.](https://openqasm.com/) diff --git a/docs/build/operators-overview.ipynb b/docs/build/operators-overview.ipynb index 25b4d698a5..64b68db288 100644 --- a/docs/build/operators-overview.ipynb +++ b/docs/build/operators-overview.ipynb @@ -13,7 +13,7 @@ "id": "8a16a455-4530-4f2e-be6c-8c0da255b1c5", "metadata": {}, "source": [ - "The `Operator` class is used in Qiskit® to represent matrix operators acting on a quantum system. It has several methods to build composite operators using tensor products of smaller operators, and to compose operators.\n", + "The `Operator` class is used in Qiskit to represent matrix operators acting on a quantum system. It has several methods to build composite operators using tensor products of smaller operators, and to compose operators.\n", "\n", "### Creating Operators\n", "\n", diff --git a/docs/build/pulse.ipynb b/docs/build/pulse.ipynb index ed750ab7d8..5ae472b6d2 100644 --- a/docs/build/pulse.ipynb +++ b/docs/build/pulse.ipynb @@ -11,7 +11,7 @@ "\n", "Most quantum algorithms can be described with circuit operations alone. When you need more control over the low-level program implementation, you can use _pulse gates_. Pulse gates remove the constraint of executing circuits with basis gates only and let you override the default implementation of any basis gate.\n", "\n", - "Pulse gates let you map a logical circuit gate (for example, `X`) to a Qiskit® Pulse program, called a `ScheduleBlock`. This mapping is referred to as a _calibration_. A high-fidelity calibration is one that faithfully implements the logical operation it is mapped from (for example, whether the `X` gate calibration drives $|0\\rangle$ to $|1\\rangle$).\n", + "Pulse gates let you map a logical circuit gate (for example, `X`) to a Qiskit Pulse program, called a `ScheduleBlock`. This mapping is referred to as a _calibration_. A high-fidelity calibration is one that faithfully implements the logical operation it is mapped from (for example, whether the `X` gate calibration drives $|0\\rangle$ to $|1\\rangle$).\n", "\n", "A schedule specifies the exact time dynamics of the input signals across all input _channels_ to the device. There are usually multiple channels per qubit, such as drive and measure. This interface is more powerful, and requires a deeper understanding of the underlying device physics.\n", "\n", diff --git a/docs/build/qasm-feature-table.mdx b/docs/build/qasm-feature-table.mdx index 98836713f1..c1d2296ebe 100644 --- a/docs/build/qasm-feature-table.mdx +++ b/docs/build/qasm-feature-table.mdx @@ -72,7 +72,7 @@ Key: - Learn how to generate OpenQASM code in the [Explore gates and circuits with the Quantum Composer](https://learning.quantum.ibm.com/tutorial/explore-gates-and-circuits-with-the-quantum-composer) tutorial. - - See the [OpenQASM 3 Qiskit® API](/api/qiskit/qasm3) reference. + - See the [OpenQASM 3 Qiskit API](/api/qiskit/qasm3) reference. - See the [OpenQASM 2 Qiskit API](/api/qiskit/qasm2) reference. - Review the [Verify your program](../verify/) topic. - Visit the [OpenQASM Live Specification](https://openqasm.com/). diff --git a/docs/build/specify-observables-pauli.mdx b/docs/build/specify-observables-pauli.mdx index 22df399b2f..0cab9f47aa 100644 --- a/docs/build/specify-observables-pauli.mdx +++ b/docs/build/specify-observables-pauli.mdx @@ -46,7 +46,7 @@ $$ where the indices $\langle i, j\rangle$ run over interacting spins and the spins are subject to a transversal field in $X$. The subscript index indicates which qubit the Pauli operator acts on, i.e. $X_i$ applies an $X$ operator on qubit $i$ and leaves the rest unchanged. -In Qiskit®, this Hamiltonian could be constructed as +In Qiskit, this Hamiltonian could be constructed as ```python from qiskit.quantum_info import SparsePauliOp diff --git a/docs/build/unitary-synthesis.mdx b/docs/build/unitary-synthesis.mdx index c1825efab6..15ae10c8ec 100644 --- a/docs/build/unitary-synthesis.mdx +++ b/docs/build/unitary-synthesis.mdx @@ -15,7 +15,7 @@ For general unitary matrices, synthesis is a complex task with computational cos Therefore, if you know an efficient decomposition for the unitary you would like to implement, it will likely be better than a general synthesis. - If no decomposition is available, Qiskit® provides you with the tools to find one. + If no decomposition is available, Qiskit provides you with the tools to find one. However, note that this generally generates deep circuits that may be unsuitable to run on noisy quantum computers. diff --git a/docs/run/advanced-runtime-options.mdx b/docs/run/advanced-runtime-options.mdx index 0403cafdb0..bf2ae6be88 100644 --- a/docs/run/advanced-runtime-options.mdx +++ b/docs/run/advanced-runtime-options.mdx @@ -15,7 +15,7 @@ To ensure faster and more efficient results, as of 1 March 2024, circuits and ob ![The image shows the top-level options categories: transpilation, resilience, execution, environment, and simulation.](/images/build/options.png "Option categories") - This section focuses on Qiskit® Runtime primitive [Options](../api/qiskit-ibm-runtime/qiskit_ibm_runtime.options.Options) (imported from `qiskit_ibm_runtime`). While most of the `primitives` interface is common across implementations, most `Options` are not. Consult the + This section focuses on Qiskit Runtime primitive [Options](../api/qiskit-ibm-runtime/qiskit_ibm_runtime.options.Options) (imported from `qiskit_ibm_runtime`). While most of the `primitives` interface is common across implementations, most `Options` are not. Consult the corresponding API references for information about the `qiskit.primitives` and `qiskit_aer.primitives` options. diff --git a/docs/run/circuit-execution.mdx b/docs/run/circuit-execution.mdx index 99dac85b74..08c355ee71 100644 --- a/docs/run/circuit-execution.mdx +++ b/docs/run/circuit-execution.mdx @@ -26,4 +26,4 @@ Therefore, each circuit is equal in duration to the longest circuit in the batch ## Dynamic repetition rate execution -Some IBM Quantum systems allow for dynamic repetition rate execution. These systems are identified in Qiskit® using `backend.configuration().dynamic_reprate_enabled`, and return a value of `True`. On these systems, it is possible to manually set the above idle time by setting the `rep_delay` of the submitted job. One can see from the above figures that by reducing the idle time one can potentially see a greater throughput of circuits on the systems that support dynamic repetition rates. See the the next section on conditional reset for more detailed usage examples. \ No newline at end of file +Some IBM Quantum systems allow for dynamic repetition rate execution. These systems are identified in Qiskit using `backend.configuration().dynamic_reprate_enabled`, and return a value of `True`. On these systems, it is possible to manually set the above idle time by setting the `rep_delay` of the submitted job. One can see from the above figures that by reducing the idle time one can potentially see a greater throughput of circuits on the systems that support dynamic repetition rates. See the the next section on conditional reset for more detailed usage examples. \ No newline at end of file diff --git a/docs/run/configure-error-mitigation.mdx b/docs/run/configure-error-mitigation.mdx index 5515a52ec0..e35e7fe2e5 100644 --- a/docs/run/configure-error-mitigation.mdx +++ b/docs/run/configure-error-mitigation.mdx @@ -61,7 +61,7 @@ applied at each resilience level. - If using an IBM Cloud® Qiskit® Runtime service instance with Q-CTRL performance management enabled, there is no need to specify runtime optimization or resilience levels, as the strategy includes an automatic preset. + If using an IBM Cloud® Qiskit Runtime service instance with Q-CTRL performance management enabled, there is no need to specify runtime optimization or resilience levels, as the strategy includes an automatic preset. Setting `optimization_level` or `resilience_level` equal to 0 will result in an execution error. Levels 1, 2, and 3 are permitted but will not impact performance. diff --git a/docs/run/dynamic-circuits-considerations.ipynb b/docs/run/dynamic-circuits-considerations.ipynb index 7de36e8694..f448b8de5f 100644 --- a/docs/run/dynamic-circuits-considerations.ipynb +++ b/docs/run/dynamic-circuits-considerations.ipynb @@ -7,7 +7,7 @@ "source": [ "# Hardware considerations and limitations for classical feedforward and control flow\n", "\n", - "[Classical feedforward and control flow](/build/classical-feedforward-and-control-flow) shows how to use Qiskit® to build circuits that involve classical feedforward and control flow, also known as dynamic circuits. When actually running such circuits on quantum hardware, there are several considerations and limitations to be aware of. Many of these limitations exist because the underlying technology supporting these features is in an early stage of development, and we hope to be able to address them in the future.\n", + "[Classical feedforward and control flow](/build/classical-feedforward-and-control-flow) shows how to use Qiskit to build circuits that involve classical feedforward and control flow, also known as dynamic circuits. When actually running such circuits on quantum hardware, there are several considerations and limitations to be aware of. Many of these limitations exist because the underlying technology supporting these features is in an early stage of development, and we hope to be able to address them in the future.\n", "\n", "## Primitives do not currently support classical feedforward and control flow\n", "\n", diff --git a/docs/run/estimate-job-run-time.mdx b/docs/run/estimate-job-run-time.mdx index fa394be516..75151cbdca 100644 --- a/docs/run/estimate-job-run-time.mdx +++ b/docs/run/estimate-job-run-time.mdx @@ -12,7 +12,7 @@ Quantum time is the duration, in seconds, a quantum system is committed to fulfi - This only applies to jobs that use primitives. - - This is not yet available on the Qiskit® Runtime on IBM Cloud® channel. + - This is not yet available on the Qiskit Runtime on IBM Cloud® channel. diff --git a/docs/run/fair-share-queue.mdx b/docs/run/fair-share-queue.mdx index 01ca2c0a3c..8bfe33cb41 100644 --- a/docs/run/fair-share-queue.mdx +++ b/docs/run/fair-share-queue.mdx @@ -10,7 +10,7 @@ When you submit a job to a quantum system, it enters the scheduler for the speci ## Fair-share terms -* **Provider:** An entity providing access to quantum computing. IBM Quantum™ Platform and IBM Cloud® are providers of Qiskit® Runtime services. +* **Provider:** An entity providing access to quantum computing. IBM Quantum™ Platform and IBM Cloud® are providers of Qiskit Runtime services. * **Instance:** A combination of hub/group/project. * **Hub:** Represents the top level of an organization such as an academic, industry, or research partner. * **Group:** A mid-level structure to which access shares can be allocated by the hub for one or more collections of users (projects). diff --git a/docs/run/get-backend-information.ipynb b/docs/run/get-backend-information.ipynb index 8ddc002771..8bf730c1ff 100644 --- a/docs/run/get-backend-information.ipynb +++ b/docs/run/get-backend-information.ipynb @@ -7,7 +7,7 @@ "source": [ "# Get backend information with Qiskit\n", "\n", - "This page explains how to use Qiskit® to find information about your available backends." + "This page explains how to use Qiskit to find information about your available backends." ] }, { diff --git a/docs/run/manage-cost.mdx b/docs/run/manage-cost.mdx index c38d9e4c26..28782f92c1 100644 --- a/docs/run/manage-cost.mdx +++ b/docs/run/manage-cost.mdx @@ -9,7 +9,7 @@ description: How to manage costs of running jobs on systems when using the Stand The IBM Cloud® Quantum Standard plan is not free, except when running jobs on simulators. Use the information in this topic to help you understand how much you’re paying and how to limit your costs. - The information in this topic only applies to those who are using the Standard plan for Qiskit® Runtime on IBM Cloud. There are no costs associated with IBM Quantum™ Platform Open plan. + The information in this topic only applies to those who are using the Standard plan for Qiskit Runtime on IBM Cloud. There are no costs associated with IBM Quantum™ Platform Open plan. ## Set a cost limit diff --git a/docs/run/max-execution-time.mdx b/docs/run/max-execution-time.mdx index 97035b849f..c4896e4d21 100644 --- a/docs/run/max-execution-time.mdx +++ b/docs/run/max-execution-time.mdx @@ -6,7 +6,7 @@ description: Describes how long a Qiskit Runtime job or session can run. # Maximum execution time for a Qiskit Runtime job or session -To ensure fairness and help control costs, there is a maximum amount of time each Qiskit® Runtime job and session can run. If a job exceeds this time limit, it is forcibly canceled and a `RuntimeJobMaxTimeoutError` exception is raised. If a session exceeds its limits, any queued jobs are canceled but any jobs that are already running are not. +To ensure fairness and help control costs, there is a maximum amount of time each Qiskit Runtime job and session can run. If a job exceeds this time limit, it is forcibly canceled and a `RuntimeJobMaxTimeoutError` exception is raised. If a session exceeds its limits, any queued jobs are canceled but any jobs that are already running are not. ## Job maximum execution time diff --git a/docs/run/minimize-time.mdx b/docs/run/minimize-time.mdx index e4b9383367..0517623227 100644 --- a/docs/run/minimize-time.mdx +++ b/docs/run/minimize-time.mdx @@ -10,7 +10,7 @@ There are several ways you can limit the amount of quantum time spent processing - Run only as many iterations and shots as you need: The time your workload takes (and therefore, its cost) depends on how many jobs you create in a session and how many shots are run in each job. Therefore, you can manage your cost by running only as many jobs and shots as you need. -- Set limits on execution time: You can limit how long each job or session runs. For details, see [Maximum execution time for a Qiskit® Runtime job or session](max-execution-time). +- Set limits on execution time: You can limit how long each job or session runs. For details, see [Maximum execution time for a Qiskit Runtime job or session](max-execution-time). - Use only the necessary settings for error suppression, error mitigation, and optimization, because higher values can cause your jobs to run longer. See [Algorithm tuning options](advanced-runtime-options), [Configure runtime compilation](configure-runtime-compilation), and [Configure error mitigation](configure-error-mitigation) for details. diff --git a/docs/run/monitor-job.mdx b/docs/run/monitor-job.mdx index 1522f9a192..b09a97d26f 100644 --- a/docs/run/monitor-job.mdx +++ b/docs/run/monitor-job.mdx @@ -26,7 +26,7 @@ Use the job instance to check the job status or retrieve the results by calling Call `service.job(\)` to retrieve a job you previously submitted. If you don’t have the job ID, or if you want to retrieve multiple jobs at once; including jobs from retired systems, call `service.jobs()` with optional filters instead. See [QiskitRuntimeService.jobs](../api/qiskit-ibm-runtime/qiskit_ibm_runtime.QiskitRuntimeService#jobs). - service.jobs() returns only Qiskit® Runtime jobs. To retrieve other jobs, use [qiskit-ibm-provider](../api/qiskit-ibm-provider/qiskit_ibm_provider.IBMBackend#ibmbackend) instead. + service.jobs() returns only Qiskit Runtime jobs. To retrieve other jobs, use [qiskit-ibm-provider](../api/qiskit-ibm-provider/qiskit_ibm_provider.IBMBackend#ibmbackend) instead. ## Example diff --git a/docs/run/native-gates.mdx b/docs/run/native-gates.mdx index 549bc7fbee..94a21adb65 100644 --- a/docs/run/native-gates.mdx +++ b/docs/run/native-gates.mdx @@ -8,7 +8,7 @@ description: Summary of the native gates and operations supported by IBM Quantum Each [processor family](processor-types) has a native gate set. By default, the systems 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. -You can view the native gates and operations for a system either [with Qiskit®](#native-gates-with-qiskit) or on the IBM Quantum™ Platform [Compute resources page](#native-gates-on-platform). +You can view the native gates and operations for a system either [with Qiskit](#native-gates-with-qiskit) or on the IBM Quantum™ Platform [Compute resources page](#native-gates-on-platform). The terms native gates and basis gates are often used interchangeably. However, you can specify a different set of basis gates to use, while the native gate set never changes. For information about changing the basis gates, see the [Represent quantum computers](../transpile/representing_quantum_computers#basis-gates) topic. diff --git a/docs/run/primitives-examples.mdx b/docs/run/primitives-examples.mdx index 79810c6616..d528a78ed3 100644 --- a/docs/run/primitives-examples.mdx +++ b/docs/run/primitives-examples.mdx @@ -13,7 +13,7 @@ To ensure faster and more efficient results, as of 1 March 2024, circuits and ob - These examples all use the primitives from Qiskit® Runtime, but you could use the base primitives instead. + These examples all use the primitives from Qiskit Runtime, but you could use the base primitives instead. ## Estimator examples diff --git a/docs/run/primitives-get-started.mdx b/docs/run/primitives-get-started.mdx index c290deca1d..4303f08845 100644 --- a/docs/run/primitives-get-started.mdx +++ b/docs/run/primitives-get-started.mdx @@ -13,7 +13,7 @@ To ensure faster and more efficient results, as of 1 March 2024, circuits and ob - These examples all use the primitives from Qiskit® Runtime, but you could use the base primitives instead. + These examples all use the primitives from Qiskit Runtime, but you could use the base primitives instead. diff --git a/docs/run/primitives.mdx b/docs/run/primitives.mdx index 190c9fda32..6bf33f20db 100644 --- a/docs/run/primitives.mdx +++ b/docs/run/primitives.mdx @@ -21,7 +21,7 @@ As we move toward larger systems and more complex workflows, the focus shifts fr qubit signals to viewing quantum devices as systems that perform tasks we need. The two most common tasks quantum computers are used for are sampling quantum states and calculating expectation values. -These tasks motivated the design of *the first two Qiskit® primitives: Sampler and Estimator*. +These tasks motivated the design of *the first two Qiskit primitives: Sampler and Estimator*. In short, the computational model introduced by the Qiskit primitives moves quantum programming one step closer to where classical programming is today, where the focus is less on the hardware details and more on the results diff --git a/docs/run/quantum-serverless.mdx b/docs/run/quantum-serverless.mdx index 9deca28df5..2839312ce3 100644 --- a/docs/run/quantum-serverless.mdx +++ b/docs/run/quantum-serverless.mdx @@ -16,7 +16,7 @@ Try out the tutorials in [IBM Quantum Learning](https://learning.quantum.ibm.com ## Qiskit Patterns with Quantum Serverless -Creating utility-scale quantum applications generally requires a variety of compute resource requirements. You can use Quantum Serverless to easily submit quantum workflows for remote, managed execution. These quantum workflows can typically be implemented within a common pattern, called a Qiskit® Pattern. A Qiskit Pattern is an intuitive, repeatable set of steps for implementing a quantum computing workflow. +Creating utility-scale quantum applications generally requires a variety of compute resource requirements. You can use Quantum Serverless to easily submit quantum workflows for remote, managed execution. These quantum workflows can typically be implemented within a common pattern, called a Qiskit Pattern. A Qiskit Pattern is an intuitive, repeatable set of steps for implementing a quantum computing workflow. Steps in a Qiskit Pattern: diff --git a/docs/run/run-jobs-in-session.mdx b/docs/run/run-jobs-in-session.mdx index 2068e34b58..4650be3b68 100644 --- a/docs/run/run-jobs-in-session.mdx +++ b/docs/run/run-jobs-in-session.mdx @@ -10,7 +10,7 @@ There are several ways to set up and use [sessions](sessions). It is recommende ## Set up to use sessions -Before starting a session, you must [set up Qiskit® Runtime](../start/install) and initialize it as a service: +Before starting a session, you must [set up Qiskit Runtime](../start/install) and initialize it as a service: ``` python from qiskit_ibm_runtime import QiskitRuntimeService, Session, Sampler, Estimator diff --git a/docs/run/sessions.mdx b/docs/run/sessions.mdx index a30f8eb750..b9a28dc73e 100644 --- a/docs/run/sessions.mdx +++ b/docs/run/sessions.mdx @@ -6,7 +6,7 @@ description: An overview of Qiskit Runtime sessions and when to use them. # Introduction to Qiskit Runtime sessions -A session is a Qiskit® Runtime feature that lets you efficiently run multi-job iterative workloads on quantum computers. Using sessions helps avoid delays caused by queuing each job separately, which can be particularly useful for iterative tasks that require frequent communication between classical and quantum resources. +A session is a Qiskit Runtime feature that lets you efficiently run multi-job iterative workloads on quantum computers. Using sessions helps avoid delays caused by queuing each job separately, which can be particularly useful for iterative tasks that require frequent communication between classical and quantum resources. The queuing time does not decrease for the first job submitted within a session. Therefore, a session does not provide any benefits when running a single job. Additionally, sessions do not work on simulators because simulators do not have a queue. diff --git a/docs/run/system-information.mdx b/docs/run/system-information.mdx index 3e13ab4c13..4dc135c97f 100644 --- a/docs/run/system-information.mdx +++ b/docs/run/system-information.mdx @@ -41,7 +41,7 @@ The revision version number will increment for fixes that do not break the exist ## System configuration values -The following is a subset of system configuration values available in IBM Quantum and from [Qiskit®](/api/qiskit/qiskit.providers.models.BackendConfiguration). +The following is a subset of system configuration values available in IBM Quantum and from [Qiskit](/api/qiskit/qiskit.providers.models.BackendConfiguration). These values are shown on both the Systems and Simulators tabs of the [Compute resources page](https://quantum.ibm.com/services/resources?services=systems) and the details page for each system. diff --git a/docs/start/configure-qiskit-local.mdx b/docs/start/configure-qiskit-local.mdx index 55234d70c9..a86b9853fe 100644 --- a/docs/start/configure-qiskit-local.mdx +++ b/docs/start/configure-qiskit-local.mdx @@ -5,7 +5,7 @@ description: How to customize the configuration of a local Qiskit installation. --- # Configure Qiskit locally -After Qiskit® is installed and running, there are some optional steps you can take to change the default Qiskit behavior. +After Qiskit is installed and running, there are some optional steps you can take to change the default Qiskit behavior. ## User configuration file diff --git a/docs/start/index.mdx b/docs/start/index.mdx index 685760751c..65f93817cf 100644 --- a/docs/start/index.mdx +++ b/docs/start/index.mdx @@ -12,7 +12,7 @@ The quantum community has explored quantum computing on the cloud since 2016. N Through IBM Quantum™, you have access to performant and utility-scale (>100-qubit) quantum systems for your work, as well as scalable and flexible quantum software. Whether you try out a no-cost plan or run your programs through a pay-as-you-go or premium plan, you can start doing useful work with quantum computing now. -The sections at the core of our documentation are based on the stages of a typical quantum user’s journey: build quantum circuits and operators in Qiskit®, then transpile and run on quantum systems using Qiskit Runtime primitives, a simplified interface for circuit execution. By pairing Qiskit with Qiskit Runtime, you benefit from seamless circuit execution powered by advanced runtime compilation, error suppression, and error mitigation techniques. +The sections at the core of our documentation are based on the stages of a typical quantum user’s journey: build quantum circuits and operators in Qiskit, then transpile and run on quantum systems using Qiskit Runtime primitives, a simplified interface for circuit execution. By pairing Qiskit with Qiskit Runtime, you benefit from seamless circuit execution powered by advanced runtime compilation, error suppression, and error mitigation techniques. If you’re just getting started with IBM Quantum, you are in the right place. Use the topics in this section to get ready, then proceed to [Build](../build) to create your first quantum circuit. Keep working through the sections in order, following the tabs at the top of this page. diff --git a/docs/start/install-qiskit-source.mdx b/docs/start/install-qiskit-source.mdx index 31a5a3d7bb..ac317cf291 100644 --- a/docs/start/install-qiskit-source.mdx +++ b/docs/start/install-qiskit-source.mdx @@ -5,7 +5,7 @@ description: Learn how to install the development version of Qiskit. --- # Install Qiskit and Qiskit Runtime from source -Installing Qiskit® from source allows you to access the current development version, instead of using the version in the Python Package Index (PyPI) repository. This lets you inspect and extend the latest version of the Qiskit code more efficiently. +Installing Qiskit from source allows you to access the current development version, instead of using the version in the Python Package Index (PyPI) repository. This lets you inspect and extend the latest version of the Qiskit code more efficiently. ## Create and activate a new virtual environment diff --git a/docs/start/install.mdx b/docs/start/install.mdx index b3fe72b916..45b7a3cf68 100644 --- a/docs/start/install.mdx +++ b/docs/start/install.mdx @@ -6,7 +6,7 @@ description: Install and set up Qiskit and Qiskit Runtime on various operating s # Install and set up Qiskit -Whether you will work locally or in a cloud environment, the first step for all users is to install Qiskit®. For those wanting to run on a real system, your next step is to choose one of two channels in order to access IBM Quantum™ systems: IBM Quantum Platform or IBM Cloud®. +Whether you will work locally or in a cloud environment, the first step for all users is to install Qiskit. For those wanting to run on a real system, your next step is to choose one of two channels in order to access IBM Quantum™ systems: IBM Quantum Platform or IBM Cloud®. (If you are installing Qiskit for the first time, skip ahead to the [Install and set up](#local) section. This notice is relevant only to users who have installed Qiskit previously.) diff --git a/docs/start/setup-channel.mdx b/docs/start/setup-channel.mdx index dd86e0f28d..c3d2f118ee 100644 --- a/docs/start/setup-channel.mdx +++ b/docs/start/setup-channel.mdx @@ -11,7 +11,7 @@ You can access IBM Quantum™ systems by using the IBM Quantum Platform or I IBM Quantum Platform has Open (free access) and Premium (enterprise subscription) plans. See [IBM Quantum access plans](https://www.ibm.com/quantum/access-plans) for details. -You can make requests locally (on your laptop or other device) using the `qiskit-ibm-runtime` client or use a cloud-based environment, such as [IBM Quantum Lab](https://lab.quantum.ibm.com) (a Jupyter Notebook environment) or [IBM Quantum Composer](https://quantum.ibm.com/composer/files/new) (a virtual circuit composer). To make requests from a local environment, you need to [install and set up Qiskit® with the Qiskit Runtime Client](install#local) and [set up to use IBM Quantum Platform.](#iqp) +You can make requests locally (on your laptop or other device) using the `qiskit-ibm-runtime` client or use a cloud-based environment, such as [IBM Quantum Lab](https://lab.quantum.ibm.com) (a Jupyter Notebook environment) or [IBM Quantum Composer](https://quantum.ibm.com/composer/files/new) (a virtual circuit composer). To make requests from a local environment, you need to [install and set up Qiskit with the Qiskit Runtime Client](install#local) and [set up to use IBM Quantum Platform.](#iqp) [IBM Quantum Lab](https://lab.quantum.ibm.com) and [IBM Quantum Composer](https://quantum.ibm.com/composer/files/new) are self-contained tools and require no setup. diff --git a/docs/support.mdx b/docs/support.mdx index b6bdaca90e..4d3a527311 100644 --- a/docs/support.mdx +++ b/docs/support.mdx @@ -13,7 +13,7 @@ Members of the IBM Quantum™ Network can reach out to IBM Quantum Support i ## Qiskit -For help with Qiskit®, access our Slack community: [Qiskit Slack](https://qisk.it/join-slack). +For help with Qiskit, access our Slack community: [Qiskit Slack](https://qisk.it/join-slack). ## Qiskit Runtime diff --git a/docs/transpile/ai-transpiler-passes.mdx b/docs/transpile/ai-transpiler-passes.mdx index 8646ed6df1..d05ad59df6 100644 --- a/docs/transpile/ai-transpiler-passes.mdx +++ b/docs/transpile/ai-transpiler-passes.mdx @@ -5,7 +5,7 @@ description: What are the AI transpiler passes and how to use them # AI transpiler passes ​ -The AI-powered transpiler passes are experimental passes that work as a drop-in replacement of "traditional" Qiskit® passes for some transpiling tasks. They often produce better results than existing heuristic algorithms (such as lower depth and CNOT count), but are also much faster than optimization algorithms such as Boolean satisfiability solvers. The AI transpiler passes run on the cloud and are available to IBM Quantum™ Premium Plan users. +The AI-powered transpiler passes are experimental passes that work as a drop-in replacement of "traditional" Qiskit passes for some transpiling tasks. They often produce better results than existing heuristic algorithms (such as lower depth and CNOT count), but are also much faster than optimization algorithms such as Boolean satisfiability solvers. The AI transpiler passes run on the cloud and are available to IBM Quantum™ Premium Plan users. diff --git a/docs/transpile/custom-transpiler-pass.ipynb b/docs/transpile/custom-transpiler-pass.ipynb index e7d53d7b4d..dadf05011e 100644 --- a/docs/transpile/custom-transpiler-pass.ipynb +++ b/docs/transpile/custom-transpiler-pass.ipynb @@ -7,7 +7,7 @@ "source": [ "# Write a custom transpiler pass\n", "\n", - "Qiskit® lets you create custom transpilation passes and run them in the `PassManager` object or add them to a `StagedPassManager`. Here we will demonstrate how to write a transpiler pass, focusing on building a pass that performs [Pauli twirling](https://arxiv.org/abs/quant-ph/0606161) on the noisy quantum gates in a quantum circuit. This example uses the DAG, which is the object manipulated by the `TransformationPass` type of pass." + "Qiskit lets you create custom transpilation passes and run them in the `PassManager` object or add them to a `StagedPassManager`. Here we will demonstrate how to write a transpiler pass, focusing on building a pass that performs [Pauli twirling](https://arxiv.org/abs/quant-ph/0606161) on the noisy quantum gates in a quantum circuit. This example uses the DAG, which is the object manipulated by the `TransformationPass` type of pass." ] }, { diff --git a/docs/transpile/defaults-and-configuration-options.mdx b/docs/transpile/defaults-and-configuration-options.mdx index 6a09bdc853..ba6b05ba65 100644 --- a/docs/transpile/defaults-and-configuration-options.mdx +++ b/docs/transpile/defaults-and-configuration-options.mdx @@ -208,7 +208,7 @@ qiskit.compiler.transpile(unitary_synthesis_method='default', translation_method - Learn how to [Set the optimization level](set-optimization). - Review more [Commonly used parameters](common-parameters). - - Learn how to [Set the optimization level when using Qiskit® Runtime.](../run/advanced-runtime-options) + - Learn how to [Set the optimization level when using Qiskit Runtime.](../run/advanced-runtime-options) - Visit the [Transpile with pass managers](transpile-with-pass-managers) topic. - For examples, see [Representing quantum computers.](representing_quantum_computers) - Try the [Submit transpiled circuits](https://learning.quantum.ibm.com/tutorial/submit-transpiled-circuits) tutorial. diff --git a/docs/transpile/index.mdx b/docs/transpile/index.mdx index f7f397d7f2..586aa56b68 100644 --- a/docs/transpile/index.mdx +++ b/docs/transpile/index.mdx @@ -7,7 +7,7 @@ description: Introduction to transpiling quantum circuits in Qiskit. # Introduction -Transpilation is the process of rewriting a given input circuit to match the topology of a specific quantum device, and optimize the circuit instructions for execution on noisy quantum systems. This documentation covers the tooling and workflows for local transpilation available to all Qiskit® users, as well as for the cloud-based [Qiskit transpiler service](qiskit-transpiler-service) available to Premium Plan users. If you're using primitives and are only interested in the default transpilation options provided by the Qiskit Runtime service, read the [Configure runtime compilation for Qiskit Runtime](../run/configure-runtime-compilation) topic. +Transpilation is the process of rewriting a given input circuit to match the topology of a specific quantum device, and optimize the circuit instructions for execution on noisy quantum systems. This documentation covers the tooling and workflows for local transpilation available to all Qiskit users, as well as for the cloud-based [Qiskit transpiler service](qiskit-transpiler-service) available to Premium Plan users. If you're using primitives and are only interested in the default transpilation options provided by the Qiskit Runtime service, read the [Configure runtime compilation for Qiskit Runtime](../run/configure-runtime-compilation) topic. A central component of Qiskit, the transpiler is designed for modularity and extensibility. Its central goal is to write new circuit transformations (known as transpiler **passes**), and combine them with other existing passes, greatly reducing the depth and complexity of quantum circuits. Which passes are chained together and in which order has a major effect on the final outcome. This pipeline is determined by the [`PassManager`](/api/qiskit/qiskit.transpiler.PassManager) and [`StagedPassManager`](/api/qiskit/qiskit.transpiler.StagedPassManager) objects. The `StagedPassManager` orchestrates the execution of one or more `PassManagers` and determines the order in which they are executed, while the `PassManager` object is merely a collection of one or more passes. Think of the `StagedPassManager` as the conductor in an orchestra, the `PassManagers` as the different instrument sections, and the `Pass`es as the individual musicians. In this way, you can compose hardware-efficient quantum circuits that let you execute utility-scale work while keeping noise manageable. diff --git a/docs/transpile/qiskit-transpiler-service.mdx b/docs/transpile/qiskit-transpiler-service.mdx index a216c5ec38..500393b68f 100644 --- a/docs/transpile/qiskit-transpiler-service.mdx +++ b/docs/transpile/qiskit-transpiler-service.mdx @@ -5,7 +5,7 @@ description: What is the Qiskit transpiler service and how to use it --- # Transpile circuits remotely with the Qiskit transpiler service -The Qiskit® transpiler service provides transpilation capabilities on the cloud. In addition to the local Qiskit transpiler capabilities, your transpilation tasks can benefit from both IBM Quantum™ cloud resources and AI-powered transpiler passes. +The Qiskit transpiler service provides transpilation capabilities on the cloud. In addition to the local Qiskit transpiler capabilities, your transpilation tasks can benefit from both IBM Quantum™ cloud resources and AI-powered transpiler passes. The Qiskit transpiler service offers a Python library to seamlessly integrate this service and its capabilities into your current Qiskit patterns and workflows. diff --git a/docs/transpile/representing_quantum_computers.mdx b/docs/transpile/representing_quantum_computers.mdx index dfdaf3bf7f..78a8e82a60 100644 --- a/docs/transpile/representing_quantum_computers.mdx +++ b/docs/transpile/representing_quantum_computers.mdx @@ -70,7 +70,7 @@ qc_t_cm_lv0.draw('mpl', style='iqp', idle_wires=False) ``` ![Ansatz transpiled to coupling map with optimization level 0](/images/transpile/representing_quantum_computers/qc_t_cm_lv0.png "Circuit transpiled with a coupling map") -As shown above, several SWAP gates were inserted (each consisting of three CX gates), which will cause a lot of errors on current devices. To see which qubits are selected on the actual qubit topology, use `plot_circuit_layout` from Qiskit® Visualizations: +As shown above, several SWAP gates were inserted (each consisting of three CX gates), which will cause a lot of errors on current devices. To see which qubits are selected on the actual qubit topology, use `plot_circuit_layout` from Qiskit Visualizations: ```python from qiskit.visualization import plot_circuit_layout diff --git a/docs/transpile/set-optimization.mdx b/docs/transpile/set-optimization.mdx index a2ffe09023..ff0bf60204 100644 --- a/docs/transpile/set-optimization.mdx +++ b/docs/transpile/set-optimization.mdx @@ -14,7 +14,7 @@ Higher optimization levels generate more optimized circuits at the expense of lo - `optimization_level=0`: Trivial optimization, which maps the circuit to the system with no explicit optimization. - `optimization_level=1-3`: Increasingly complex optimization, with heuristic algorithms that are used to find a layout and insert SWAP gates, with the goal of improving the overall performance of the circuit. The number of iterations that these algorithms run increases with higher optimization levels. -Because finding the best layout is an NP-hard problem, it is the most time-consuming part of the transpilation process. However, Qiskit® uses stochastic algorithms that have been refactored into Rust, resulting in significant speedup. Therefore, optimization levels 1-3 all use the same layout algorithms. There are some slight differences in how the circuits are translated into basis gates, as described in the following table: +Because finding the best layout is an NP-hard problem, it is the most time-consuming part of the transpilation process. However, Qiskit uses stochastic algorithms that have been refactored into Rust, resulting in significant speedup. Therefore, optimization levels 1-3 all use the same layout algorithms. There are some slight differences in how the circuits are translated into basis gates, as described in the following table: diff --git a/docs/transpile/transpile-with-pass-managers.ipynb b/docs/transpile/transpile-with-pass-managers.ipynb index d8897c1dc3..9692f9ca49 100644 --- a/docs/transpile/transpile-with-pass-managers.ipynb +++ b/docs/transpile/transpile-with-pass-managers.ipynb @@ -17,7 +17,7 @@ "source": [ "## What is a (staged) pass manager?\n", "\n", - "In the context of Qiskit®, transpilation refers to the process of transforming an input circuit into a form that is suitable for execution on a quantum device. Transpilation typically occurs in a sequence of steps called transpiler passes. The circuit is processed by each transpiler pass in sequence, with the output of one pass becoming the input to the next. For example, one pass could go through the circuit and merge all consecutive sequences of single-qubit gates, and then the next pass could synthesize these gates into the basis set of the target device. The transpiler passes included with Qiskit are located in the [qiskit.transpiler.passes](/api/qiskit/transpiler_passes) module.\n", + "In the context of Qiskit, transpilation refers to the process of transforming an input circuit into a form that is suitable for execution on a quantum device. Transpilation typically occurs in a sequence of steps called transpiler passes. The circuit is processed by each transpiler pass in sequence, with the output of one pass becoming the input to the next. For example, one pass could go through the circuit and merge all consecutive sequences of single-qubit gates, and then the next pass could synthesize these gates into the basis set of the target device. The transpiler passes included with Qiskit are located in the [qiskit.transpiler.passes](/api/qiskit/transpiler_passes) module.\n", "\n", "A pass manager is an object that stores a list of transpiler passes and can execute them on a circuit. Create a pass manager by initializing a [`PassManager`](/api/qiskit/qiskit.transpiler.PassManager) with a list of transpiler passes. To run the transpilation on a circuit, call the [run](/api/qiskit/qiskit.transpiler.PassManager#run) method with a circuit as input.\n", "\n", diff --git a/docs/transpile/transpiler-stages.ipynb b/docs/transpile/transpiler-stages.ipynb index bd5b16ac4c..2bdf31e0da 100644 --- a/docs/transpile/transpiler-stages.ipynb +++ b/docs/transpile/transpiler-stages.ipynb @@ -7,7 +7,7 @@ "source": [ "# Transpiler stages\n", "\n", - "This page describes the stages of prebuilt transpilation pipeline in Qiskit®. There are six stages:\n", + "This page describes the stages of prebuilt transpilation pipeline in Qiskit. There are six stages:\n", "\n", "1. `init`\n", "2. `layout`\n", diff --git a/docs/verify/building_noise_models.ipynb b/docs/verify/building_noise_models.ipynb index 586c43e173..e3887ea5a4 100644 --- a/docs/verify/building_noise_models.ipynb +++ b/docs/verify/building_noise_models.ipynb @@ -7,7 +7,7 @@ "source": [ "# Build noise models\n", "\n", - "This page shows how to use the Qiskit® Aer [`noise`](https://qiskit.org/ecosystem/aer/apidocs/aer_noise.html) module to build noise models for simulating quantum circuits in the presence of errors. This is useful for emulating noisy quantum processors and for studying the effects of noise on the execution of quantum algorithms." + "This page shows how to use the Qiskit Aer [`noise`](https://qiskit.org/ecosystem/aer/apidocs/aer_noise.html) module to build noise models for simulating quantum circuits in the presence of errors. This is useful for emulating noisy quantum processors and for studying the effects of noise on the execution of quantum algorithms." ] }, { @@ -52,7 +52,7 @@ "source": [ "## Qiskit Aer `noise` module\n", "\n", - "The Qiskit® Aer `noise` module contains Python classes to build customized noise models for simulation. There are three key classes:\n", + "The Qiskit Aer `noise` module contains Python classes to build customized noise models for simulation. There are three key classes:\n", "\n", "1. The `NoiseModel` class which stores a noise model used for noisy simulation.\n", "2. The `QuantumError` class which describes CPTP gate errors. These can be applied:\n", diff --git a/docs/verify/cloud-based-simulators.mdx b/docs/verify/cloud-based-simulators.mdx index abc445992b..5b497ea3cf 100644 --- a/docs/verify/cloud-based-simulators.mdx +++ b/docs/verify/cloud-based-simulators.mdx @@ -5,7 +5,7 @@ description: Overview of available IBM Quantum cloud-based simulators # Available IBM Quantum simulators -This page gives details about the IBM Quantum™ cloud-based simulators. For information about the Qiskit® built-in simulator, see the [Python-based simulators page in the API reference.](/api/qiskit/providers_basic_provider) You can also use the [Qiskit reference primitives](simulate-with-qiskit-primitives) for local statevector simulation. +This page gives details about the IBM Quantum™ cloud-based simulators. For information about the Qiskit built-in simulator, see the [Python-based simulators page in the API reference.](/api/qiskit/providers_basic_provider) You can also use the [Qiskit reference primitives](simulate-with-qiskit-primitives) for local statevector simulation. IBM Quantum features a collection of high-performance simulators for prototyping quantum circuits and algorithms. diff --git a/docs/verify/index.mdx b/docs/verify/index.mdx index 06b72ea57b..e9b4dd21d7 100644 --- a/docs/verify/index.mdx +++ b/docs/verify/index.mdx @@ -11,7 +11,7 @@ Because the cost of classically simulating quantum circuits scales exponentially - Test smaller versions of the circuits that can be simulated classically. - Modify the circuits so that they become classically simulable and test these modified circuits. -Stabilizer circuits are a useful tool for accomplishing this latter goal. These are a restricted class of quantum circuits that can be efficiently simulated classically. Specialized simulators can easily simulate stabilizer circuits with thousands of qubits. See [Efficient simulation of stabilizer circuits with Qiskit® Aer primitives](stabilizer-circuit-simulation) for an overview of stabilizer circuits and how to simulate them efficiently. +Stabilizer circuits are a useful tool for accomplishing this latter goal. These are a restricted class of quantum circuits that can be efficiently simulated classically. Specialized simulators can easily simulate stabilizer circuits with thousands of qubits. See [Efficient simulation of stabilizer circuits with Qiskit Aer primitives](stabilizer-circuit-simulation) for an overview of stabilizer circuits and how to simulate them efficiently. For general quantum circuits, the following tools are available for you to verify your quantum programs: diff --git a/docs/verify/simulate-with-qiskit-aer.ipynb b/docs/verify/simulate-with-qiskit-aer.ipynb index e5dbc85b16..e248ccd195 100644 --- a/docs/verify/simulate-with-qiskit-aer.ipynb +++ b/docs/verify/simulate-with-qiskit-aer.ipynb @@ -7,7 +7,7 @@ "source": [ "# Exact and noisy simulation with Qiskit Aer primitives\n", "\n", - "[Exact simulation with Qiskit® primitives](simulate-with-qiskit-primitives) demonstrates how to use the reference primitives included with Qiskit to perform exact simulation of quantum circuits. Currently existing quantum processors suffer from errors, or noise, so the results of an exact simulation do not necessarily reflect the results you would expect when running circuits on real hardware. While the reference primitives in Qiskit do not support modeling noise, [Qiskit Aer](https://qiskit.org/ecosystem/aer/) includes implementations of the primitives that do support modeling noise. Qiskit Aer is a high-performance quantum circuit simulator that you can use in place of the reference primitives for better performance and more features. It is part of the [Qiskit Ecosystem](https://qiskit.github.io/ecosystem/). In this article, we demonstrate the use of Qiskit Aer primitives for exact and noisy simulation.\n", + "[Exact simulation with Qiskit primitives](simulate-with-qiskit-primitives) demonstrates how to use the reference primitives included with Qiskit to perform exact simulation of quantum circuits. Currently existing quantum processors suffer from errors, or noise, so the results of an exact simulation do not necessarily reflect the results you would expect when running circuits on real hardware. While the reference primitives in Qiskit do not support modeling noise, [Qiskit Aer](https://qiskit.org/ecosystem/aer/) includes implementations of the primitives that do support modeling noise. Qiskit Aer is a high-performance quantum circuit simulator that you can use in place of the reference primitives for better performance and more features. It is part of the [Qiskit Ecosystem](https://qiskit.github.io/ecosystem/). In this article, we demonstrate the use of Qiskit Aer primitives for exact and noisy simulation.\n", "\n", "Let's create an example circuit on eight qubits." ] diff --git a/docs/verify/simulate-with-qiskit-primitives.mdx b/docs/verify/simulate-with-qiskit-primitives.mdx index 7b2e9b9780..ad8bc4600b 100644 --- a/docs/verify/simulate-with-qiskit-primitives.mdx +++ b/docs/verify/simulate-with-qiskit-primitives.mdx @@ -5,7 +5,7 @@ description: How to perform exact simulation of quantum circuits using primitive # Exact simulation with Qiskit primitives -The reference primitives in Qiskit® can perform local statevector simulations, which is useful for quickly prototyping algorithms. +The reference primitives in Qiskit can perform local statevector simulations, which is useful for quickly prototyping algorithms. The `Estimator` primitive can compute an expectation value, and the `Sampler` primitive can compute circuit output probabilities. diff --git a/docs/verify/stabilizer-circuit-simulation.ipynb b/docs/verify/stabilizer-circuit-simulation.ipynb index 9f9c42f794..b21cd8b346 100644 --- a/docs/verify/stabilizer-circuit-simulation.ipynb +++ b/docs/verify/stabilizer-circuit-simulation.ipynb @@ -7,7 +7,7 @@ "source": [ "# Efficient simulation of stabilizer circuits with Qiskit Aer primitives\n", "\n", - "This page shows how to use Qiskit® Aer primitives to efficiently simulate stabilizer circuits, including those subject to Pauli noise.\n", + "This page shows how to use Qiskit Aer primitives to efficiently simulate stabilizer circuits, including those subject to Pauli noise.\n", "\n", "Stabilizer circuits, also known as Clifford circuits, are an important restricted class of quantum circuits that can be efficiently simulated classically. There are several equivalent ways to define stabilizer circuits. One definition is that a stabilizer circuit is a quantum circuit that consists solely of the following gates:\n", "\n", diff --git a/docs/verify/using-ibm-quantum-simulators.mdx b/docs/verify/using-ibm-quantum-simulators.mdx index 9b3742469b..a74eeee298 100644 --- a/docs/verify/using-ibm-quantum-simulators.mdx +++ b/docs/verify/using-ibm-quantum-simulators.mdx @@ -6,7 +6,7 @@ description: Set up ibmq_qasm_simulator and map a basic noise model for an IBM Q # Using IBM Quantum cloud-based simulators -Set up ``ibmq_qasm_simulator`` and map a basic noise model for an IBM Quantum™ hardware device in Qiskit® Runtime, then use this noise model to perform noisy simulations of ``QuantumCircuits`` by using ``Sampler`` and ``Estimator`` to study the effects of errors that occur on real devices. +Set up ``ibmq_qasm_simulator`` and map a basic noise model for an IBM Quantum™ hardware device in Qiskit Runtime, then use this noise model to perform noisy simulations of ``QuantumCircuits`` by using ``Sampler`` and ``Estimator`` to study the effects of errors that occur on real devices. ## Set up your local development environment diff --git a/translations/ja/api/migration-guides/qiskit-runtime-from-provider.mdx b/translations/ja/api/migration-guides/qiskit-runtime-from-provider.mdx index 634db485cd..626e234277 100644 --- a/translations/ja/api/migration-guides/qiskit-runtime-from-provider.mdx +++ b/translations/ja/api/migration-guides/qiskit-runtime-from-provider.mdx @@ -5,7 +5,7 @@ description: How to migrate `backend.run()` from Qiskit IBM Provider to Qiskit I # Migrate `backend.run()` from `qiskit_ibm_provider` to `qiskit_ibm_runtime` -The Qiskit® Runtime interface includes two packages: +The Qiskit Runtime interface includes two packages: Qiskit IBM Provider (the [`qiskit_ibm_provider`](../qiskit-ibm-provider) package) and Qiskit IBM Runtime (the [`qiskit_ibm_runtime`](../qiskit-ibm-runtime) package). Until now, primitives (`Sampler` and `Estimator`)