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
Different orders of instructions in the same tick will result in different timeslice-svg plots. For example, the following code produces the correct time slice plot as expected:
It seems that every time a noise instruction is plotted, a global coordinate shift will be applied regardless of the type of subsequent instructions. However, coordinate shifting should only occur with noise instructions, not with any other instructions.
Stim version: 1.13.0
The text was updated successfully, but these errors were encountered:
This is because internally everytime it sees an operation happen on a qubit again within one tick, it increments an internal subtick value. That was the fastest safest way to be sure there were no ordering bugs and no ambiguity about the order things are declared in the circuit.
Probably what should be done here is to have a subtick per qubit, and to take the max subtick + 1 of the qubits affected by the operation then set all their subticks to that value.
Different orders of instructions in the same tick will result in different
timeslice-svg
plots. For example, the following code produces the correct time slice plot as expected:However, when the instructions
R
/RX
andDEPOLARIZE1
are placed alternatively, the time slice will be plotted incorrectly.It seems that every time a noise instruction is plotted, a global coordinate shift will be applied regardless of the type of subsequent instructions. However, coordinate shifting should only occur with noise instructions, not with any other instructions.
Stim version: 1.13.0
The text was updated successfully, but these errors were encountered: