Add backward propagating marks to Crumble #998
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added 3 instructions:
REVMARKX,REVMARKZ,REVMARKYto address Issue #665.These create backward-propagating Pauli marks using the same logic as the forward-propagating ones. As suggested by @Strilanc, they do not interact with the forward-propagating marks.
They can be inserted using
shift+<Pauli>+<#>, and I’ve updated the GUI accordingly:To motivate this feature, here are two example use-cases:
Visualising how double-check in the cultivation procedure translates to measuring the logical operator twice (with two clicks)
Checking that an encoding circuit correctly encodes the logical operator by propagating it backward (with one click).
✅ Passed Crumble tests