Add ability for frequency override in gate operations
Explanation of changes
- Add ability to override the frequency for some operations.
Measure(qubit="q0", freq=5e9)
- Add ability to "reset" the frequency to the clock frequency using the
SetClockFrequencyoperation:SetClockFrequency(clock=clock, clock_freq_new=None). This resets the frequency to the frequency set in the configuration or the clock device element.
Motivation of changes
There is already a way to override device-level parameters for gate-operations. Additionally, we sometimes need to override frequencies for some operations, for example when we sweep measurement operations for frequency sweeps.
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 @deprecatedand entry in deprecated code suggestions (or N/A). -
Newly added/adjusted documentation and docstrings render properly (or N/A). -
Pipeline fix or dependency update: post in #software-for-developerschannel to mergemainback in or update local packages (or N/A). -
Tested on hardware (or N/A). -
CHANGELOG.mdandAUTHORS.mdhave been updated (or N/A). -
Update Hardware backends documentation if backend interface change or N/A -
Check whether performance is significantly affected by looking at the Performance metrics results. -
Windows tests in CI pipeline pass (manually triggered by maintainers before merging). - Maintainers do not hit Auto-merge, we need to actively check as manual tests do not block pipeline
For reference, the issues workflow is described in the contribution guidelines.
Edited by Gábor Oszkár Dénes