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
Currently
In our current implementation, we assume that when a qubit is assigned to the "WaitRule" which means that it is waiting for a message from other nodes before making decisions (perform Pauli frame corrections, wait to compare purification results, etc.).
This assumption holds when there is no classical message loss and when there is no delay in executing gate operations.
If message loss is introduced
This assumption will not hold and we need mechanisms to store messages for later uses inside the RuleSet/Runtime.
The text was updated successfully, but these errors were encountered:
Currently
In our current implementation, we assume that when a qubit is assigned to the "WaitRule" which means that it is waiting for a message from other nodes before making decisions (perform Pauli frame corrections, wait to compare purification results, etc.).
This assumption holds when there is no classical message loss and when there is no delay in executing gate operations.
If message loss is introduced
This assumption will not hold and we need mechanisms to store messages for later uses inside the RuleSet/Runtime.
The text was updated successfully, but these errors were encountered: