bugfix: Handle meas_level
from backend.run
#142
Merged
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
Validate meas_level if it is supplied to run, and if it's valid, remove it. AwsQuantumTask does not accept
meas_level
argument.Note:
meas_level=0 is raw results, an array of complex values (think sampled data collected from an ADC)
meas_level=1 is kerneled results, so a single complex value
meas_level=2 is classified results, 0 or 1
meas_level is also often supplied as an enum. For example: https://github.com/Qiskit-Extensions/qiskit-experiments/blob/f22bb7b67893a1b75f7d0f1fecdb0bd63284e244/qiskit_experiments/framework/base_experiment.py#L454