Acquisition testcases with Qblox dummy data (QAE-791)

Explanation of changes

This change adds new Qblox acquisition testcases, and modifies some old testcases to use the Qblox dummy acquisition capability.

Note: now the dummy acquisition data mocking is inside each testcase. The reason is that it is impossible to know which slot, sequencer, acquisition channel does the dummy acquisition data belongs to without knowing the schedule and the hardware config and the device config, and all three are only present at the same time in the testcase.

Motivation of changes

It is easy to make mistakes if we do not test how quantify-scheduler processes realistic acquisition data what's returned by qblox-instruments. Now, several tests ensure, that the data is processed as expected.


Merge checklist

See also merge request guidelines

  • Merge request has been reviewed (in-depth by a knowledgeable contributor), and is approved by a project maintainer.
  • New code is covered by unit tests (or N/A).
  • New code is documented and docstrings use numpydoc format (or N/A).
  • New functionality: considered making private instead of extending public API (or N/A).
  • Public API changed: added @deprecated (or N/A).
  • Tested on hardware (or N/A).
  • CHANGELOG.md and AUTHORS.md have been updated (or N/A).
  • Windows tests in CI pipeline pass (manually triggered by maintainers before merging).
  • New qblox-instruments is released, and quantify-scheduler depends on new qblox-instruments which support correct dummy behavior.

For reference, the issues workflow is described in the contribution guidelines.

Edited by Edgar Reehuis

Merge request reports

Loading