You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know why we haven't noticed this until now, but shouldn't the measurements be half zeros and half ones? I thought for certain this used to work at one point.
The text was updated successfully, but these errors were encountered:
The reason this came up was that I was quite skeptical that pauli frames would work to perform the "double syndrome measurement" encoding circuit, thinking mostly about how it would handle entangled states post-measurement . I wanted see if it had correct output for measuring the bell state, but it was all 0s, which lead to this discovery...
I think it is just a minor bug in how you define the sMZ measurement. It needs two arguments, not just one. Implicitly, if you have only one argument it means "measure this qubit and discard the result".
This works: pftrajectories(PauliFrame(20,1,1), [sHadamard(1), sMZ(1,1)]) |> pfmeasurements
We should have a warning when the circuit contain measurement that discard the result (i.e. when we have sMZ(qubit) instead of sMZ(qubit,bit)).
Krastanov
changed the title
PauliFrame initZ! not working properly
Raise a warning if pftrajectory (and others) if the circuit contains measurements that discard the result, i.e. sMZ(1,nothing)Sep 28, 2023
I don't know why we haven't noticed this until now, but shouldn't the measurements be half zeros and half ones? I thought for certain this used to work at one point.
The text was updated successfully, but these errors were encountered: