Qiskit

Qiskit is an open-source SDK for working with quantum computers at the level of extended quantum circuits, operators, and primitives. This library is the core component of Qiskit, which contains the building blocks for creating and working with quantum circuits, quantum operators, and primitive functions (Sampler and Estimator). It also contains a transpiler that supports optimizing quantum circuits, and a quantum information toolbox for creating advanced operators. Qiskit provides two public APIs: a Python API and a C API. The Python API is the primary interface and prior to Qiskit 2.0 was the only public API available for Qiskit. The C API is designed to provide direct access to Qiskit's internal data model (which is written in Rust). The C API can be consumed as either a shared library ( libqiskit.so ) for standalone use, or from its embedding in the qiskit Python package for writing Python extension modules. Pip will handle all dependencies automatically and you will always install the latest (and well-tested) version. To install Qiskit as a standalone C library the only option is currently to build Qiskit from source. This requires having the Rust compiler installed. To simplify building having GNU Make installed is recommended. With these requirements installed you can run: Which will compile the C library and put the dist/c directory in the root of the repository which will contain the shared library and C headers for the library. You can refer to the documentation on installing the C API for more details and how to use the built library. Now that Qiskit is installed, it's time to begin working with Qiskit. We will use the Python interface to demonstrate creating a quantum program. The essential parts of a quantum program are: 1. Define and build a quantum circuit that represents the quantum state 2. Define the classical output by measurements or a set of observable operators 3. Depending on the output, use the Sampler primitive to sample outcomes or the Estimator primitive to estimate expectation values. Once you've made your first quantum circuit, choose which primitive you will use. Starting with the Sampler, we use measure all(inplace=False) to get a copy of the circuit in which all the qubits are measured: Qiskit provides an abstraction layer that lets users run quantum circuits on hardware from any vendor that provides a compatible interface. The best way to use Qiskit is with a runtime environment that provides optimized implementations of Sampler and Estimator for a given hardware platform. This runtime may involve using pre- and post-processing, such as optimized transpiler passes with error suppression, error mitigation, and, eventually, error correction built in. A runtime implements the qiskit.primitives.BaseSamplerV2 and qiskit.primitives.BaseEstimatorV2 interfaces. For example, some packages that provide implementations of a runtime primitive implementation are: Qiskit also provides a lower-level abstract interface for describing quantum backends. This interface, located in qiskit.providers , defines an abstract BackendV2 class that providers can implement to represent their hardware or simulators to Qiskit. The backend class includes a common interface for executing circuits on the backends; however, in this interface each provider may perform different types of pre- and post-processing and return outcomes that are vendor-defined. Some examples of published provider packages that interface with real hardware are: You can refer to the documentation of these packages for further instructions on how to get access and use these systems. We use GitHub issues for tracking requests and bugs. Please join the Qiskit Slack community for discussion, comments, and questions. For questions related to running or using Qiskit, Stack Overflow has a qiskit . For questions on quantum computing with Qiskit, use the qiskit tag in the Quantum Computing Stack Exchange (please, read first the guidelines on how to as