Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quantum Tensor-product code #349

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Conversation

Fe-r-oz
Copy link
Contributor

@Fe-r-oz Fe-r-oz commented Aug 29, 2024

QuantumTensorProduct codes -- Examples below demonstrate the use of RepCode and BCH. Classical TPC via CSS constructions give QTPC. Now we can use classical codes to construct this quantum code! Classical TPC is tested and it is made sure to follow same conventions as Wolf paper.

These examples are added in test_ecc_base.jl so the they are tested for correctness.

Using Different Component Codes, H₁ != H₂
image

image

image

image

Using Same Component Codes, H₁ == H₂
RepCode(6)
image
BCH
image
H₂ from this paper
image

If you want to submit an unfinished piece of work in order to get comments and discuss, please mark the pull request as a draft and ping the repository maintainer.

Please address only one topic or issue per pull request! Many small PRs are much easier to review and merge than one large PR.

Before merging, all changes and new functionality should be marked in the CHANGELOG file, but feel free to just leave your CHANGELOG notes in the PR description, to avoid merge conflicts with other requests modifying that file. The maintainer will add these CHANGELOG notes for you if you do so.

Before considering your pull request ready for review and merging make sure that all of the following are completed (please keep the clecklist as part of your PR):

  • The code is properly formatted and commented.
  • Substantial new functionality is documented within the docs.
  • All new functionality is tested.
  • All of the automated tests on github pass.

If possible, keep your git history not too wild (rebase and squash commits, keep commits small and semantically separated) so that review is easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant