Releases: tergite/tergite-backend
v2024.12.2
The December 2024 patch 2 release of the Tergite backend.
It is compatible with the v2024.12.x release of the Tergite stack.
Changed
- Changed the apt installation step in Dockerfile to remove
/var/lib/apt/lists/*
after completion
Full Changelog: v2024.12.1...v2024.12.2
v2024.12.1
The December 2024 patch 1 release of the Tergite backend.
It is compatible with the v2024.12.x release of the Tergite stack.
Added
- Added Dockerfile.
- Added instructions how to run with docker.
- Added instructions how to run the qiskit_pulse_2q simulator in the configuration docs.
Changed
- Changed
start_bcc.sh
script to use redis connection obtained from the environment. - Changed
start_bcc.sh
script to update the exported environment variables after reading from theENV_FILE
. - Updated Github action to deploy built multiplatform image to docker hub as something like
tergite/tergite-backend
- Removed some redundant libraries in the
requirements.txt
file. - Removed some outdated docs.
Full Changelog: v2024.12.0...v2024.12.1
v2024.12.0
The December 2024 release of the Tergite backend.
It is compatible with the v2024.12.x release of the Tergite stack.
Added
- Added redis connection environment variables
- Added GitLab CI configuration
- Added storing of Qobj header data in the logfiles of the quantum jobs
- Qiskit dynamics simulator backend with two-qubit CZ gate ("qiskit_pulse_2q")
- Added CouplerProps to Backend Configurations
- Added the
coupling_dict
to thebackend_config.toml
Fixed
- Fixed httpx version to 0.27.2 as 0.28.0 removes many deprecations that we were still dependent on in FastAPI testClient
Changed
- Removed the
coupling_map
from thebackend_config.toml
as it is generated on-the-fly from thecoupling_dict
.
Full Changelog: v2024.09.1...v2024.12.0
v2024.09.1
A patch release of the September 2024 series of the Tergite backend.
It is compatible with the v2024.09.x release of the Tergite stack.
Fixed
- Fixed 'KeyError' when no units are not passed in the backend_config file
- Fixed "...bin/conda/activate: Not a directory" error when starting as systemd service
- Fixed silent error where calibrations are not sent to MSS on executor initialization
- Fixed "TypeError: Object of type datetime is not JSON serializable" when sending calibration data to MSS
- Fixed 'SyntaxWarning: 'is not' with a literal' when initializing backend
Full Changelog: v2024.09.0...v2024.09.1
v2024.09.0
The September 2024 release of the Tergite backend.
It is compatible with the v2024.09.x release of the Tergite stack.
Added
- The
QuantumExecutor
as abstract class to implement a backend EXECUTOR_TYPE
keyword in the .env variables to select the backend- Qiskit dynamics simulator backend with one qubit ("qiskit_pulse_1q")
- Added the initialization of the redis store with configuration picked from the
backend_config.toml
file
when the execution worker starts - Added an initial request to update the backend information in MSS
when the execution worker starts
Changed
- BREAKING CHANGE:
EXECUTOR_DATA_DIRNAME
definition in the .env variables instead ofgeneral.data_dir
inexecutor-config.yml
- BREAKING CHANGE: Removed the whole
general
section in theexecutor-config.yml
- BREAKING CHANGE: Renamed
executor-config.yml
toquantify-config.yml
- Removed the old config files that were used for setting up automatic calibration
- Removed the script that loaded automatic calibration configurations at the start
- Moved the
backend_config.toml
file from/configs
folder - Moved the
properties
service to thelibs
folder - Moved the
storage
,date_time
,representation
andlogging
utils to theproperties
lib - Removed the
scripts
folder - Removed the
archive
folder
Fixed
- Fixed the reporting to MSS of errors in jobs during post-processing
Full Changelog: v2024.04.0...v2024.09.0
v2024.04.0
The April 2024 release of the Tergite backend.
It is compatible with the v2024.04.x release of the Tergite stack.
The Tergite release v2024.04 which merges the Tergite stack into three clear parts: front, back, client/sdks
Added
- Added storage_file lib (formerly tergite-quantify-connector-storagefile)
- Added quantum_executor service (formerly tergite-quantify-connector)
- Added the executor-config.yml and its python-based validators
Changed
- Changed the way discriminators are loaded to load from the database
- BREAKING_CHANGE: Removed hard-coded discriminators
- BREAKING_CHANGE: Removed official support for Python 3.8; Official support is now >=3.9
- BREAKING_CHANGE: Removed Labber support
- Replaced tergite-quantify-connector-storagefile package with an internal storage_file lib
- Moved unused files to archive folder
- BREAKING_CHANGE: Removed calibration and two state discrimination source code
- BREAKING_CHANGE: Replaced tergite-quantify-connector-storagefile package with an internal storage_file lib
- BREAKING_CHANGE: Merged tergite-quantify-connector into tergite-backend and renamed its service to quantum_executor
- BREAKING_CHANGE: Changed configuration of hardware to use executor-config.yml file with proper validations on loading
- BREAKING_CHANGE: Removed support for Pulsar, or any other instrument drivers other than Cluster.
The old implementation wrongfully assumed that all these drivers have the same signature i.e.driver(name: str, identifier: str | None)
yetSpiRack(name: str, address: str, baud_rate: int = 9600, timeout: float = 1, is_dummy: bool = False,)
,
Pulsar(name: str, identifier: Optional[str] = None, port: Optional[int] = None, debug: Optional[int] = None, dummy_type: Optional[PulsarType] = None,)
Cluster(name: str, identifier: Optional[str] = None, port: Optional[int] = None, debug: Optional[int] = None, dummy_type: Optional[PulsarType] = None)
are all different. - BREAKING_CHANGE: We got rid of quantify connector’s redundant reset() method.
- BREAKING_CHANGE: Changed backend name used when querying MSS for backend properties to be equal to settings.DEFAULT_PREFIX
Fixed
- Fixed duplicate job uploads to respond with HTTP 409
Full Changelog: https://github.com/tergite/tergite-backend/commits/v2024.04.0