Update to qibolab 0.2

calibration_scripts/rx_calibration.py

@@ -13,10 +13,10 @@
     e.platform.settings.nshots = 2000
 
     rabi_output = e.rabi_amplitude(
-        min_amp_factor=0.5,
-        max_amp_factor=1.5,
-        step_amp_factor=0.01,
-        pulse_length=e.platform.qubits[target].native_gates.RX.duration,
+        min_amp=0.0,
+        max_amp=2,
+        step_amp=0.01,
+        pulse_length=e.platform.natives.single_qubit[target].RX[0][1].duration,
     )
     # update only if chi2 is satisfied
     if rabi_output.results.chi2[target][0] > 2:
@@ -43,10 +43,10 @@
         ramsey_output.update_platform(e.platform)
 
     rabi_output_2 = e.rabi_amplitude(
-        min_amp_factor=0.5,
-        max_amp_factor=1.5,
-        step_amp_factor=0.01,
-        pulse_length=e.platform.qubits[target].native_gates.RX.duration,
+        min_amp=0,
+        max_amp=0.2,
+        step_amp=0.01,
+        pulse_length=e.platform.natives.single_qubit[target].RX[0][1].duration,
     )
     # update only if chi2 is satisfied
     if rabi_output_2.results.chi2[target][0] > 2:
@@ -61,10 +61,10 @@
         )
 
     rabi_output_3 = e.rabi_amplitude(
-        min_amp_factor=0.5,
-        max_amp_factor=1.5,
-        step_amp_factor=0.01,
-        pulse_length=e.platform.qubits[target].native_gates.RX.duration,
+        min_amp=0,
+        max_amp=0.2,
+        step_amp=0.01,
+        pulse_length=e.platform.natives.single_qubit[target].RX[0][1].duration,
     )
     # update only if chi2 is satisfied
     if rabi_output_3.results.chi2[target][0] > 2:

doc/source/getting-started/interface.rst

@@ -105,7 +105,7 @@ This program will upload your report to the server and generate an unique URL.
 
 
 ``qq compare``
-^^^^^^^^^^^^^
+^^^^^^^^^^^^^^
 
 
 Using ``qq compare`` it is possible to compare together two ``Qibocal`` reports.

doc/source/protocols/chevron.rst

@@ -18,9 +18,9 @@ Below is an example runcard for this experiment.
     - id: chevron
       operation: chevron
       parameters:
-        amplitude_max_factor: 1.1
-        amplitude_min_factor: 0.9
-        amplitude_step_factor: 0.01
+        amplitude_max: 1.1
+        amplitude_min: 0.9
+        amplitude_step: 0.01
         duration_max: 51
         duration_min: 4
         duration_step: 2

doc/source/protocols/flipping.rst

@@ -1,16 +1,20 @@
 Flipping
 ========
 
-The flipping experiment corrects the amplitude in the qubit drive pulse. In this experiment,
-we applying an :math:`R_x(\pi/2)` rotation followed by :math:`N` flips (two :math:`R_x(\pi)` rotations)
+The flipping experiment corrects the amplitude in the qubit drive pulse for :math:`R_x(\pi)` rotations. In this experiment,
+we apply an :math:`R_x(\pi/2)` rotation followed by :math:`N` flips (two :math:`R_x(\pi)` rotations)
 and we measure the qubit state.
 The first :math:`R_x(\pi/2)` is necessary to discriminate the over rotations and under rotations of the :math:`R_x(\pi)` pulse:
 without it the difference between the two cases is just a global phase, i.e., the
 probabilities are the same. With the :math:`R_x(\pi/2)` pulse, in case of under rotations the state will be closer to :math:`\ket{0}`
 after the initial flip, in the over rotations one the final state will be closer to :math:`\ket{1}`.
 
 By fitting the resulting data with a sinusoidal function, we can determine the delta amplitude, which allows us to refine the
-:math:`\pi` pulse amplitue.
+:math:`\pi` pulse amplitude.
+
+We implemented also a version of the flipping protocol to calibrate the drive pulse amplitude of the :math:`R_x(\pi/2)` rotations,
+in this case each :math:`R_x(\pi)` rotation is replaced by two :math:`R_x(\pi/2)` rotations.
+The main reasons for implementing protocols to fine tune the `R_x(\pi/2)` rotations are explained in :ref:`rabi`.
 
 Parameters
 ^^^^^^^^^^
@@ -24,30 +28,28 @@ It follows a runcard example of this experiment.
 
 .. code-block:: yaml
 
-	- id: flipping
-	  operation: flipping
-	  parameters:
-	    detuning: 0.05
-	    nflips_max: 30
-	    nflips_step: 1
+    - id: flipping
+      operation: flipping
+      parameters:
+        delta_amplitude: 0.05
+        nflips_max: 30
+        nflips_step: 1
 
 The expected output is the following:
 
 .. image:: flipping.png
 
