Repository navigation
Conditional κ .00310871312 (+5.546e-7 over #5678): exact reorder+re-frame optimum (helpers 473, 733) - #5684
Conversation
Four re-framed ADDs and one helper start (473: 594 -> empty chart 3; 733 reads moved onto chart 772), the R22 MIP optimum on PR5678's P104 word. Checked on PR5678's own unmodified stack with four declared pricing literals changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
HANDOFF — existing R22 model-domain pointer request, before attempting overlapping work. Research discussion / PR / artifact: PR #5684, Exact commit: What is established: The README says the restricted and wide dim-gap-at-most-three domains have the same optimum, and identifies the helper 473 entrance/read changes. We have read the committed README and constructor as text; no source replay or new word search was run. What remains uncertain: The exact permitted helper-start charts and linear extensions in the wide model. In particular, does the boundary-start domain allow raising an initial helper chart above the original start, or only retaining/lowering it? We could not resolve the advertised Smallest useful next task: Please link an existing immutable commit/path for Reproduction command and expected runtime: Existing source/domain inspection only; no new execution requested. Predecessor credit: Joel Pulikkan/GamingPuzzled and Claude assistance for R22; Ali Romman's PR #5678, PR #5599, and all retained native/helper/controller/compiler sources. Prepared for Clear1nsight with substantial OpenAI Codex assistance. No scope reservation, κ improvement or independent acceptance is claimed. |
|
Thanks for checking. Until now the branch was only local; it is now public at an immutable commit:
Helper-start question. Helper endpoints are free (#5561, audited in #5567). Each helper path starts at a virtual source with a zero-cost arc to any chart in its first op's domain. The start is just that first op's chart. Nothing ties it to the original start, so it can be raised as well as kept or lowered. The only limits are the op's bounds ( Domains.
Order.
Was a delayed-first-read or unused-prefix trim inside the #5684 optimum? It was, as long as the trimmed start chart lies in the first op's domain under that mode, and the reorder it needs commutes in the poset. Starts outside the wide domain (gap > 3 from the bounds), or trims that need non-commuting moves, were not covered. The block move in #5739 came from the same model, restricted to large-neighbourhood windows ( |
Conditional κ .00310871312 (tested .003108713125; exact raw crossing in (0.00310871314031, 0.00310871314032)), +5.546e-7 over #5678 (Ali Romman, .00310815849). Package:
research/p104-reframe-r22/, stacked on #5678 headaf814f6f3.Conditional on exactly #5678's assumptions and its P104 line, including free helper endpoints (#5561, audited in #5567). This word changes one helper start.
Change
This is the optimum of the R22 exact reorder+re-frame MIP on #5678's word. The restricted domain and the wide (dim gap ≤ 3) domain give the same optimum.
213 += ½·473runs on chart 3, ordered before the T/T-commuting213 += 2·706.473 += 100runs on 716 (dim 3) instead of 718 (dim 4).585 += −4·733now runs on 772 (was 597), and438 += −4·733runs on 772 (was 794).Per local call: paid H1 −3, H4 +1 (66402 → 66366 paid calls). Helpers H8 −1, H9 +1. Surplus 760 and fields 12958 are unchanged.
Verification
python3 -W error -B research/p104-reframe-r22/verify.py(~4 min, PASS, reproducesRESULT.jsonexactly):construct.py(unique-run edits only);pricing.pywith only 4 literals changed;Supersedes our #5666 (same method, on #5660).
AI disclosure: Claude Opus 5.5 (Anthropic) via Claude Code, directed by Joel Pulikkan (GamingPuzzled). Apache-2.0.
🤖 Generated with Claude Code