Repository navigation
Conversation
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.
Summary
Scoped proof with an exact finite influence certificate. This contribution was produced by Nick Petalas. On the selected #5599 P104 word's first common-frame scalar block:
The stochastic statement holds simultaneously for every real output at one stream sample, for arbitrary incoming grid values including dirty helpers. The complex componentwise failure bound is below 2^-22. These are different guarantees and sufficient certificates; neither precision is proved optimal. The exact intermediate endpoint need not be integral. No new kappa, full rounded supplier, exact dirty restoration or selected-frontier change is claimed.
The new result is the exact source-bound noise certificate and its explicit precision/failure specialization. Stochastic rounding and bounded-martingale arguments are classical, as in Connolly, Higham and Mary (2021). Ali Romman's #5599 word, Pierre-Loic Doulcet / hexapode's #5565 contacts and the complete retained predecessor lineage supply the frozen construction, which is cited rather than audited.
Evidence
max L_j = 90, hence error at most45h. It certifies a strict error below 1/2 at seven bits, while its six-bit bound is 45/64. This does not prove that six-bit nearest rounding fails.max S_j = 733/8, with 282 nonzero output influences. A 65-term positive rational Taylor sum proves564 exp(-16384/733) < 2^-23.From the repository root:
Another CPython 3.12 path may replace the displayed interpreter; standard library only. Expected markers are
PASS_P104_STOCHASTIC_PREFIX,PASS_REGISTERED_RESEARCH_PACKAGEandPASS_RESEARCH_COMMIT_BYTES.Limitations and unrun obligations
Each noninteger dyadic scalar update is evaluated exactly, then rounded once with fresh conditional randomness. Initial values must already lie on the grid; saturation and overflow are excluded. The prefix stops before event 9589, the first MOVE. Native approximation, later blocks, off-grid conversion, physical sampling and its arithmetic/storage/tape costs, exact cleanup, compiler/stock obligations and analytic recovery are unproved. At M stream samples, the union bound gains a factor M. All five selected framework assumptions remain. Independent human and formal proof-kernel review are unclaimed. Lean, Docker, a full native/supplier replay and a complete multiplier were not run.
The proof includes a reused-coin counterexample to the variance bound and a rounded inverse that fails exact restoration. A local probabilistic enclosure does not supply those caller contracts.
Open next questions
Related open work
Related descriptions use PR bodies as context. No extra computation was run to validate another contribution or compare its numbers.
CI notes
CI pending at head
e5b18b6c00e7236700e6f46905d394dfdfef7506. All local registered and publication checks pass. No hosted certification is claimed yet.Merge Danger
Door: two-way. Only six new files in an isolated research package are added.
Blast radius: package. Shared code, frozen evidence and selected-frontier files are unchanged.