-Qibocal provides also a "signal" version of this routine, it follows a possible runcard
-with its report.
+If the same experiment is run setting the `rx90: True` the flipping is performed to calibrate the amplitude of the :math:`R_x(\pi/2)` rotation
 
 .. code-block:: yaml
 
     - id: flipping
-      operation: flipping_signal
+      operation: flipping
       parameters:
-        detuning: -0.5
-        nflips_max: 20
+        delta_amplitude: 0.05
+        nflips_max: 30
         nflips_step: 1
-
-.. image:: flipping_signal.png
+        rx90: True
 
 Requirements
 ^^^^^^^^^^^^

doc/source/protocols/flux/crosstalk.rst

@@ -62,50 +62,3 @@ Requirements
 ^^^^^^^^^^^^
 
 - :ref:`qubit_flux`
-
-.. _resonator_crosstalk:
-
-Resonator crosstalk
--------------------
-
-In a similar fashion it is possible to repeat the previous experiment
-by sweeping the readout frequency. Note that in this case it will be
-necessary to bias the qubit away from its sweetspot more to observe
-significant variations.
-
-Parameters
-^^^^^^^^^^
-
-.. autoclass:: qibocal.protocols.flux_dependence.resonator_crosstalk.ResCrosstalkParameters
-  :noindex:
-
-Example
-^^^^^^^
-
-.. code-block:: yaml
-
-    - id: resonator crosstalk
-      operation: resonator_crosstalk
-      targets: [2]
-      parameters:
-        bias_point:
-            2: 0.5
-        bias_step: 0.01
-        bias_width: 0.4
-        flux_qubits: [0, 3]
-        freq_step: 100000
-        freq_width: 6000000
-        nshots: 2000
-
-.. image:: resonator_crosstalk.png
-
-As we can see, even by biasing the qubit away from its sweetspot we are not able to see
-a dependence ( a deviation from the straight line) but only a shift.
-
-The protocols aims at extracting the crosstalk coefficients
-:math:`C_{20}` and :math:`C_{23}`.
-
-Requirements
-^^^^^^^^^^^^
-
-- :ref:`resonator_flux`

doc/source/protocols/flux/single.rst

@@ -120,54 +120,10 @@ A possible runcard to assess how the resonator frequency changes by varying flux
         relaxation_time: 1000
 
 
-From this protocol it is possible to extract both the bare and the dressed resonator frequency
-as well as an estimate for the coupling :math:`g_0`.
-It is suggested to run this protocol only after executing the qubit flux dependence experiment
-since some of the coefficients required can be computed with that experiment.
-
-
 .. image:: resonator_flux.png
 
 Requirements
 ^^^^^^^^^^^^
 
 - :ref:`resonator_punchout`
 - :ref:`qubit_flux`
-
-Qubit flux dependence (tracking)
---------------------------------
-
-As we saw above both the resonator and the qubit are affected by an external flux.
-In the qubit flux dependence the measurement is performed at fixed readout frequency.
-To take into account how the transmon shifts in frequency when probing the qubit we have
-another experiment `qubit_flux_tracking`.
-
-Parameters
-^^^^^^^^^^
-
-.. autoclass:: qibocal.protocols.flux_dependence.qubit_flux_tracking.QubitFluxTrackParameters
-  :noindex:
-
-Example
-^^^^^^^
-
-Here is a possible runcard:
-
-.. code-block:: yaml
-
-    - id: qubit flux dependence
-      operation: qubit_flux_tracking
-      parameters:
-        bias_step: 0.001
-        bias_width: 0.05
-        drive_amplitude: 0.002
-        drive_duration: 4000
-        freq_step: 200000
-        freq_width: 10000000
-        nshots: 1024
-        relaxation_time: 20000
-
-Requirements
-^^^^^^^^^^^^
-
-- :ref:`resonator_flux`

doc/source/protocols/index.rst

@@ -1,3 +1,4 @@
+.. _calibration_routines:
 Protocols
 =========
 
@@ -28,11 +29,9 @@ In this section we introduce the basics of all protocols supported by ``qibocal`
     allxy
     flipping
     readout_mitigation_matrix
-    avoided_crossing
     readout_optimization
     standard_rb
     chevron
     virtual_z
     state_tomographies
-    coupler/chevron
     references

doc/source/protocols/qubit_spectroscopy/qubit_spectroscopy.rst

@@ -53,10 +53,6 @@ Here is the corresponding plot:
 
 
 To extract the qubit frequency a Lorentzian fit is performed.
-After the post-processing the following parameters will be updated:
-
-* qubit.drive_frequency
-* qubit.native_gates.RX.frequency
 
 Requirements
 ^^^^^^^^^^^^