Skip to content

154, 339, 379, 380, 382; precision refinements at 211 and 241: registration request #586

Closed

Description

@franciscouzo

This updates #583 with five continued-search improvements and two tighter certificates. The unchanged n=302 and n=381 packings and the counts covered by #561 are omitted.

Displayed bounds are rounded upward to 12 decimal places from the exact rational certificate headers. Improvements are computed before rounding.

n / certificate New certified upper bound Comparison bound Improvement Comparison
154 12.921206577133 12.922499814643 0.00129324 #583
339 18.925319360704 18.926898900357 0.00157954 Evan Daniel
379 19.953531362123 19.953531531603 1.6948e-07 #583
380 19.961611078672 19.973553606628 0.0119425 #583
382 19.987713157610 19.988600568289 0.000887411 #583

For n=339, the comparison uses Evan Daniel’s stronger published certificate, rather than my larger bound in #583. Counts above 324 are submitted for the beyond-horizon list.

The following are certificate precision refinements of the n=211 and n=241 arrangements already submitted in #583:

n / certificate New certified upper bound Certificate in #583 Improvement
211 14.993558913975 14.993558914123 1.48631e-10
241 15.987117095151 15.987117095169 1.87519e-11

All seven certificates are pinned to b85dee2b964e7f7fb9f765227e60c44cdcd3aa4d in franciscouzo/square-packing. Each contains an exact rational container side followed by exactly n rational triples (x, y, t), with t = tan(theta/2). The certificate headers are authoritative; matching nN.json files retain full SHA-256 hashes and seed provenance.

The certificates for n=154, 211 and 241 were produced with Evan Daniel’s exact contact solver. The others are rational witnesses with centre dilation 1+1e-11 for n=339 and 1+1e-12 for n=379, 380 and 382.

All seven passed both jlevy/squares’ checker and Evan Daniel’s checker in exact rational arithmetic.

Both checkers use rational half-angle rotations and separating-axis geometry. These certificates establish finite packing feasibility; no local or global optimality proof or independent human review is claimed.

Lineage and credit:

  • 154: continued Evan Daniel’s arrangement from #552, descended from my earlier n=155 packing, through browser refinement, native basin hopping and exact finishing.
  • 211 and 241: retain Daniil Ostashev’s construction credit; these tighter certificates continue the refinements reported in 154-382: registration request #583.
  • 339 and 379: continue my L-border constructions from #506. The latest n=339 improvement used the browser’s fq search; n=379 used native SLP refinement.
  • 380 and 382: further browser fq refinements of Kevin Fang’s arrangements, retaining the construction credit from 154-382: registration request #583.

Evan Daniel’s optimizer, contact solver and verifier, David Ellsworth’s search/refinement ideas, and the upstream sqpack.verify checker were used.

The search implementation, verification orchestration and issue preparation used OpenAI Codex. Earlier search work also used Claude Code. I directed the work.

