Feat randomized measurements #536
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A continuation of #515 that explicitly supports randomized measurements.
This PR supports one new feature:
RandomizedMeasurementstruct / class that will add per-shot randomized measurements to a program, as well as support the client in ascertaining which random unitary was played on each qubit per shot.The documentation should stand on its own here. One note, I've put all of this functionality into
qpu/experimental(both in Rust and Python). It is experimental both in the sense that it is an experimental feature in the QCS SDK that should not be considered stable as well as in the sense that it supports features relevant to QIS experimentalists.Review Guidance:
crates/lib/src/qpu/experimental/randomized_measurements.rsmeasurements builds off the primitives defined in the file above.crates/python/qcs_sdk/qpu/experimental/randomized_measurements.pyi.crates/lib/src/qpu/experimental/randomized_measurements.rsas well ascrates/lib/examples/randomized_measurements.rs.