Repository navigation
Reject two T740 axis-search candidates on exact operator replay - #3263
Merged
Mister-Meeseeks merged 5 commits intoOct 17, 2026
Merged
Mister-Meeseeks merged 5 commits into
Mister-Meeseeks merged 5 commits into
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.
Result
This PR now records exact operator replays for two frozen T740 axis-search candidates. Our global CP-SAT rank-only model gives a hypothetical κ of about
0.001734807085759196…under PR #3200's verifier, but its owner-0 / port-0 operator differs at coordinate character2^53.A fresh overlap refresh found the higher open conditional headline in PR #3251:
0.001734815770385098563484. We pinned itsBINS,MOVESandRESULTartifacts to headd7d6254416f0b3ffe659079cca42fd152df63a36. The inherited PR #3200 numerical verifier accepts its profile and root, but the source-bound exact eight-stream replay finds a mismatch for its owner-0 / port-0 moves at character2^52. This one group is enough to reject that frozen allocation as operator-preserving. Its headline is about8.6846259e-9above our hypothetical; neither candidate supplies a new admissible κ here.The exact replay reports three changed Gaussian-integer matrix entries, and the registered package reproduces both witnesses. The selected record remains unchanged.
Scope and overlap
The global search spans 2,328
(port, child-usage)patterns and 82,880 groups; its false positive uses partially hosted donors (children 14 and 15). Related work in #3199, #3204 and #3220 is acknowledged. This PR adds candidate-specific exact counterexamples, not a proof that every exchange or repair fails, a full audit of either supplier stack, or a selected-frontier change.Reproduction
The registered replay authenticates both source stacks, verifies both conditional rank/profile results with the inherited PR #3200 auditor, positive-controls the exact baseline, reproduces the mismatches at
2^53and2^52, and rejects two mutation controls. The optional OR-Tools discovery run isFEASIBLE, notOPTIMAL, and its parallel incumbent is nondeterministic.