Activity

  1. added
    intakeTracking intake (saving, validation, tabulation, credits) of new results
    on Oct 14, 2026
  2. jlevy commented on Oct 14, 2026

    @jlevy
    Owner

    @franciscouzo, thank you for #561, #570, #583 and #586. This reply covers all four.

    Pins. We retained the certificates at the commits the issues pin: 0fa0e0de for #561 (nine certificates), and b85dee2b for #583 and #586 (14 certificates, the head of your repository when we read it). GitHub does not serve #570's commit 1b31bc90. Its 154 certificate has the same digest as the one #583 pins, so we read #570's 154 through #583, and #586 replaces #570's 379.

    Replay. Every retained certificate was replayed on both of this repository's exact checkers: the sqpack exact witness verifier and the independent rational corner checker. All 23 certificates passed on both. For each one, a duplicate-square control and an outside-container control were refused by both checkers. That is 69 jobs, and re-running every job reproduced its recorded outcome.

    Comparison with the current register entry at each count (sides rounded up at 12 places; for counts above 324, the register entry is the row tracked from your #506 certificates):

    n your side pin register entry below it by
    154 12.921206577133 b85dee2b case ceiling 12.923070202301 1.86e-3
    156 12.979165853835 0fa0e0de case ceiling 12.979172613644 6.76e-6
    176 13.807637227056 0fa0e0de case ceiling 13.812856253277 5.22e-3
    211 14.993558913975 b85dee2b case ceiling 14.996336721336 2.78e-3
    237 15.902947773659 0fa0e0de case ceiling 15.902949607677 1.83e-6
    241 15.987117095151 b85dee2b case ceiling 15.988132439524 1.02e-3
    271 16.948992356452 0fa0e0de case ceiling 16.949116687815 1.24e-4
    302 17.870013850405 b85dee2b case ceiling 17.872029849081 2.02e-3
    338 18.906332809853 0fa0e0de #506 row 18.906436500552 1.04e-4
    339 18.925319360704 b85dee2b #506 row 18.929433883808 4.11e-3
    344 18.993741872920 0fa0e0de #506 row 18.994353244944 6.11e-4
    375 19.901618621328 0fa0e0de #506 row 19.906335145009 4.72e-3
    376 19.904949736499 0fa0e0de #506 row 19.910276586885 5.33e-3
    378 19.942536155970 0fa0e0de #506 row 19.942541777355 5.62e-6
    379 19.953531362123 b85dee2b #506 row 19.953572709539 4.13e-5
    380 19.961611078672 b85dee2b #506 row 19.987440766556 2.58e-2
    381 19.974977397657 b85dee2b #506 row 19.992663288464 1.77e-2
    382 19.987713157610 b85dee2b no row; the grid, 20 1.23e-2

    Certificates no issue names. b85dee2b also holds certificates at 176, 344, 375, 376 and 378 that are newer than the ones #561 names. We retained, replayed and compared them too, and all five passed both checkers:

    n b85dee2b side register entry below it by
    176 13.807637226803 case ceiling 13.812856253277 5.22e-3
    344 18.993724693587 #506 row 18.994353244944 6.29e-4
    375 19.893906534236 #506 row 19.906335145009 1.24e-2
    376 19.904068025747 #506 row 19.910276586885 6.21e-3
    378 19.942519693846 #506 row 19.942541777355 2.21e-5

    We will register only the certificates the issues name unless you ask otherwise. Would you like these five registered in place of #561's at those counts?

    Registration is the next step. We will reply here when it lands, and we will keep the construction credits you list for each count.


    Generated by Claude Code

  3. franciscouzo commented on Oct 14, 2026

    @franciscouzo
    Author

    Hi @jlevy, please import all certificates

  4. jlevy commented on Oct 14, 2026

    @jlevy
    Owner

    @franciscouzo, thank you; this is the report-order evaluation of every open report at the counts #586 claims.

    At each count, a report is recorded when its side is decidably below every side reported before it (and below the record on main); a tie stays with the earlier report. Sides are rounded up at 12 places.

    n Side Verdict Best now
    154 12.921206577133 recorded: a new packing, continuing Evan Daniel's arrangement (#552); 1.29e-03 below #570 (Francisco Couzo) this report 12.921206577133
    211 14.993558913975 recorded: a refinement of the finder's own packing as #583 gives it; 1.49e-10 below #583 (Francisco Couzo) this report 14.993558913975
    241 15.987117095151 recorded: a refinement of the finder's own packing as #583 gives it; 1.88e-11 below #583 (Francisco Couzo) this report 15.987117095151
    339 18.925319360704 recorded: a new packing, continuing the author's own L-border construction (#506); 1.58e-03 below #584 (Evan Daniel) this report 18.925319360704
    379 19.953531362123 recorded: a new packing, continuing the author's own L-border construction (#506); 1.69e-07 below #583 (Francisco Couzo) this report 19.953531362123
    380 19.961611078672 recorded: a new packing, continuing Kevin Fang's published arrangement (TheSnakeFang/squarepack-certs); 1.19e-02 below #583 (Francisco Couzo) this report 19.961611078672
    382 19.987713157610 recorded: a new packing, continuing Kevin Fang's published arrangement (TheSnakeFang/squarepack-certs); 8.87e-04 below #583 (Francisco Couzo) this report 19.987713157610

    The registrations are in the records pull request #602, and a follow-up with the result ids and rungs will come once it is on main.


    Generated by Claude Code

  5. jlevy commented on Oct 14, 2026

    @jlevy
    Owner

    @franciscouzo, thank you. With #602 merged, every certificate at b85dee2 is on main, which answers your request to import them all:

    Both of our exact routes replayed every one of these certificates; an independent review of that replay comes next, then adoption on the case pages. This corrects our reply of 14 October, which said only the certificates the issues name would be registered unless you asked. At 211 and 241, Mykhailo Polkovskyi's #593 states the same exact sides; whether to record that tie is with the owner.

    Evidence: E-couzo-583-586-certificate-report (your report, recorded). On main: RESULTS.md, the packet.


    Generated by Claude Code

  6. added 2 commits that reference this issue on Oct 14, 2026
  7. jlevy commented on Oct 16, 2026

    @jlevy
    Owner

    @franciscouzo, thank you. Where this request stands in the record on main.

    Corrections to earlier replies.

    • The follow-up reply of 2026-10-14 gave T-182 as V0/C0, recorded; it now reads V3/C3, confirmed.
    • The follow-up reply of 2026-10-14 gave E-couzo-583-586-certificate-report as recorded; it now reads reviewed.
    • The follow-up reply of 2026-10-14 gave T-165 as V0/C0, recorded; it now reads V3/C3, confirmed.

    What is registered.

    • s(154) <= 12.921206577133, s(211) <= 14.993558913975 and s(241) <= 15.987117095151, by exact rational certificates:
      • T-182, confirmed at V3/C3: re-verified here by an independent implementation (sqpack.verify, run by each case's verify_exact module and the packing-witness command, devtools.check_rational_witness_independent, devtools.evand_arrangement_reports, devtools.upper_bound_reports, devtools.check_half_angle_area, devtools.evand_exact_certificates).
    • The same commit's certificate at 176, which no issue names, imported as you asked:
      • T-165, confirmed at V3/C3 by the same routes.

    On the case pages. Our reply of 14 October said adoption would follow the review. On 15 October 2026 T-182 became the house at 154, 211 and 241, and T-165 at 176; the packings they replace (Evan Daniel's T-160 at 154, Daniil Ostashev's T-149 at 211, your packing improved by Evan Daniel (T-098) at 241, and Nate Chaoweeraprasit's T-151 at 176) stay retained as history.

    Smaller certificates that are not adopted: Mykhailo Polkovskyi's of 14 October (T-186, V0/C0) at 154 and 176; at 176, PR #574's (T-174), whose houses are held for the owner; and, since #627 merged, your 487b058 certificate at 211 (T-188, V0/C0), 9.29e-6 below T-182, a refinement of this packing.

    Beyond the case corpus. 339, 379, 380 and 382, and the same commit's 344, 375, 376 and 378, are rows beyond the n ≤ 324 corpus, which take no register entry. 344 and 376 are still the current rows. Later reports supersede the others: Evan Daniel's #584 composition at 375, and since #627 your 487b058 certificates at 378, 379 and 380, and #607's at 339 and 382. The row at 376 lies above Göbel's classical construction, 10 + 7√2, by 4.57e-3, a question for the owner on #613.

    On main. packing/frontier/RESULTS.md, docs/project/reviews/review-2026-10-14-upper-bound-imports-561-593.md, packing/frontier/n-154.md, packing/frontier/n-211.md, packing/frontier/n-241.md, packing/frontier/n-176.md.

    Nothing you asked for is queued, so this issue is closed with this comment.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    intakeTracking intake (saving, validation, tabulation, credits) of new results

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions