research-tree: item c fails pre-registered screen, pruned
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
8a4d756541
commit
ce31bec73e
1 file changed
+1
@@ -34,6 +34,7 @@ Rules:
|
||||
| P3 | O1 with size-matched K = 8 partitions | — | — | PRUNED (eligibility 23 %; lesson: control cut area as a covariate, do not match it) |
|
||||
|
||||
Log (newest first):
|
||||
- 2026-11-19: **Item c (last-fill-aware objective inside H2) FAILS its pre-registered screen; PRUNED (this recipe).** Recovery postfit (PASS 59a6255f, one labelled infrastructure recovery after a pre-worker guard KeyError, 0 targets read in the stop) COMPLETE, 552 / 204. c − H2 seed 0: last fill +.0193 Rg, CI [−.0559, +.0948] (gate needed ΔD ≤ −.010 with upper bound < 0, and |effect| > the same-domain seed spread .0482: not met); field +.00029, CI [−.0013, +.0019] (upper bound above +.001: fails); τ-b +.00037, CI crosses 0. Secondary (reported separately, no gate): last-1 % tail error E_tail +.066, CI [+.044, +.087], i.e. *worse* tail placement; peak certificate 0 for every arm. **Reading:** this location-aware objective did not move the last-filled point, and by the secondary metric it moved the late region the wrong way. That closes this recipe, not the question: the S2 diagnostic (more far-from-tail picks) still stands as H2's main weakness. 630.73 GPU-s postfit including the stop.
|
||||
- 2026-11-19: **Track A (Gre24-style random-split protocol) scored, and seed-1 noise reference scored** (MeltSol, evidence fee71ea6; original bindings 958abd8c/a5fa4a6e and 7b4da089, each run once). **Track A:** splits 0/1/2/4 (split 3 stopped on budget, disclosed; 14 preparation failures disclosed; our own random splits), 1228 paired test visits / 571 unique parts. Split-averaged median per-part RMSE/max: A 3.99 % → H2 3.25 %; per-part paired Δ −.00742, CI [−.00844, −.00646]. **Reading:** on the same re-created random splits H2 clearly beats A. This is *not* a SOTA claim against Gre24's table: our A on these splits gives 3.99 %, not the paper's 3.31-3.38 %, so the plan's reproduction gate is not met and the gap between H2 3.25 % and the paper number is not interpretable (four splits, different seeds, random splits leak families). **Seed-1 vs seed-0 (H2, grouped protocol, 552/204):** field +.00015, CI [−.00143, +.00204]; last fill −.048 Rg, CI [−.122, +.024]; τ +.00004, CI crosses 0. **Reading:** the seed spread is small for the field (about 1/30 of H2's −.005 gain, so the field confirmation is not a seed artefact). For last fill it is about .05 Rg, comparable to H2's +.080 last-fill loss, so single-seed last-fill differences are noisy. c and b will be read against the same-domain seed-1 reference, as their bindings specify.
|
||||
- 2026-11-19: **All phase-3 training terminal, no scores yet** (TRON read-only, 07:10 and 07:30 CST). seed-1 v2: five folds PASS, 105,759.84 GPU-s; postfit PASS 7b4da089 already adopted, postfit not started. b: five folds PASS, 95,685.04 GPU-s on the ledger (9,647.52 of it charged waiting), postfit binding not yet written. For c, seed-1 and b: no prediction, scoring or test-target read; 7,200 GPU-s postfit reserve each. Horsea has no compute processes. Native routing is still missing; order once it returns: c postfit review → Track A shared-slot narrow review → seed-1 postfit → b postfit binding + review.
|
||||
- 2026-11-19: **Item c training terminal** (TRON read-only, 05:20 CST): five folds PASS, TRAIN_COMPLETE_POSTFIT_REVIEW_PENDING, 105,362.42 GPU-s spent + 7,200 postfit reserve; no prediction, scoring or test-target read. **Native routing is down** (tool update removed TRON's Codex session send), so c's postfit review and Track A's shared-slot delta review (3e62e08c) are held, with no Slack substitute and no TRON exception. seed-1 (4 PASS / 1 active) and b (5 active) keep running.
|
||||
|
||||
Reference in new issue
Block a user