Create separate runtime for per-tuple measurements #4
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.
Third time's the charm!
(For context for future readers: it is useful to have statistics on a per-tuple level versus a per-qubit level)
Testing
ctest
and manual testing withqir-xacc
:I have not tested Qwerty end-to-end yet because there are 2-3 more PRs needed to upstream all my changes, some of which may take a while. But the (tuple-grouped) output is the same as it expects