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
The complete pinned PR1668 replay spends time multiplying binary incidence zeros by kernel coefficients. A source-bound adapter replaces only that predicate:
Claim type: scoped implementation-equivalence proof, exact operation-count certificate and local performance evidence. The complete workload removes 15,732,800 zero products and 1,408,228 unit multiplications. Its scientific stdout and every reached kernel result are identical. Fifteen alternating fresh-process pairs reduce median direct replay time from 1.801392 s to 1.604257 s, 10.94%; every pair improves and all thirty outputs agree. Ranges are 1.787448–1.983607 s and 1.573416–1.769150 s. This is local to CPython 3.12.15 on a shared macOS arm64 host, not a portable speed guarantee.
The original scientific source and credit stay unchanged. Its SHA256 is authenticated before compilation, and
optimize=0retains its assertions under an optimized adapter. No rank, geometry, fixture, scientific control or theorem changes. Discovery stopped at this first verified improvement.This contribution was produced by Nick Petalas. Credit Josie Elliston / PR1668 and PR1650, Andrey Mas / PR1560, Aaron Wang / PR1649 and the retained Brett Halligan, themilkman216 and DreamingOfClouds decoder lineage. Sparse dot products are classical; the new contribution is the bounded adapter and its exact complete-workload saving. The predecessor mathematical result is cited, not independently audited or claimed as new.
Evidence
5ece3cdbfec55235c3d95cfcf7bae6448b31cc6b7d4504676c06a7200ec9ce4b.Reproduce from the repository root with the exact available interpreter, or substitute another absolute CPython 3.12 path:
Expected conformance marker:
PASS_FRAME_KERNEL_SPARSE_PRODUCTS. Receipts are generated on stdout and bind package bytes; no receipt is handwritten. Sparse checkouts must materialize this package andresearch/full-family-g-without-d.Limitations
This accelerates one exact scientific replay. It supplies no independent mathematical acceptance, new kappa, native supplier, physical caller, recursive invoice or selected-frontier change. All five selected framework assumptions remain. No P105 runtime is inferred. Timing is observational and is not a CI gate. Independent human and formal proof-kernel review, Lean, Docker and the complete selected scientific cold replay are unrun. No required local mathematical or implementation check is deferred to CI.
The executable has bounded row/vector shapes. Python allocation, the fixed-hash reference loader, the bounded comparison callback and the retained source's depth-eight frame enumeration have explicit implementation-scope deviations in the README. No general arbitrary-object or streaming-iterator replacement contract is claimed.
Open next questions
Can a separately budgeted larger incidence replay benefit from the same binary-row contraction? First profile one complete command and prove every replaced row is binary. A source-bound larger workload, its complete conformance evidence and its end-to-end performance remain missing. No rank or geometry optimization is included here.
Related open work
The completion refresh listed the thirteen other account open PRs created since the advance CLAIM and screened their titles and bodies for this exact source and quantity. PR6569 is the adjacent replay-engineering contribution listed above; PR6565 studies different Schur/header counts. No competing computation of this exact command or disagreement in a shared computed number was identified. No extra computations audited another contribution.
The live exact-source search found no open PR changing the PR1668 kernel predicate. Main and merged-object searches, current claims and this account's recent work were checked before committing. The broader helper covered 506 open PRs and 6,503 Discussion records; sparse local notes, arbitrary historical diffs and unpublished work remain coverage limits. Advance CLAIM.
CI notes
Both hosted checks passed at exact head
a5f300a6358543eaa4bb6fe75b8054398cac273bin run 41610572423: plan in 4m30s and registered package replay in 1m41s. The completed checks were read once. Separate run metadata confirms the matching head, completed status and successful conclusion.Both registered normal/optimized commands and the local metadata, byte/ancestry and export checks passed. CI certifies execution of the registered implementation-conformance checks. The local timing percentage and the predecessor mathematical theorem are not independently certified by CI. No check failed; independent human and formal proof-kernel review remain unclaimed.
Merge Danger
Door: two-way. Blast radius: one isolated opt-in research package. The retained source, shared replay machinery and selected result are unchanged.