Review and replay wand125's sqverify_continuous (f30cc2c) for the two n = 40 lower bounds

Open
#533 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
testing

Research direction

Start by reviewing the retained tools/sqverify_continuous/ tool and its README, then compare lemmas C1–C6 and certificate.rs with src/slab.rs and the run function. Build the tool, verify source_sha256, and run its tests before replaying both n = 40 examples and their controls, including this repository’s mass controls. Done means the packet and mapped review are on main, replay receipts are retained by T-145 and the 6.718 entry (or the review explains why not), and #485 has a reply.

Written by the indexing model from the issue text.

Description

intake

What remains. wand125/square-packing f30cc2c publishes tools/sqverify_continuous/ (v3), a continuous-angle mode added to this repository's sqverify-fast. Its README decides both n = 40 lower bounds: T-145, s(40) > 1340000/199529, and the unregistered s(40) > 3359/500 of #485. Taking it in means:

  1. Retain the tool at f30cc2c in a packet (MIT code; the upstream documentation copies stay CC BY 4.0). Minutes.
  2. A soundness review of the mode: its lemmas C1 to C6 against src/slab.rs and the run function, the root-range coverage, the near-axis premise, and its certificate.rs, which differs from the reviewed declared-net source. About one review lane.
  3. Build it, check source_sha256 1266a8b9…, and run its tests.
  4. Replay both examples and their controls here, adding this repository's own mass controls.

It would be the first decision of the n = 40 continuous cover by code other than the producer's (GC-4 in the 10 October review). It shares components with sqverify-fast and follows the producer's method in outline, so it is independent code, not an independent method. It is recorded beside the rung and moves none.

Why it is held. The replay is priced at up to about 4.4 CPU-hours (c6718 up to 2.3, c6715 up to 1.9, the three controls about 10 CPU-minutes), from the README's six-thread walls. It waits for an owner budget, after the review.

Context. wand125's review on #485, edited on 12 October to link f30cc2c. Bead think-tln9 holds the 6.718 claim.

Bead: think-xzob.

Done when the packet and a mapped review are on main, the replay's receipts are retained beside T-145 and the 6.718 entry or the review records why not, and #485 has a reply.


Generated by Claude Code

Dominant language
Python
Stars
54
Forks
6
Avg merge
9h 11m
Merged PRs (30d)
239

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jlevy/squares

All issues in jlevy/squares

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.