Fix: parity reset for each image , thereby avoiding cFRQI to avoid cross image control gate interference#15
Draft
phantmgx wants to merge 1 commit intomoth-quantum:mainfrom
Draft
Conversation
…oss-image control gate interference
Contributor
|
Hi @phantmgx - thanks for your submission! I merged with duspic's fix, so if you would like to update this to work with it, that would be great - right now there is a conflict. If not I will do it myself, but it might take a while. |
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
2 participants
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.
Fixes a bug in
qpixl_parallel.pywhere the parity check (pc) was shared across all images during encoding. This caused corrupted outputs when combining images of different shapes, as control gates could affect the wrong image.This update resets the parity per image and applies control-X gates separately, preventing cross-image interference during encoding.
Fix aligns with what's discussed in issue #14. Reproduction steps are described there.