Skip to content

data: rename 19 tier5 stems with reproduced CC lower bounds (GH-225 follow-up) - #232

Merged
guluchen merged 7 commits into
mainfrom
data/gh225-lb-push
Nov 8, 2026
Merged

guluchen merged 7 commits into
mainfrom
data/gh225-lb-push

Conversation

@guluchen

@guluchen guluchen commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

Follow-up to #230. This PR renames 19 tier5 stems (four of them now exact) whose lower bounds were raised in 12-36 h runs on a dedicated server. Each value is reproduced in the batch: same matrices, and only the Gx/Gz header comments change, as in #230 / #223.

Rule used: a value goes into a stem only when two runs with different search trees reached it, with the last level EMPTY on both halves (X half only under a verified XZ-dual map). This is the same CC engine family, not an independent second method.

Arms:

  • C = main 755e0c2's CC default (gated erasure).
  • E = main 1239e9a's CC default plus ungated erasure.

C and E differ in binary and gating. TN_684 uses relabelled E runs instead; COLOR_2791 uses a bfs row order.

Old (main) New Arm 1 (s) Arm 2 (s)
BB_1080_4_32to48 BB_1080_4_34to48 C 40 586 E 44 390
BB_756_16_32to34 BB_756_16_34 (d = 34) C 59 834 E 65 917
BB_864_4_32to40 BB_864_4_34to40 C 58 134 E 64 158
COLOR_1027_1_31to37 COLOR_1027_1_33to37 C 78 893 E index 77 146
COLOR_2791_1_28to61 COLOR_2791_1_30to61 C 42 701 C bfs 79 340
TN_288_2_22to24 TN_288_2_24 (d = 24) C 98 733 E 100 460
TN_324_4_23to25 TN_324_4_24to25 C 72 074 E 72 807
TN_360_4_23to24 TN_360_4_24 (d = 24) C 47 415 E 48 186
TN_396_4_23to26 TN_396_4_24to26 C 47 489 E 47 923
TN_432_8_23to29 TN_432_8_25to29 C 87 063 E 89 519
TN_468_4_23to29 TN_468_4_25to29 C 107 865 E 110 270
TN_496_2_28to30 TN_496_2_30 (d = 30) C 117 232 E 119 072
TN_504_2_24to34 TN_504_2_25to34 C 54 147 E 56 955
TN_540_4_24to34 TN_540_4_25to34 C 57 564 E 63 505
TN_576_2_24to37 TN_576_2_26to37 C 79 691 E 88 962
TN_612_2_24to40 TN_612_2_26to40 C 97 484 E 107 037
TN_648_10_22to32 TN_648_10_23to32 C 53 620 E 58 436
TN_648_14_22to28 TN_648_14_23to28 C 70 302 E 63 576
TN_684_2_24to29 TN_684_2_25to29 E -seed=1 106 893 E -seed=2 105 414

Checks on the solved stems and on all others:

  • verify_levels.txt: in all 71 runs every recorded level is EMPTY. The missing levels are the odd levels of the BB codes (parity rule), and verify_parity.txt confirms that every column of Hx and Hz has odd weight there, in pure Python.
  • verify_dual.txt: the XZ-dual maps of the X-half-only codes are re-checked in pure Python: BB_756, BB_864, BB_1080 (halfswap-inverse), COLOR_1027, COLOR_2791 (identity, Hx = Hz) and TN_496 (tanner-swap). The TN_496 map was dumped from a scratch patch of 755e0c2, which is not in any commit.
  • Upper bounds are unchanged, and the upper-bound witnesses of the 17 TN/BB stems are re-verified under the new stems in optimization/experiments/GH-146/witnesses/renamed-2026-11-07/VERIFY.txt (17/17 VALID). For the four solved stems the lower bound meets a witness of that weight.
  • All four solved stems: both arms printed o d and passed the runner's science check. Their stems were {lb}to{ub} on main.

Caveats:

  • C and E both use the erasure rule (gated and ungated), so a soundness bug in shared code would affect both. Runs without erasure reached only the lower values noted in the rename history.
  • COLOR_1027's two arms use the same row order and differ only in gating and binary (level 32: 38.0G vs 36.3G nodes), so that pair is the weakest of the set.
  • The first batch (12 h, data: rename 19 tier5 stems with reproduced CC lower bounds (GH-225 follow-up) #232's original commit) already reached some of these values with intermediate stems; the rename-history rows here show the final stems only, with the earlier times where useful.

Not renamed: COLOR_2791 lb 31 (only C, 88 551 s; PLAUSIBLE).

Records are in optimization/experiments/GH-225/lb-push/ (REPRODUCTION.md, summary.md, verify_*.txt, push1-push5, repro3).

Changes:

  • git mv of the matrix files;
  • rename-history rows and the witness note in data/matrices/README.md;
  • NOTICE sections 5 and 9;
  • stem names in optimization/baselines/SERVER.md, main_server_reference.json and README.md (examples), and in the untiered MANIFEST.csv, validation.json and README.md.

QDistSAT mirror: guluchen/QDistSAT#19 (same branch name); all 80 matrix files are byte-identical.

Hub: #15; follow-up to #225.

🤖 Generated with Claude Code

…H-225 follow-up)

