Repository navigation
Releases
Records snapshot
Every current record on polypack.fly.dev with its coordinates: the leader of each open problem, one gzipped JSON file per piece shape, named n-{N}.json.gz, holding every container shape M for that N (N is the piece shape, M the container shape; 0 is a circle, 3 or more a regular polygon). The release is refreshed every week, on Sunday, from a copy of the site's database.
As of 2026-11-15T12:30:47.224Z: 3,787,785 records, 850,049,527 pieces, 9,801 shape pairs in 99 files; and 122,791 records of the other kinds of problem in 8 files.
Download everything with the GitHub CLI: gh release download records --repo sinkomr/PolyPack. manifest.json lists every file with its size and SHA-256, and for each piece shape its pairs, each with the fingerprint of its records. One pair alone is at https://polypack.fly.dev/api/snapshot/{N}-{M}.json.gz (the site generates it when asked, from its records at that moment).
Units. Since 2026-10-27 ("units": "diameter" in the manifest) disk and ball pieces have diameter 1 (they had radius 1) and a circle or ball container is scored by its diameter (it was scored by its radius). Every file was rebuilt in the new units; a file of format 1 uses the old ones.
Format. (Format 3, since 2026-11-07, only means that the site generates each file when it is asked; the files hold what format 2's did.) Each piece shape's file is {"format": 3, "N": …, "pairs": [ … ]}, and each of its pairs is {"format": 3, "N": …, "M": …, "records": [ … ]}, one record per line. A record has P, score (container side, or diameter for a circle container), id, name, found_with, verification, created_at, container_phi and pieces as [x, y, theta], every number at full precision. Polygon pieces have side length 1 and circle pieces diameter 1; angles are in radians. The conventions are on the API page, https://polypack.fly.dev/api#snapshot, and the full entry of a record, with how it was found, is at https://polypack.fly.dev/api/submissions/{id}.
The other kinds of problem (curved 2D in 2D, 2D on 3D, 3D in 3D and 3D on 4D) have one file per space, named space-{space}.json.gz (surface, curved, sphere, torus, boundary, polyhedra), listed under spaces in manifest.json. Each is {"format": 3, "space": …, "records": [ … ]}, one record per line in the order the site lists the problems. A record has problem (its id, such as boundary/tesseract/cube/12), P, score, id, name, software, method, created_at and config, the configuration in its space's submission format (https://polypack.fly.dev/api#spaces), every number at full precision. The full entry is at https://polypack.fly.dev/api/spaces/entries/{id}.
Published values from the literature, with their sources, are in data/records.json. Closed problems take no entries and are left out: those with a proven optimum, and for the spaces also those that are infeasible.