Skip to content

Added reference to published paper for Carbon and Tesseract Color codes#378

Open
marcusps wants to merge 2 commits into
errorcorrectionzoo:mainfrom
marcusps:marcusps/update-carbon-and-teseract
Open

Added reference to published paper for Carbon and Tesseract Color codes#378
marcusps wants to merge 2 commits into
errorcorrectionzoo:mainfrom
marcusps:marcusps/update-carbon-and-teseract

Conversation

@marcusps

Copy link
Copy Markdown
Contributor

Modified Codes:

Carbon code:

  • added reference to published paper, described new data (10 rounds of error correction, >51x improvement over physical baseline)

Tesseract color code:

  • added reference to published paper

Checklist:

I remembered to:

  • Include relevant citations I could think of (with \cite{...})

  • Create links to the other referenced codes (with
    \hyperref[code:...]{...})

  • Update the relevant meta changelog fields with my user_id (see
    users/users_db.yml; add yourself in the PR if you aren't there already)

marcusps added 2 commits June 28, 2026 20:43
Updated realization details for trapped-ion devices to include new data on error correction rounds and logical error rates.
Added reference to published paper
@marcusps

Copy link
Copy Markdown
Contributor Author

@valbert4 @phfaist

I don't understand exactly what led to the failure -- but the copilot assessment seems to indicate it is related to the arXiv API and thus not related to the changes proposed here?

Here is what copilot said was the cause (click on the triangle to expand)

The build is failing because the site build hits the arXiv API too hard and eventually gets rate-limited.

Root cause:

The citations that triggered the failure include:

  • arxiv:1912.04500 in codes/classical/homogeneous/symmetric/symmetric_space.yml
  • arxiv:1912.04500 in codes/classical/groups/permutation/binary_permutation.yml
  • arxiv:1005.4959 in codes/classical/bits/cyclic/quad_residue/golay.yml

Relevant files:

How to fix it:

  1. Prefer cached citation metadata instead of live arXiv fetches in CI.

    • Your workflow already restores eczoo_sitegen/_zoodb_citations_cache_LOCAL, but the current cache key includes ${{ github.sha }}, which makes it effectively unique per commit:
    • .github/workflows/quick-test-compile-zoo.yml:82
    • That prevents strong reuse across commits.
  2. Change the citation cache key so it can be reused between commits.
    For example, replace:

    key: zoodb-citations-cache-LOCAL-${{ github.sha }}-${{ hashFiles('**/yarn.lock') }}

    with something like:

    key: zoodb-citations-cache-LOCAL-${{ hashFiles('**/yarn.lock') }}

    or, better, key it on citation-bearing files if practical.

  3. If the build should not depend on external services, configure the site build to run in an offline/cache-only mode for PR CI.

    • That’s the most robust fix for transient 429/503 failures.
  4. If you need a content-side workaround immediately, reduce newly introduced uncached arXiv references in the changed files or replace them with already-cached/non-arXiv citation sources where appropriate.

Most likely minimal fix:

  • Update the cache key in .github/workflows/quick-test-compile-zoo.yml so the citations cache is reused across runs. Right now the per-commit SHA in the key is making CI refetch citations too often, which leads to the arXiv rate limit.

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