research-tree: 170 new-family holdout result (field gain transfers)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
7606833cee
commit
0957363465
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-20: **NEW-FAMILY HOLDOUT RESULT: H2's field gain TRANSFERS** (Zenodo 17831586, 170 cases / 98 ABC families, zero roster/near-duplicate overlap; frozen 5-fold ensembles of A, H2 seed 0, H2 seed 1, no retraining; pre-score PASS a670a4d4/f314ca15 + split PASS 06c35e1a; predictions frozen 202a01a1 before any target read; each Fill_time decoded once; result a236d696, target ledger 0f3cd58d). Family-weighted field relative L2, H2 − A, 98-family paired bootstrap (2,000, seed 2026111408): seed 0 −1.322 pp, CI [−1.721, −0.959]; seed 1 −1.364 pp, CI [−1.769, −0.971] → both FIELD_GAIN_TRANSFERS (pre-registered). Last fill: hit counts equal across the three; distance up for seed 0, slightly down for seed 1 (descriptive, no gate). Reading: on genuinely new part families from a different public release, the learned mesh model's field advantage over the tree model holds and is larger in absolute terms than on the grouped Greif protocol (−0.50 pp); last fill is still not improved. Limits: same solver/material/process as training; single gate per part; one release. Compute: 1a 37,748 CPU-s, 1b ~196 GPU-s, scoring 83 CPU-s.
|
||||
- 2026-11-20: **34 shared misses classified by true last-3 % region** (bounded CPU read, MeltAssist PASS 53c9c543; result by-part.csv 3d6c38e1; hypothesis-generating). Same region / different region / NA (peak > .10 Rg from every last-3 % component): H2 seed 0 4/5/25, seed 1 8/4/22, A 16/4/14 (A on query nodes only). **Reading:** for most of H2's shared misses the predicted last point is not in the true late zone at all; A's misses are mostly inside the right late region. This corrects my visual note (four pairs suggested 'same end region, different point' was the main case; that is the minority for H2) and is consistent with the S2 diagnostic (H2 more far-from-tail picks, 71 vs 49). Untested hypothesis: H2's predicted field has spurious late maxima away from the true late zone (endpoint = argmax is sensitive to small local errors), rather than a wrong branch choice.
|
||||
- 2026-11-20: **New-family holdout established: 170 cases / 98 families** (warpage set, Zenodo 17831586). ZIP verified on Horsea (MD5/SHA-256 49884675…). Geometry vetting under MeltAssist PASS d2a31203 (scope COMBINED_VTU_LOG_SCALE_YML_SURFACE_ALIGNMENT; Points/Cells only, Fill_time sealed): 173 pass (unit uniquely mm from LOG volume ≤ 0.5 %, counts, finite/positive volumes, YML inlet on surface), 23 excluded NO_LOG_SCALE_MATCH. Near-duplicates (pre-frozen < 1 % fingerprint rule) vs our 552 / 204 families: 0 of 95,496 pairs; within the set 0 of 14,878; roster identity overlap 0. Minus 3 cases with V/P switchover < 99 % (10555, 10656, 10941; pre-registered rule) → 170 cases / 98 ABC families: same solver, material, melt/mold temperatures and fill rule as Greif, complete fill, new families. This is the first independent test of 'new parts'. Next: frozen-model evaluation spec (pre-registered before any Fill_time read).
|
||||
- 2026-11-19: **Warpage set (Zenodo 17831586) metadata census: candidate new-family fill-time holdout** (Claude, HTTP range reads of the 392 LOG/YML entries only; no VTU bytes fetched; docs/claude/data/greif_warpage_log_census.csv sha256 e44ff604…, scripts warp_fetch.py / warp_census.py). 588 ZIP entries = 196 VTU + 196 LOG + 196 YML. All 196: melt 543.15 K / mold 318.15 K (same as main corpus), last filling-phase row 100 % 'Filled' before packing starts, packing profile 0 % (applies only after fill), no short-shot text; V/P switchover median 99.83 %, 193/196 ≥ 99 % (3 between 98.51 and 99 %); gate coordinates + normals present for all. **Family overlap: 110 ABC chunk hashes, 0 shared with the 249 v5 hashes, 0 shared abc_id+step.** Reading: under the pre-registered rule (complete fill, switchover ≥ 99 %, new families) 193 cases qualify as a same-process new-family holdout, pending (i) overlap check against our actual 552-part roster (v4-based) and (ii) a geometry near-duplicate check once the ZIP is on Horsea. Labels (nodal Fill_time) are listed in the record but untouched. **Access note:** Zenodo returned 403 to a 'Mozilla/5.0' User-Agent and 206 to curl's default UA from the same host; Horsea's 403s likely came from the UA I had suggested.
|
||||
|
||||
Reference in new issue
Block a user