New answers tagged

12

Thanks for pointing this out! It turns out that this device was mis-calibrated in a way that was leading to that behavior. We just fixed the calibrations, so the problem should be gone now. I apologize for the trouble, and we will try to update our routine calibrations to detect and prevent this problem from coming up in the future :-).


6

This was a readout crosstalk error that has now been resolved.


3

Your expectation here is correct. c[0] should be 0 (well, modulo some small readout errors). The difference between backends is just due to a software bug on some of them. This will get fixed, thanks for reporting. As an aside, it is important to note that on current IBM devices, there is a constraint that all measurements are done simultaneously. So both ...


Top 50 recent answers are included