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

Allow measurement outcomes to be provided to the quantum board when performing moves #167

Merged
merged 5 commits into from
Apr 28, 2021

Conversation

weinstein
Copy link
Contributor

@weinstein weinstein commented Apr 26, 2021

Part of fixing issue #152

  • adds an optional measurement outcome field to Move objects
  • use that measurement outcome instead of sampling if present when performing moves

@weinstein weinstein marked this pull request as ready for review April 26, 2021 23:37
@weinstein weinstein requested review from cantwellc and removed request for dstrain115 April 26, 2021 23:38
Copy link
Collaborator

@cantwellc cantwellc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should work nicely.

def __init__(self,
source: str,
target: str,
*,
source2: str = None,
target2: str = None,
move_type: enums.MoveType = None,
move_variant: enums.MoveVariant = None):
move_variant: enums.MoveVariant = None,
measurement: bool = None):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use an int for this instead? Is any one measurement "truer" than the other? And we also won't have to deal with the conversion in post_select later on.

Copy link
Collaborator

@cantwellc cantwellc Apr 27, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good thought. Int would also allow for the possibility of multi outcome measurements in the future

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

Successfully merging this pull request may close these issues.

4 participants