Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get_match_for_measurement should follow precedence rules of matching qubit #160

Closed
MarquessV opened this issue Mar 10, 2023 · 0 comments · Fixed by #243
Closed

get_match_for_measurement should follow precedence rules of matching qubit #160

MarquessV opened this issue Mar 10, 2023 · 0 comments · Fixed by #243
Assignees

Comments

@MarquessV
Copy link
Contributor

MarquessV commented Mar 10, 2023

Per this discussion the precedence for determining the best match for a Measurement to a vector of MeasureCalibrationDefinition is as follows:

  1. Match fixed qubit
  2. Match variable qubit
  3. Match no qubit (I don't recall this case but it's supported here)

The tiebreaker among calibrations of equal precedence is "last wins."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant