Calibration
Helmi is continuously calibrated to ensure functionality. The calibration process involves a series of experiments, aimed at fine-tuning the parameters, necessary for controlling and measuring the qubits. In addition to calibration, we run benchmarks to obtain the figures of merit reflecting the current state of the quantum computer.
Note
Calibration and benchmarking experiments are interleaved with regular user jobs in Helmi's job queue, as detailed in the Running on Helmi section. The calibration might therefore slightly increase the waiting time in the queue of regular user jobs.
Calibration sequences
To minimize the impact of calibration on user operations, we execute shorter calibration sequences during the day and a longer calibration run throughout the night.
Short calibration:
- Every 2 hours from 11 am to 11 pm
- Adjusts qubit drive frequency, drive amplitude and readout threshold
- Measures \(T_1\), \(T_2\), \(T_2^*\) and readout accuracy
Extended calibration:
- Every day at 4 am
- Adjusts qubit drive frequency, amplitude fine-tuning and readout threshold
- Measures \(T_1\), \(T_2\), \(T_2^*\), readout accuracy, single- and two-qubit gate fidelities
A calibration sequence produces what is called a calibration_set
. This is a set of device parameters, which the quantum computer is currently using to execute quantum circuits. It is identified via a calibration_set_id
, a unique identifier for the specific calibration_set
. Usually, when submitting quantum circuits, the most up-to-date calibration set is used, however, it is possible to use a specific calibration_set_id
. This can be useful for testing the degradation of the performance of our quantum computers.
Quality metrics set
The benchmarks results are summarized in the quality metric set representing the figures of merit and reflecting the latest state of the quantum computer. The calibration metrics can be fetched from Helmi's API by sending HTTP GET
requests to /calibration/metrics/latest
. An example script is provided here. Each quality metrics set is identified via a unique ID, with a new ID created after each calibration. Note, that not all metrics are updated after each calibration run. We recommend to save the current calibration set ID together with the job ID to facilitate debugging and analysis. Also note that it can happen that there is a delay of up to 10 minutes between calibrating the device and benchmarking the quality metrics set, causing there to be some delay in presenting the quality metrics data.
The metrics contained in the quality metrics set are summarized below:
Metric | Description |
---|---|
\(T_1\) time (s) | The \(T_1\) time is called the longitudinal relaxation rate and describes how quickly the excited state of the qubit returns to its ground state. |
\(T_2\) time (s) | The \(T_2\) time is called the transverse relaxation rate and describes loss of coherence of a superposition state. |
\(T_2\)-echo time (s) | The \(T_2\)-echo time describes the loss of coherence of the superposition state of the qubit. It is more precise than the \(T_2\) Time as it is less susceptible to low-frequency noise. |
Single-shot readout fidelity | Measures the average accuracy of distinguishing qubit states. The experiment prepares for 50% of the shots the qubit in the ground state \(| 0\rangle\) and for the other 50% in the excited state \(| 1\rangle\). |
Single-shot readout 10 error | The error in labelling the qubit state as \(| 0\rangle\) when it was prepared in state \(| 1\rangle\) |
Single-shot readout 01 error | The error in labelling the qubit state as \(| 1\rangle\) when it was prepared in state \(| 0\rangle\) |
1QB average gate fidelity | Average 1QB gate fidelity estimated with randomized benchmarking. |
2QB average gate fidelity | The average 2QB gate fidelity estimated with randomized benchmarking. |
CZ gate fidelity | The average CZ gate fidelity estimated with interleaved randomized benchmarking. It is usually higher than the average 2QB gate fidelity as a random 2QB Clifford transpiles on average to 8 1QB gates and 1.5 CZ gates. |
These metrics provide critical insights into the operational efficiency, error rates, and coherence properties of Helmi. Understanding these figures of merit allows a user to make informed decisions on transpilation strategies and qubit selection, optimizing for circuit depth or fidelity.
Example response
Here is an example response from Helmi's API for the calibration and quality metrics set
{
"calibration_set_id": "03436204-3588-4567-95ec-5a61acfd227d",
"quality_metric_set_id": "ec1298a0-43ce-43f2-b6d1-10c1fe750786",
"metrics": {
"QB1.fidelity_1qb_gates_averaged": {
"value": "0.9971526901996984",
"unit": "",
"uncertainty": "5.622242981254397e-05",
"timestamp": "2024-03-20T05:05:08.109836"
},
"TC-3-5.cz_gate_fidelity": {
"value": "0.9848983187049354",
"unit": "",
"uncertainty": "0.002603321013490276",
"timestamp": "2024-03-20T05:05:08.109836"
}
}
}