Artificial detuning in Ramsey Schedule and bug fixes

Explanation of changes

This MR includes the latest versions of the timedomain schedules, which we used in the qitt experiments (originally written by @AdriaanRol). In particular, we have added the ability to add an artificial detuning in a Ramsey experiment. There is also a bug fix in the AllXY schedule, as well as some other very minor alterations.

Motivation of changes

When doing Ramsey experiment, we can add an 'artificial detuning' in software to emulate the effect of an extra frequency detuning. The point of this is to ensure that we always see an oscillating signal due to this detuning, even when the qubit drive frequency is on resonance. This allows us to obtain a more accurate fit when using the Ramsey to precisely tune the frequency. The artificial detuning is implemented by adding a varying phase to the \pi/2 pulse in the Ramsey sequence:

rec_phase = np.rad2deg(2 * np.pi * artificial_detuning * tau)
schedule.add(
    Rxy(theta=90, phi=rec_phase, qubit=qubit), ref_pt="start", rel_time=tau
)

This artificial detuning is already incorporated into the Ramsey analysis code in quantify core, and has been tested in the qitt experiments, but it has not yet been merged here. I also need it for the new Ramsey mock experiments that I am working on.

Aside from this, we have fixed a bug in the AllXY sequence where one of the phases in allxy_combinations was wrong (we discovered this when doing the qitt experiments) and have added a new optional argument elt_select_idx which allows the user to select a particular index or indices from the AllXY sequence.


Merge checklist

See also merge request guidelines

  • Merge request has been reviewed and approved by a project maintainer.
  • Merge request contains a clear description of the proposed changes and the issue it addresses.
  • Merge request made onto appropriate branch (develop for most MRs).
  • New code is fully tested.
  • New code is documented and docstrings use numpydoc format.
  • Changelog has been updated (when applicable).
  • CI pipelines pass
    • black code-formatting passes (gitlab-ci),
    • test suite passes (gitlab-ci),
    • no degradation in code-coverage (codacy),
    • no (serious) new pylint code quality issues introduced (codacy),
    • documentation builds successfully (CI and readthedocs).
Edited by Kelvin Loh

Merge request reports

Loading