TN_288_2_23to24 (was TN_288_2_22to24), TN_432_8_24to29 (was TN_432_8_23to29),
TN_468_4_24to29 (was TN_468_4_23to29), TN_576_2_25to37 (was TN_576_2_24to37),
TN_612_2_25to40 (was TN_612_2_24to40), COLOR_1027_1_32to37 (was COLOR_1027_1_31to37),
COLOR_2791_1_29to61 (was COLOR_2791_1_28to61). Same matrices; only the Gx/Gz header
comments change. Each lower bound was reached by at least two CC runs with different
search trees (gated-erasure main 755e0c2 and ungated-erasure main 1239e9a, or a
different row order); same engine, not an independent method; upper bounds unchanged.

Records: optimization/experiments/GH-225/lb-push/ (12 h runs, yfclab2 CPUs 64-95); witness copies in optimization/experiments/GH-146/witnesses/renamed-2026-11-07/ (5/5 VALID).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@guluchen

guluchen commented Nov 6, 2026

Copy link
Copy Markdown
Owner Author

All checks pass. Merge is on hold together with the QDistSAT mirror (guluchen/QDistSAT#19), so the two repos keep the same stems. The mirror's test (3.9) job fails in setup: ubuntu-latest is now Ubuntu 26.04, which has no Python 3.9. The fix needs a QDistSAT workflow edit that our token cannot push.

…und 34

lb 34 reached by main 755e0c2's CC default (40 586 s) and by main 1239e9a plus
ungated erasure (24 h run, 44 390 s), different trees; same engine, not an independent
method; upper bound unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@guluchen guluchen changed the title data: rename seven tier5 stems with reproduced 12 h CC lower bounds (GH-225 follow-up) data: rename eight tier5 stems with reproduced CC lower bounds (GH-225 follow-up) Nov 7, 2026
yfc and others added 3 commits November 7, 2026 15:56
…2_25to34, TN_648_10_23to32

Each lower bound was reached in 36 h runs by main 755e0c2's CC default (gated erasure)
and by main 1239e9a plus ungated erasure (different trees). On TN_360 the lower bound
24 meets the GH-146 weight-24 witness, so d = 24. Same engine, not an independent
method; upper bounds unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…_4_25to34, TN_648_14_23to28; COLOR_1027 33, COLOR_2791 30

Each lower bound was reached in 36 h runs by two configurations with different search
trees (main 755e0c2's CC default with gated erasure, and main 1239e9a plus ungated
erasure; for COLOR_2791 a bfs row order). On BB_756 the lower bound 34 meets the
GH-146 weight-34 witness, so d = 34. COLOR_1027_1_33to37 and COLOR_2791_1_30to61
replace the intermediate 32to37 / 29to61 names of this branch. Same engine, not an
independent method; upper bounds unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add the results of the finished 36 h runs: TN_288_2_24 (d = 24) and TN_496_2_30
(d = 30) solved, TN_432_8_25to29, TN_468_4_25to29, TN_576_2_26to37, TN_612_2_26to40
and TN_684_2_25to29. Each new value was reached by two runs with different search
trees and has its last level EMPTY; the solved stems' upper bounds are the GH-146
witnesses, 17/17 VALID in renamed-2026-11-07/VERIFY.txt. Odd-level parity and the XZ-dual
maps of the X-half-only codes were re-checked in pure Python (verify_parity.txt,
verify_dual.txt). The intermediate 23to24, 24to29, 25to37, 25to40 and 29to30 names of
this branch are folded into the final stems in the rename-history rows and notices.
Same engine, not an independent method; upper bounds unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@guluchen guluchen changed the title data: rename eight tier5 stems with reproduced CC lower bounds (GH-225 follow-up) data: rename 19 tier5 stems with reproduced CC lower bounds (GH-225 follow-up) Nov 8, 2026
guluchen and others added 2 commits November 9, 2026 06:59
Remove host names, absolute paths, CPU assignments and load samples.
Solver output, timings, bounds and level records are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…oved

The previous commit emptied these files by mistake; restore them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@guluchen
guluchen merged commit fae495b into main Nov 8, 2026
3 checks passed
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