The MeasurementOutcomes.backend attribute has been designed mainly for simulation, since it is used for frequencies, probabilities, and samples, that in hardware execution should all be obtained with simple operations.
Ideally, there could be a different mechanism for passing this backend, improving objects isolation. However, in Qibolab this should not be used (hopefully?), so it should be simpler to address the issue at least here.
The
MeasurementOutcomes.backend
attribute has been designed mainly for simulation, since it is used for frequencies, probabilities, and samples, that in hardware execution should all be obtained with simple operations.Ideally, there could be a different mechanism for passing this backend, improving objects isolation. However, in Qibolab this should not be used (hopefully?), so it should be simpler to address the issue at least here.
https://github.com/qiboteam/qibolab/pull/618#discussion_r1412050002