From 81f024ec90679f4170da7fcdc13f81746f8e0729 Mon Sep 17 00:00:00 2001 From: Eric Arellano <14852634+Eric-Arellano@users.noreply.github.com> Date: Mon, 14 Oct 2024 14:40:13 -0400 Subject: [PATCH] Fix more external links --- docs/api/qiskit/0.46/qiskit.algorithms.VQE.mdx | 2 +- docs/api/qiskit/release-notes/0.19.mdx | 6 +++--- docs/api/qiskit/release-notes/0.20.mdx | 14 +++++++------- docs/api/qiskit/release-notes/0.23.mdx | 10 +++++----- docs/api/qiskit/release-notes/0.25.mdx | 12 ++++++------ docs/api/qiskit/release-notes/0.33.mdx | 6 +++--- docs/api/qiskit/release-notes/0.37.mdx | 2 +- scripts/js/lib/links/ignores.ts | 1 + 8 files changed, 27 insertions(+), 26 deletions(-) diff --git a/docs/api/qiskit/0.46/qiskit.algorithms.VQE.mdx b/docs/api/qiskit/0.46/qiskit.algorithms.VQE.mdx index fe687c30cf7..267a830e3b5 100644 --- a/docs/api/qiskit/0.46/qiskit.algorithms.VQE.mdx +++ b/docs/api/qiskit/0.46/qiskit.algorithms.VQE.mdx @@ -19,7 +19,7 @@ python_api_name: qiskit.algorithms.VQE An instance of VQE requires defining two algorithmic sub-components: a trial state (a.k.a. ansatz) which is a `QuantumCircuit`, and one of the classical [`optimizers`](qiskit.algorithms.optimizers#module-qiskit.algorithms.optimizers "qiskit.algorithms.optimizers"). The ansatz is varied, via its set of parameters, by the optimizer, such that it works towards a state, as determined by the parameters applied to the ansatz, that will result in the minimum expectation value being measured of the input operator (Hamiltonian). - An optional array of parameter values, via the *initial\_point*, may be provided as the starting point for the search of the minimum eigenvalue. This feature is particularly useful such as when there are reasons to believe that the solution point is close to a particular point. As an example, when building the dissociation profile of a molecule, it is likely that using the previous computed optimal solution as the starting initial point for the next interatomic distance is going to reduce the number of iterations necessary for the variational algorithm to converge. It provides an [initial point tutorial](https://github.com/Qiskit/qiskit-tutorials-community/blob/master/chemistry/h2_vqe_initial_point.ipynb) detailing this use case. + An optional array of parameter values, via the *initial\_point*, may be provided as the starting point for the search of the minimum eigenvalue. This feature is particularly useful such as when there are reasons to believe that the solution point is close to a particular point. As an example, when building the dissociation profile of a molecule, it is likely that using the previous computed optimal solution as the starting initial point for the next interatomic distance is going to reduce the number of iterations necessary for the variational algorithm to converge. It provides an [initial point tutorial](https://github.com/qiskit-community/qiskit-community-tutorials/blob/51cb790aebbe1015f22c0957a108ff66eb1c9136/chemistry/h2_vqe_initial_point.ipynb) detailing this use case. The length of the *initial\_point* list value must match the number of the parameters expected by the ansatz being used. If the *initial\_point* is left at the default of `None`, then VQE will look to the ansatz for a preferred value, based on its given initial state. If the ansatz returns `None`, then a random point will be generated within the parameter bounds set, as per above. If the ansatz provides `None` as the lower bound, then VQE will default it to $-2\pi$; similarly, if the ansatz returns `None` as the upper bound, the default value will be $2\pi$. diff --git a/docs/api/qiskit/release-notes/0.19.mdx b/docs/api/qiskit/release-notes/0.19.mdx index 0c9bb18abc6..6e06c215b98 100644 --- a/docs/api/qiskit/release-notes/0.19.mdx +++ b/docs/api/qiskit/release-notes/0.19.mdx @@ -161,7 +161,7 @@ VQE expectation computation with Aer qasm\_simulator now defaults to a computati * [cvxpy](https://github.com/cvxgrp/cvxpy/) is now in the requirements list as a dependency for qiskit-aqua. It is used for the quadratic program solver which is used as part of the `qiskit.aqua.algorithms.QSVM`. Previously `cvxopt` was an optional dependency that needed to be installed to use this functionality. This is no longer required as cvxpy will be installed with qiskit-aqua. * For state tomography run as part of `qiskit.aqua.algorithms.HHL` with a QASM backend the tomography fitter function `qiskit.ignis.verification.StateTomographyFitter.fit()` now gets called explicitly with the method set to `lstsq` to always use the least-squares fitting. Previously it would opportunistically try to use the `cvx` fitter if `cvxpy` were installed. But, the `cvx` fitter depends on a specifically configured `cvxpy` installation with an SDP solver installed as part of `cvxpy` which is not always present in an environment with `cvxpy` installed. -* The VQE expectation computation using qiskit-aer’s `qiskit.providers.aer.extensions.SnapshotExpectationValue` instruction is not enabled by default anymore. This was changed to be the default in 0.7.0 because it is significantly faster, but it led to unexpected ideal results without shot noise (see [#1013](https://github.com/Qiskit/qiskit-aqua/issues/1013) for more details). The default has now changed back to match user expectations. Using the faster expectation computation is now opt-in by setting the new `include_custom` kwarg to `True` on the `qiskit.aqua.algorithms.VQE` constructor. +* The VQE expectation computation using qiskit-aer’s `qiskit.providers.aer.extensions.SnapshotExpectationValue` instruction is not enabled by default anymore. This was changed to be the default in 0.7.0 because it is significantly faster, but it led to unexpected ideal results without shot noise (see [#1013](https://github.com/qiskit-community/qiskit-aqua/issues/1013) for more details). The default has now changed back to match user expectations. Using the faster expectation computation is now opt-in by setting the new `include_custom` kwarg to `True` on the `qiskit.aqua.algorithms.VQE` constructor. @@ -482,11 +482,11 @@ The Qiskit Aqua 0.7.0 release introduces a lot of new functionality along with a ##### Optimization module -The `` qiskit.optimization` `` module now offers functionality for modeling and solving quadratic programs. It provides various near-term quantum and conventional algorithms, such as the `MinimumEigenOptimizer` (covering e.g. `VQE` or `QAOA`) or `CplexOptimizer`, as well as a set of converters to translate between different problem representations, such as `QuadraticProgramToQubo`. See the [changelog](https://github.com/Qiskit/qiskit-aqua/#migration-guide) for a list of the added features. +The `` qiskit.optimization` `` module now offers functionality for modeling and solving quadratic programs. It provides various near-term quantum and conventional algorithms, such as the `MinimumEigenOptimizer` (covering e.g. `VQE` or `QAOA`) or `CplexOptimizer`, as well as a set of converters to translate between different problem representations, such as `QuadraticProgramToQubo`. See the [changelog](https://github.com/qiskit-community/qiskit-aqua/#migration-guide) for a list of the added features. ##### Operator flow -The operator logic provided in `` qiskit.aqua.operators` `` was completely refactored and is now a full set of tools for constructing physically-intuitive quantum computations. It contains state functions, operators and measurements and internally relies on Terra’s Operator objects. Computing expectation values and evolutions was heavily simplified and objects like the `ExpectationFactory` produce the suitable, most efficient expectation algorithm based on the Operator input type. See the [changelog](https://github.com/Qiskit/qiskit-aqua/#migration-guide) for a overview of the added functionality. +The operator logic provided in `` qiskit.aqua.operators` `` was completely refactored and is now a full set of tools for constructing physically-intuitive quantum computations. It contains state functions, operators and measurements and internally relies on Terra’s Operator objects. Computing expectation values and evolutions was heavily simplified and objects like the `ExpectationFactory` produce the suitable, most efficient expectation algorithm based on the Operator input type. See the [changelog](https://github.com/qiskit-community/qiskit-aqua/#migration-guide) for a overview of the added functionality. ##### Native circuits diff --git a/docs/api/qiskit/release-notes/0.20.mdx b/docs/api/qiskit/release-notes/0.20.mdx index 815fbd19341..5524e0a5150 100644 --- a/docs/api/qiskit/release-notes/0.20.mdx +++ b/docs/api/qiskit/release-notes/0.20.mdx @@ -754,7 +754,7 @@ The main change made in this release is a refactor of the Randomized Benchmarkin * The `qiskit.ignis.verification.randomized_benchmarking.randomized_benchmarking_seq()` function is now using the updated Clifford class [`Clifford`](/api/qiskit/0.45/qiskit.quantum_info.Clifford "qiskit.quantum_info.Clifford") and the updated CNOT-Dihedral class `qiskit.ignis.verification.randomized_benchmarking.CNOTDihedral` to construct its output instead of using pre-generated group tables for the Clifford and CNOT-Dihedral group elements, which were stored in pickle files. This may result in subtle differences from the output from the previous version. * A new requirement [scikit-learn](https://scikit-learn.org/stable/) has been added to the requirements list. This dependency was added in the 0.3.0 release but wasn’t properly exposed as a dependency in that release. This would lead to an `ImportError` if the `qiskit.ignis.measurement.discriminator.iq_discriminators` module was imported. This is now correctly listed as a dependency so that `scikit-learn` will be installed with qiskit-ignis. * The `qiskit.ignis.verification.qv_circuits()` function is now using the circuit library class [`QuantumVolume`](/api/qiskit/0.45/qiskit.circuit.library.QuantumVolume "qiskit.circuit.library.QuantumVolume") to construct its output instead of building the circuit from scratch. This may result in subtle differences from the output from the previous version. -* Tomography fitters can now also get list of Result objects instead of a single Result as requested in [issue #320](https://github.com/Qiskit/qiskit-ignis/issues/320/). +* Tomography fitters can now also get list of Result objects instead of a single Result as requested in [issue #320](https://github.com/qiskit-community/qiskit-ignis/issues/320/). @@ -783,7 +783,7 @@ The main change made in this release is a refactor of the Randomized Benchmarkin #### Bug Fixes -* Fix a bug of the position of measurement pulses inserted by py:func:qiskit.ignis.characterization.calibrations.pulse\_schedules.drag\_schedules. Fixes [#465](https://github.com/Qiskit/qiskit-ignis/issues/465) +* Fix a bug of the position of measurement pulses inserted by py:func:qiskit.ignis.characterization.calibrations.pulse\_schedules.drag\_schedules. Fixes [#465](https://github.com/qiskit-community/qiskit-ignis/issues/465) @@ -819,15 +819,15 @@ The main change made in this release is a refactor of the Randomized Benchmarkin #### Bug Fixes -* Changed in python version 3.8: On macOS, the spawn start method is now the default. The fork start method should be considered unsafe as it can lead to crashes in subprocesses. However P\_BFGS doesn’t support spawn, so we revert to single process. Refer to #1109 \<[https://github.com/Qiskit/qiskit-aqua/issues/1109](https://github.com/Qiskit/qiskit-aqua/issues/1109)> for more details. +* Changed in python version 3.8: On macOS, the spawn start method is now the default. The fork start method should be considered unsafe as it can lead to crashes in subprocesses. However P\_BFGS doesn’t support spawn, so we revert to single process. Refer to #1109 \<[https://github.com/qiskit-community/qiskit-aqua/issues/1109](https://github.com/qiskit-community/qiskit-aqua/issues/1109)> for more details. * Binding parameters in the `CircuitStateFn` did not copy the value of `is_measurement` and always set `is_measurement=False`. This has been fixed. * Previously, SummedOp.to\_matrix\_op built a list MatrixOp’s (with numpy matrices) and then summed them, returning a single MatrixOp. Some algorithms (for example vqe) require summing thousands of matrices, which exhausts memory when building the list of matrices. With this change, no list is constructed. Rather, each operand in the sum is converted to a matrix, added to an accumulator, and discarded. -* Changing backends in VQE from statevector to qasm\_simulator or real device was causing an error due to CircuitSampler incompatible reuse. VQE was changed to always create a new CircuitSampler and create a new expectation in case not entered by user. Refer to #1153 \<[https://github.com/Qiskit/qiskit-aqua/issues/1153](https://github.com/Qiskit/qiskit-aqua/issues/1153)> for more details. -* Exchange and Wikipedia finance providers were fixed to correctly handle Quandl data. Refer to #775 \<[https://github.com/Qiskit/qiskit-aqua/issues/775](https://github.com/Qiskit/qiskit-aqua/issues/775)> for more details. Fixes a divide by 0 error on finance providers mean vector and covariance matrix calculations. Refer to #781 \<[https://github.com/Qiskit/qiskit-aqua/issues/781](https://github.com/Qiskit/qiskit-aqua/issues/781)> for more details. +* Changing backends in VQE from statevector to qasm\_simulator or real device was causing an error due to CircuitSampler incompatible reuse. VQE was changed to always create a new CircuitSampler and create a new expectation in case not entered by user. Refer to #1153 \<[https://github.com/qiskit-community/qiskit-aqua/issues/1153](https://github.com/qiskit-community/qiskit-aqua/issues/1153)> for more details. +* Exchange and Wikipedia finance providers were fixed to correctly handle Quandl data. Refer to #775 \<[https://github.com/qiskit-community/qiskit-aqua/issues/775](https://github.com/qiskit-community/qiskit-aqua/issues/775)> for more details. Fixes a divide by 0 error on finance providers mean vector and covariance matrix calculations. Refer to #781 \<[https://github.com/qiskit-community/qiskit-aqua/issues/781](https://github.com/qiskit-community/qiskit-aqua/issues/781)> for more details. * The `ListOp.combo_fn` property has been lost in several transformations, such as converting to another operator type, traversing, reducing or multiplication. Now this attribute is propagated to the resulting operator. * The evaluation of some operator expressions, such as of `SummedOp``s and evaluations with the ``CircuitSampler` did not treat coefficients correctly or ignored them completely. E.g. evaluating `~StateFn(0 * (I + Z)) @ Plus` did not yield 0 or the normalization of `~StateFn(I) @ ((Plus + Minus) / sqrt(2))` missed a factor of `sqrt(2)`. This has been fixed. -* `OptimizationResult` included some public setters and class variables were `Optional`. This fix makes all class variables read-only so that mypy and pylint can check types more effectively. `MinimumEigenOptimizer.solve` generated bitstrings in a result as `str`. This fix changed the result into `List[float]` as the other algorithms do. Some public classes related to optimization algorithms were missing in the documentation of `qiskit.optimization.algorithms`. This fix added all such classes to the docstring. #1131 \<[https://github.com/Qiskit/qiskit-aqua/issues/1131](https://github.com/Qiskit/qiskit-aqua/issues/1131)> for more details. -* `OptimizationResult.__init__` did not check whether the sizes of `x` and `variables` match or not (they should match). This fix added the check to raise an error if they do not match and fixes bugs detected by the check. This fix also adds missing unit tests related to `OptimizationResult.variable_names` and `OptimizationResult.variables_dict` in `test_converters`. #1167 \<[https://github.com/Qiskit/qiskit-aqua/issues/1167](https://github.com/Qiskit/qiskit-aqua/issues/1167)> for more details. +* `OptimizationResult` included some public setters and class variables were `Optional`. This fix makes all class variables read-only so that mypy and pylint can check types more effectively. `MinimumEigenOptimizer.solve` generated bitstrings in a result as `str`. This fix changed the result into `List[float]` as the other algorithms do. Some public classes related to optimization algorithms were missing in the documentation of `qiskit.optimization.algorithms`. This fix added all such classes to the docstring. #1131 \<[https://github.com/qiskit-community/qiskit-aqua/issues/1131](https://github.com/qiskit-community/qiskit-aqua/issues/1131)> for more details. +* `OptimizationResult.__init__` did not check whether the sizes of `x` and `variables` match or not (they should match). This fix added the check to raise an error if they do not match and fixes bugs detected by the check. This fix also adds missing unit tests related to `OptimizationResult.variable_names` and `OptimizationResult.variables_dict` in `test_converters`. #1167 \<[https://github.com/qiskit-community/qiskit-aqua/issues/1167](https://github.com/qiskit-community/qiskit-aqua/issues/1167)> for more details. * Fix parameter binding in the `OperatorStateFn`, which did not bind parameters of the underlying primitive but just the coefficients. * `op.eval(other)`, where `op` is of type `OperatorBase`, sometimes silently returns a nonsensical value when the number of qubits in `op` and `other` are not equal. This fix results in correct behavior, which is to throw an error rather than return a value, because the input in this case is invalid. * The `construct_circuit` method of `VQE` previously returned the expectation value to be evaluated as type `OperatorBase`. This functionality has been moved into `construct_expectation` and `construct_circuit` returns a list of the circuits that are evaluated to compute the expectation value. diff --git a/docs/api/qiskit/release-notes/0.23.mdx b/docs/api/qiskit/release-notes/0.23.mdx index 815b9a15deb..f21cd2482fc 100644 --- a/docs/api/qiskit/release-notes/0.23.mdx +++ b/docs/api/qiskit/release-notes/0.23.mdx @@ -390,10 +390,10 @@ No change * optimize\_svm method of qp\_solver would sometimes fail resulting in an error like this ValueError: cannot reshape array of size 1 into shape (200,1) This addresses the issue by adding an L2 norm parameter, lambda2, which defaults to 0.001 but can be changed via the QSVM algorithm, as needed, to facilitate convergence. * A method `one_letter_symbol` has been removed from the `VarType` in the latest build of DOCplex making Aqua incompatible with this version. So instead of using this method an explicit type check of variable types has been introduced in the Aqua optimization module. -* :meth\`\~qiskit.aqua.operators.state\_fns.DictStateFn.sample()\` could only handle real amplitudes, but it is fixed to handle complex amplitudes. #1311 \<[https://github.com/Qiskit/qiskit-aqua/issues/1311](https://github.com/Qiskit/qiskit-aqua/issues/1311)> for more details. -* Trotter class did not use the reps argument in constructor. #1317 \<[https://github.com/Qiskit/qiskit-aqua/issues/1317](https://github.com/Qiskit/qiskit-aqua/issues/1317)> for more details. -* Raise an AquaError if :class\`qiskit.aqua.operators.converters.CircuitSampler\` samples an empty operator. #1321 \<[https://github.com/Qiskit/qiskit-aqua/issues/1321](https://github.com/Qiskit/qiskit-aqua/issues/1321)> for more details. -* `to_opflow()` returns a correct operator when coefficients are complex numbers. #1381 \<[https://github.com/Qiskit/qiskit-aqua/issues/1381](https://github.com/Qiskit/qiskit-aqua/issues/1381)> for more details. +* :meth\`\~qiskit.aqua.operators.state\_fns.DictStateFn.sample()\` could only handle real amplitudes, but it is fixed to handle complex amplitudes. #1311 \<[https://github.com/qiskit-community/qiskit-aqua/issues/1311](https://github.com/qiskit-community/qiskit-aqua/issues/1311)> for more details. +* Trotter class did not use the reps argument in constructor. #1317 \<[https://github.com/qiskit-community/qiskit-aqua/issues/1317](https://github.com/qiskit-community/qiskit-aqua/issues/1317)> for more details. +* Raise an AquaError if :class\`qiskit.aqua.operators.converters.CircuitSampler\` samples an empty operator. #1321 \<[https://github.com/qiskit-community/qiskit-aqua/issues/1321](https://github.com/qiskit-community/qiskit-aqua/issues/1321)> for more details. +* `to_opflow()` returns a correct operator when coefficients are complex numbers. #1381 \<[https://github.com/qiskit-community/qiskit-aqua/issues/1381](https://github.com/qiskit-community/qiskit-aqua/issues/1381)> for more details. * Let backend simulators validate NoiseModel support instead of restricting to Aer only in QuantumInstance. * Correctly handle PassManager on QuantumInstance `transpile` method by calling its `run` method if it exists. * A bug that mixes custom `initial_state` in `QAOA` with Hadamard gates has been fixed. This doesn’t change functionality of QAOA if no initial\_state is provided by the user. Attention should be taken if your implementation uses QAOA with cusom `initial_state` parameter as the optimization results might differ. @@ -1429,7 +1429,7 @@ VQE expectation computation with Aer qasm\_simulator now defaults to a computati * Calling PauliTrotterEvolution.convert on an operator including a term that is a scalar multiple of the identity gave an incorrect circuit, one that ignored the scalar coefficient. This fix includes the effect of the coefficient in the global\_phase property of the circuit. * Make ListOp.num\_qubits check that all ops in list have the same num\_qubits Previously, the number of qubits in the first operator in the ListOp was returned. With this change, an additional check is made that all other operators also have the same number of qubits. * Make PauliOp.exp\_i() generate the correct matrix with the following changes. 1) There was previously an error in the phase of a factor of 2. 2) The global phase was ignored when converting the circuit to a matrix. We now use qiskit.quantum\_info.Operator, which is generally useful for converting a circuit to a unitary matrix, when possible. -* Fixes the cyclicity detection as reported buggy in [https://github.com/Qiskit/qiskit-aqua/issues/1184](https://github.com/Qiskit/qiskit-aqua/issues/1184). +* Fixes the cyclicity detection as reported buggy in [https://github.com/qiskit-community/qiskit-aqua/issues/1184](https://github.com/qiskit-community/qiskit-aqua/issues/1184). diff --git a/docs/api/qiskit/release-notes/0.25.mdx b/docs/api/qiskit/release-notes/0.25.mdx index ed9e47ba885..599e5a67d2c 100644 --- a/docs/api/qiskit/release-notes/0.25.mdx +++ b/docs/api/qiskit/release-notes/0.25.mdx @@ -241,7 +241,7 @@ No change ## 0.25.0 -This release officially deprecates the Qiskit Aqua project. Accordingly, in a future release the `qiskit-aqua` package will be removed from the Qiskit metapackage, which means in that future release `pip install qiskit` will no longer include `qiskit-aqua`. The application modules that are provided by qiskit-aqua have been split into several new packages: `qiskit-optimization`, `qiskit-nature`, `qiskit-machine-learning`, and `qiskit-finance`. These packages can be installed by themselves (via the standard pip install command, e.g. `pip install qiskit-nature`) or with the rest of the Qiskit metapackage as optional extras (e.g. `pip install 'qiskit[finance,optimization]'` or `pip install 'qiskit[all]'` The core algorithms and the operator flow now exist as part of qiskit-terra at [`qiskit.algorithms`](/api/qiskit/0.45/algorithms#module-qiskit.algorithms "qiskit.algorithms") and [`qiskit.opflow`](/api/qiskit/0.45/opflow#module-qiskit.opflow "qiskit.opflow"). Depending on your existing usage of Aqua you should either use the application packages or the new modules in Qiskit Terra. For more details on how to migrate from Qiskit Aqua, you can refer to the [migration guide](https://github.com/Qiskit/qiskit-aqua/blob/main/README.md#migration-guide). +This release officially deprecates the Qiskit Aqua project. Accordingly, in a future release the `qiskit-aqua` package will be removed from the Qiskit metapackage, which means in that future release `pip install qiskit` will no longer include `qiskit-aqua`. The application modules that are provided by qiskit-aqua have been split into several new packages: `qiskit-optimization`, `qiskit-nature`, `qiskit-machine-learning`, and `qiskit-finance`. These packages can be installed by themselves (via the standard pip install command, e.g. `pip install qiskit-nature`) or with the rest of the Qiskit metapackage as optional extras (e.g. `pip install 'qiskit[finance,optimization]'` or `pip install 'qiskit[all]'` The core algorithms and the operator flow now exist as part of qiskit-terra at [`qiskit.algorithms`](/api/qiskit/0.45/algorithms#module-qiskit.algorithms "qiskit.algorithms") and [`qiskit.opflow`](/api/qiskit/0.45/opflow#module-qiskit.opflow "qiskit.opflow"). Depending on your existing usage of Aqua you should either use the application packages or the new modules in Qiskit Terra. For more details on how to migrate from Qiskit Aqua, you can refer to the [migration guide](https://github.com/qiskit-community/qiskit-aqua/blob/main/README.md#migration-guide). @@ -715,9 +715,9 @@ The Qiskit Terra 0.17.0 includes many new features and bug fixes. The major new This mapping is based on controlled Pauli Y-rotations and constructed using the [`PolynomialPauliRotations`](/api/qiskit/0.45/qiskit.circuit.library.PolynomialPauliRotations "qiskit.circuit.library.PolynomialPauliRotations"). -* A new module [`qiskit.algorithms`](/api/qiskit/0.45/algorithms#module-qiskit.algorithms "qiskit.algorithms") has been introduced. This module contains functionality equivalent to what has previously been provided by the `qiskit.aqua.algorithms` module (which is now deprecated) and provides the building blocks for constructing quantum algorithms. For details on migrating from `qiskit-aqua` to this new module, please refer to the [migration guide](https://github.com/Qiskit/qiskit-aqua/blob/main/README.md#migration-guide). +* A new module [`qiskit.algorithms`](/api/qiskit/0.45/algorithms#module-qiskit.algorithms "qiskit.algorithms") has been introduced. This module contains functionality equivalent to what has previously been provided by the `qiskit.aqua.algorithms` module (which is now deprecated) and provides the building blocks for constructing quantum algorithms. For details on migrating from `qiskit-aqua` to this new module, please refer to the [migration guide](https://github.com/qiskit-community/qiskit-aqua/blob/main/README.md#migration-guide). -* A new module [`qiskit.opflow`](/api/qiskit/0.45/opflow#module-qiskit.opflow "qiskit.opflow") has been introduced. This module contains functionality equivalent to what has previously been provided by the `qiskit.aqua.operators` module (which is now deprecated) and provides the operators and state functions which are used to build quantum algorithms. For details on migrating from `qiskit-aqua` to this new module, please refer to the [migration guide](https://github.com/Qiskit/qiskit-aqua/blob/main/README.md#migration-guide). +* A new module [`qiskit.opflow`](/api/qiskit/0.45/opflow#module-qiskit.opflow "qiskit.opflow") has been introduced. This module contains functionality equivalent to what has previously been provided by the `qiskit.aqua.operators` module (which is now deprecated) and provides the operators and state functions which are used to build quantum algorithms. For details on migrating from `qiskit-aqua` to this new module, please refer to the [migration guide](https://github.com/qiskit-community/qiskit-aqua/blob/main/README.md#migration-guide). * This is the first release that includes precompiled binary wheels for the for Linux aarch64 systems. If you are running a manylinux2014 compatible aarch64 Linux system there are now precompiled wheels available on PyPI, you are no longer required to build from source to install qiskit-terra. @@ -1354,7 +1354,7 @@ The Qiskit Terra 0.17.0 includes many new features and bug fixes. The major new * Fixes a bug where the `channels` field for a [`PulseBackendConfiguration`](/api/qiskit/0.45/qiskit.providers.models.PulseBackendConfiguration "qiskit.providers.models.PulseBackendConfiguration") object was not being included in the output of the [`qiskit.providers.models.PulseBackendConfiguration.to_dict`](/api/qiskit/0.45/qiskit.providers.models.PulseBackendConfiguration#to_dict "qiskit.providers.models.PulseBackendConfiguration.to_dict") method. Fixed [#5579](https://github.com/Qiskit/qiskit/issues/5579) -* Fixed the `'circular'` entanglement in the [`qiskit.circuit.library.NLocal`](/api/qiskit/0.45/qiskit.circuit.library.NLocal "qiskit.circuit.library.NLocal") circuit class for the edge case where the circuit has the same size as the entanglement block (e.g. a two-qubit circuit and CZ entanglement gates). In this case there should only be one entanglement gate, but there was accidentially added a second one in the inverse direction as the first. Fixed [Qiskit/qiskit-aqua#1452](https://github.com/Qiskit/qiskit-aqua/issues/1452) +* Fixed the `'circular'` entanglement in the [`qiskit.circuit.library.NLocal`](/api/qiskit/0.45/qiskit.circuit.library.NLocal "qiskit.circuit.library.NLocal") circuit class for the edge case where the circuit has the same size as the entanglement block (e.g. a two-qubit circuit and CZ entanglement gates). In this case there should only be one entanglement gate, but there was accidentially added a second one in the inverse direction as the first. Fixed [qiskit-community/qiskit-aqua#1452](https://github.com/qiskit-community/qiskit-aqua/issues/1452) * Fixed the handling of breakpoints in the [`PiecewisePolynomialPauliRotations`](/api/qiskit/0.45/qiskit.circuit.library.PiecewisePolynomialPauliRotations "qiskit.circuit.library.PiecewisePolynomialPauliRotations") class in the [`qiskit.circuit.library`](/api/qiskit/0.45/circuit_library#module-qiskit.circuit.library "qiskit.circuit.library"). Now for `n` intervals, `n+1` breakpoints are allowed. This enables specifying another end interval other than $2^\text{num qubits}$. This is important because from the end of the last interval to $2^\text{num qubits}$ the function is the identity. @@ -1692,7 +1692,7 @@ The 0.8 release includes several new features and bug fixes. The highlights for #### Bug Fixes -* Fixed an issue in the expectation value method `expectation_value()`, for the error mitigation classes `TensoredExpvalMeasMitigator` and `CTMPExpvalMeasMitigator` if the `qubits` kwarg was not specified it would incorrectly use the total number of qubits of the mitigator, rather than the number of classical bits in the count dictionary leading to greatly reduced performance. Fixed [#561](https://github.com/Qiskit/qiskit-ignis/issues/561) +* Fixed an issue in the expectation value method `expectation_value()`, for the error mitigation classes `TensoredExpvalMeasMitigator` and `CTMPExpvalMeasMitigator` if the `qubits` kwarg was not specified it would incorrectly use the total number of qubits of the mitigator, rather than the number of classical bits in the count dictionary leading to greatly reduced performance. Fixed [#561](https://github.com/qiskit-community/qiskit-ignis/issues/561) * Fix the `"auto"` method of the `TomographyFitter`, `StateTomographyFitter`, and `ProcessTomographyFitter` to only use `"cvx"` if CVXPY is installed *and* a third-party SDP solver other than SCS is available. This is because the SCS solver has lower accuracy than other solver methods and often returns a density matrix or Choi-matrix that is not completely-positive and fails validation when used with the [`qiskit.quantum_info.state_fidelity()`](/api/qiskit/0.45/quantum_info#qiskit.quantum_info.state_fidelity "qiskit.quantum_info.state_fidelity") or [`qiskit.quantum_info.process_fidelity()`](/api/qiskit/0.45/quantum_info#qiskit.quantum_info.process_fidelity "qiskit.quantum_info.process_fidelity") functions. @@ -1701,7 +1701,7 @@ The 0.8 release includes several new features and bug fixes. The highlights for This release officially deprecates the Qiskit Aqua project, in the future (no sooner than 3 months from this release) the Aqua project will have it’s final release and be archived. All the functionality that qiskit-aqua provides has been migrated to either new packages or to other qiskit packages. The application modules that are provided by qiskit-aqua have been split into several new packages: `qiskit-optimization`, `qiskit-nature`, `qiskit-machine-learning`, and `qiskit-finance`. These packages can be installed by themselves (via the standard pip install command, ie `pip install qiskit-nature`) or with the rest of the Qiskit metapackage as optional extras (ie, `pip install 'qiskit[finance,optimization]'` or `pip install 'qiskit[all]'`. The core building blocks for algorithms and the operator flow now exist as part of qiskit-terra at [`qiskit.algorithms`](/api/qiskit/0.45/algorithms#module-qiskit.algorithms "qiskit.algorithms") and [`qiskit.opflow`](/api/qiskit/0.45/opflow#module-qiskit.opflow "qiskit.opflow"). Depending on your existing usage of Aqua you should either use the application packages or the new modules in Qiskit Terra. -For more details on how to migrate from using Qiskit Aqua, you can refer to the [migration guide](https://github.com/Qiskit/qiskit-aqua/blob/main/README.md#migration-guide). +For more details on how to migrate from using Qiskit Aqua, you can refer to the [migration guide](https://github.com/qiskit-community/qiskit-aqua/blob/main/README.md#migration-guide). diff --git a/docs/api/qiskit/release-notes/0.33.mdx b/docs/api/qiskit/release-notes/0.33.mdx index 8d2804daf46..f8b25e1f5f7 100644 --- a/docs/api/qiskit/release-notes/0.33.mdx +++ b/docs/api/qiskit/release-notes/0.33.mdx @@ -142,9 +142,9 @@ No change This release officially marks the end of support for the Qiskit Aqua project in Qiskit. It was originally deprecated in the 0.25.0 release and as was documented in that release the `qiskit-aqua` package has been removed from the Qiskit metapackage, which means `pip install qiskit` will no longer include `qiskit-aqua`. However, because of limitations in python packaging we cannot automatically remove a pre-existing install of `qiskit-aqua` when upgrading a previous version of Qiskit to this release (or a future release) with `pip install -U qiskit`. If you are upgrading from a previous version it’s recommended that you manually uninstall Qiskit Aqua with `pip uninstall qiskit-aqua` or install in a fresh python environment. -The application modules that were provided by `qiskit-aqua` have been split into several new packages: `qiskit-optimization`, `qiskit-nature`, `qiskit-machine-learning`, and `qiskit-finance`. These packages can be installed by themselves (via the standard pip install command, e.g. `pip install qiskit-nature`) or with the rest of the Qiskit metapackage as optional extras (e.g. `pip install 'qiskit[finance,optimization]'` or `pip install 'qiskit[all]'`). The core algorithms and the operator flow now exist as part of Qiskit Terra at `qiskit.algorithms` and `qiskit.opflow`. Depending on your existing usage of Aqua you should either use the application packages or the new modules in Qiskit Terra. For more details on how to migrate from Qiskit Aqua you can refer to the [Aqua Migration Guide](https://github.com/Qiskit/qiskit-aqua/blob/main/docs/tutorials/Qiskit%20Algorithms%20Migration%20Guide.ipynb). +The application modules that were provided by `qiskit-aqua` have been split into several new packages: `qiskit-optimization`, `qiskit-nature`, `qiskit-machine-learning`, and `qiskit-finance`. These packages can be installed by themselves (via the standard pip install command, e.g. `pip install qiskit-nature`) or with the rest of the Qiskit metapackage as optional extras (e.g. `pip install 'qiskit[finance,optimization]'` or `pip install 'qiskit[all]'`). The core algorithms and the operator flow now exist as part of Qiskit Terra at `qiskit.algorithms` and `qiskit.opflow`. Depending on your existing usage of Aqua you should either use the application packages or the new modules in Qiskit Terra. For more details on how to migrate from Qiskit Aqua you can refer to the [Aqua Migration Guide](https://github.com/qiskit-community/qiskit-aqua/blob/main/docs/tutorials/Qiskit%20Algorithms%20Migration%20Guide.ipynb). -This release also officially deprecates the Qiskit Ignis project. Accordingly, in a future release the `qiskit-ignis` package will be removed from the Qiskit metapackage, which means in that future release `pip install qiskit` will no longer include `qiskit-ignis`. Qiskit Ignis has been supersceded by the [Qiskit Experiments](https://qiskit.org/documentation/experiments/) project and active development has ceased. While deprecated, critical bug fixes and compatibility fixes will continue to be made to provide users a sufficient opportunity to migrate off of Ignis. After the deprecation period (which will be no shorter than 3 months from this release) the project will be retired and archived. You can refer to the [migration guide](https://github.com/Qiskit/qiskit-ignis#migration-guide) for details on how to switch from Qiskit Ignis to Qiskit Experiments. +This release also officially deprecates the Qiskit Ignis project. Accordingly, in a future release the `qiskit-ignis` package will be removed from the Qiskit metapackage, which means in that future release `pip install qiskit` will no longer include `qiskit-ignis`. Qiskit Ignis has been supersceded by the [Qiskit Experiments](https://qiskit.org/documentation/experiments/) project and active development has ceased. While deprecated, critical bug fixes and compatibility fixes will continue to be made to provide users a sufficient opportunity to migrate off of Ignis. After the deprecation period (which will be no shorter than 3 months from this release) the project will be retired and archived. You can refer to the [migration guide](https://github.com/qiskit-community/qiskit-ignis#migration-guide) for details on how to switch from Qiskit Ignis to Qiskit Experiments. @@ -1453,6 +1453,6 @@ This release deprecates the Qiskit Ignis project, it has been supersceded by the * The Qiskit Ignis project as a whole has been deprecated and the project will be retired and archived in the future. While deprecated only compatibility fixes and fixes for critical bugs will be made to the proejct. Instead of using Qiskit Ignis you should migrate to use [Qiskit Experiments](https://qiskit.org/documentation/experiments/) instead. You can refer to the migration guide: - [https://github.com/Qiskit/qiskit-ignis#migration-guide](https://github.com/Qiskit/qiskit-ignis#migration-guide) + [https://github.com/qiskit-community/qiskit-ignis#migration-guide](https://github.com/qiskit-community/qiskit-ignis#migration-guide) \ No newline at end of file diff --git a/docs/api/qiskit/release-notes/0.37.mdx b/docs/api/qiskit/release-notes/0.37.mdx index 58c2a05ad91..92da22f54a8 100644 --- a/docs/api/qiskit/release-notes/0.37.mdx +++ b/docs/api/qiskit/release-notes/0.37.mdx @@ -169,7 +169,7 @@ No change This release officially marks the end of support for the Qiskit Ignis project from Qiskit. It was originally deprecated in the 0.33.0 release and as was documented in that release the `qiskit-ignis` package has been removed from the Qiskit metapackage, which means in that future release `pip install qiskit` will no longer include `qiskit-ignis`. However, note because of limitations in python packaging we cannot automatically remove a pre-existing install of `qiskit-ignis`. If you are upgrading from a previous version it’s recommended that you manually uninstall Qiskit Ignis with `pip uninstall qiskit-ignis` or install the metapackage in a fresh python environment. -Qiskit Ignis has been supersceded by the [Qiskit Experiments](https://qiskit.org/documentation/experiments/) project. You can refer to the [migration guide](https://github.com/Qiskit/qiskit-ignis#migration-guide) for details on how to switch from Qiskit Ignis to Qiskit Experiments. +Qiskit Ignis has been supersceded by the [Qiskit Experiments](https://qiskit.org/documentation/experiments/) project. You can refer to the [migration guide](https://github.com/qiskit-community/qiskit-ignis#migration-guide) for details on how to switch from Qiskit Ignis to Qiskit Experiments. diff --git a/scripts/js/lib/links/ignores.ts b/scripts/js/lib/links/ignores.ts index ac146add4d5..fba75b396bc 100644 --- a/scripts/js/lib/links/ignores.ts +++ b/scripts/js/lib/links/ignores.ts @@ -56,6 +56,7 @@ const ALWAYS_IGNORED_URLS__EXPECTED = [ "https://doi.org/10.1103/PhysRevApplied.5.034007", "http://dx.doi.org/10.1103/PhysRevA.83.012308", "https://doi.org/10.1103/PhysRevLett.103.150502", + "https://doi.org/10.1103/PhysRevA.99.032331", ]; // These external URLs cause actual 404s and should probably be fixed.