Call `determine_absolute_timing` in `qcompile` when no `device_cfg` supplied

Edgar Reehuisrequested to merge
abs-timing-no-dev into main

Explanation of changes

We make sure determine_absolute_timing is called when device_compile is skipped.

Two tests are added:

  • test_qcompile_no_device_cfg_determine_absolute_timing => verify that determine_absolute_timing is called upon no device config supplied
  • test_compile_no_device_cfg => example of compiling pulse-only schedule with no device config

Motivation of changes

This allows for simple pulse-only schedules without the need of supplying device configuration, hardware config suffices.

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 (main for most MRs).
  • New code is fully tested.
  • New code is documented and docstrings use numpydoc format.
  • CHANGELOG.rst and AUTHORS.rst have been updated (when applicable).
  • CI pipelines pass
    • pre-commit run --all-files --hook-stage commit 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),
    • windows tests pass (manually triggered by maintainers before merging).

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

Edited by Edgar Reehuis

Merge request reports