v1.0.0

• Set minimal required qiskit version to 0.45.0 (#108)
• Use qiskit-algorithms package instead of deprecated qiskit.algorithms in examples (#110)
• Use arnica.aqt.eu instead of arnica-stage.aqt.eu as default portal (#111)

v0.19.0

• Interprete string filters in AQTProvider.get_backend() as exact matches, not patterns (#90)
• Fix incorrect handling of qubit/clbit permutations by offline simulators (#93)
• Depend on qiskit instead of qiskit-terra (#95)
• Remove use of deprecated Bit.index and Bit.register (#99)
• Use ruff format instead of black (#101)

v0.18.0

• Check that the circuits submitted to the offline simulators can be converted to the AQT API (#68)
• Update the user guide and improve the API reference consistency (#72, #75)
• Add quickstart examples for the Qiskit.org homepage (#73)
• Add persistence mechanism for AQTJob instances (#77)
• Rename OfflineSimulatorResource.noisy to OfflineSimulatorResource.with_noise_model (#77)

v0.17.0

• Merge community and AQT versions (#61)

Qiskit AQT Provider 0.4.3

Changelog

Fixes

• Fix result processing on AQTJob creation when a single circuit list is passed to backend.run(). (Fixed #46)
• Properly retain circuit metadata in output Result object returned by AQTJob.result().

Qiskit AQT Provider 0.4.2

Changelog

Fixes

• Bumps version that was missing in 0.4.1.

Qiskit AQT Provider 0.4.1

Changelog

Deprecated

backend.run(qobj=...) support is being phased out in favor of backend.run(circuit=...).
This only affect users who submit circuits / qobj using keyword arguments.

Qiskit AQT Provider 0.4.0

Changelog

Breaking changes

• The AQT provider namespace packing (from qiskit.providers.aqt import AQTProvider) has been replaced
  with its own module, e.g. from qiskit_aqt_provider import AQTProvider.

Added

• It is now possible to query for counts directly from a job instance using job.get_counts().

Bug fixes

• The job.status() query now works correctly, and returns a Qiskit JobStatus enum.

Deprecated

• Use of the AQTAccount object is deprecated in place of instantiating
  the AQTProvider directly with the AQT token. This functionality will be removed in an
  upcoming release.

Qiskit AQT Provider 0.3.0

Changelog

Added

• A new kwarg, wait, on AQTJob.result() which sets a timeout for waiting
  for results.
• The run() method for AQTSimulator, AQTSimulatorNoise1, and AQTDevice
  now supports taking in a QuantumCircuit object (and a list of
  QuantumCircuit objects) directly. The circuit no longer needs to be
  converted to a QasmQobj using qiskit.assemble() anymore to be run on
  the backend.

Upgrade

• Python 3.5 is no longer supported. You will need at least Python 3.6
  to run this version of qiskit-aqt-provider.

Deprecated

• The current import path of qiskit.providers.aqt is deprecated and will
  be removed in the next release. This is being done for two reasons. The
  first is to make it clear what is developed as part of the core qiskit
  project, and things on top of it. The second is that python namespace
  packaging is quite error prone and a frequent cause of user issues. So
  having the aqt provider package own its namespace should make it much more
  reliable to install and use. (see Qiskit/qiskit#559 for more details).
  While the first reason may change over time as the priorities and
  objective of the Qiskit project evolve, the second will always remain
  true. So even if the first reason goes away this will be a one way
  permanent change
• Passing a QasmQobj object to the run() method of AQTSimulator,
  AQTSimulatorNoise1, and AQTDevice is deprecated and will be removed in
  a future release. Instead you should just pass a transpiled
  QuantumCircuit (or a list of circuits) to run directly, the assembly
  step can be skipped.

Fixed

• Added missing required attribute, max_experiments, from the
  BackendConfiguration returned by the AQT backends.

Qiskit AQT Provider 0.2.0

Changelog

Added

• A new backend, aqt_qasm_simulator_noise_1 has been added. This is
  a simulator backend with a noise model.

Fixed

• Jobs are now checked that they do not exceed backend's max shots before
  submitting to the backend.