This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
job/result: expose raw bitstrings through result.get_memory() #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
airwoodix
force-pushed
the
job-result-memory
branch
from
5f8bbf4
to
ae972f9
Compare
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified Files
|
wilfried-huss
approved these changes
Apr 11, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
This patch enables using
result.get_memory()to access the raw bitstrings for each shot after a circuit execution.Details and comments
memoryoption (e.g. passed inbackend.run()) has no effect: the classical memory is always available, since this is what the AQT cloud computing API returns and the standard counts are calculated in the provider code.