Repository navigation
1d: improved upper bound 1.460217284022874* (600-cell step function) - #247
Merged
Merged
Conversation
Contributor
|
Replayed from construction.json at steps-re/c1d-certificate@9a09149 (sha256 3dd39fae...b3a28c, matches the PR), reading each stored double as an exact rational: C(f) = 698746209786798359455483373677229695641600 / 478522078482569620433992386249161163190849 = 1.46021728402287398... so the stated 1.460217284022874 is a valid upper bound (rounded up by about 1.5e-17). Two computations agree on the same fraction: the knot formula from the constant page (2n max|S_m| / (sum v)^2), and a direct piecewise-linear construction of f*f evaluated exactly at all 2401 knots and midpoints, with each midpoint checked to be the average of its neighbours. |
echul-seal
added a commit
to echul-seal/optimizationproblems
that referenced
this pull request
Oct 26, 2026
Rebased onto main after teorth#247 and teorth#248. Adds the [S2026] row after the [SCIEL2026] row, the [S2026] reference, a Recent progress line (previously 1.457854884921989*), and the README table cell.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Improves the upper bound on C_1d (signed third autocorrelation constant) from 1.463071582607559* to 1.460217284022874*. Adds a row to
constants/1d.md, a reference, the README table cell, and a "Recent progress" line. Markdown only.Evidence
698746209786798359455483373677229695641600 / 478522078482569620433992386249161163190849= 1.46021728402287398...The printed bound is rounded up.
python -I verify.py construction.jsonruns in under a second (standard library only).SHA-256 of
construction.json:3dd39fae744555179b0356b84e752db724e892bd23dda51403976edfb5b3a28cThe asterisk follows CONTRIBUTING (self-archived, too long to check by hand). Open PRs #234 and #243 touch the same 1d lines, so a small rebase may be needed depending on merge order. Happy to do it.
AI use
An AI agent (Claude Code) wrote and ran the optimizer and both checkers for me, and prepared this PR. The bound does not rest on trusting that work: anyone can rerun
verify.pyon the archived certificate in a second.