Repository navigation
B5c-2a: correlated_nd_pilot complete (judged under @1, @2 frozen); campaign next -> B5c-2b - #34
Merged
Merged
Conversation
…correlated_nd@2 frozen (44c5e77f1fb0); campaign next -> B5c-2b Task row and file carry the pilot headline numbers (1040 expected = 749 rows + 177 failed + 4 oom + 0 missing + 110 deferred; 307 accepted) and point at results/calibration/correlated_nd_wave1.json; board re-rendered offline. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
B5c-2a, the Insight task and campaign.
correlated_nd_pilotmoves tocomplete. The task row andtasks/correlated_nd_pilot.mdcarry the headline numbers: 1040 expected = 749 rows + 177 failed + 4 oom + 0 missing + 110 deferred; 307 accepted under@1. They also carry the freeze (44c5e77f1fb0) and a pointer toresults/calibration/correlated_nd_wave1.json. The evidence link is now autofit_inference#17.gaussian-x3-search-benchmark'snextnow names B5c-2b: realisations 2–3, then the 12 450-run scored-wave manifest and its probe, then the submit.bin/pyauto-insight board --offlinere-rendered the board.pyauto-insight check --offlinepasses,ruffis clean andpytest testsgives 204 passed.Parent: PyAutoLabs/autofit_inference#18.
Decisions taken
Each one is flagged for the human. Each has a one-line revert.
--mem = max(8 G, ceil(2 × peak))per cell class (dataset × search × settings, both backends). The peak is the largest sampledsacctMaxRSS, or 8 G when any pilot task was OOM-killed. Sampled RSS undercounts the peak at a kill: task 304 read 3.1 G when it died at 8 G. This raises two cells: d50 Nautilusn_live_400to 16 G and d100 cold NUTS to 17 G (MaxRSS 8.1 G). Revert: setMEMORY_HEADROOMincalibrate_correlated_nd.pyand regenerate.n_live_200is deferred from the scored menu, along withn_live_400andn_live_100. All 40n_live_200/400attempts failed at the pin within 31–74 s, before the first bound was sampled. The cause is nautilus's HDF5 checkpoint: it cannot store a D = 100 bound attribute (h5py "object header message is too large"). Affordability therefore cannot be judged from the pilot walls; for comparison, d50n_live_200took a median of 820 s.n_live_100is deferred by construction: Nautilus needs n_live > D. d100 warm NUTS is deferred with its provider. Revert: drop the entries from_correlated_nd.A2_DEFERREDin a later amendment, after a library or nautilus fix.n_live_100(both backends) and d50 warm NUTS are deferred by the §7 cap rule, read as "no attempt ended on its own". In each, 9 of 10 attempts hit the 4 h cap and the 10th was OOM-killed before the cap. Revert: calibrate with "every attempt Terminated at the cap" only. Those two cells would then get timeouts from zero completed rows, so they would be probe-first.@2, read literally from "a band moves only on ≥ 20 completed pilot rows of its task". The evidence task moves to [0.85, 1.1] on 79 rows. The posterior task has 1 row, so it keeps [0.5, 2.0].@1had one shared band. With a single band, 34 of the 307 accepted pilot rows would have flipped, all of them BlackJAX NUTS (500 samples), judged by Nautilus σ noise. Revert:FROZEN_CND2bands as plain tuples (one band for both tasks).n_live_200rows (σ ratios 0.04–0.13) pass the medians against the banana's wide reference σ, and without §4(c) they would drag the lower band edge to 0. Revert: drop the(c)filter incalibrate_correlated_nd.calibrate.oomattempt class. SLURM's OOM SIGKILL exits 137 undertimeout, the same code as the cap's own kill. The pilot submit therefore wrote cap stubs (process wall = the 4 h limit) for the 4 OOM tasks, which would have been counted as censored cap failures.cnd_cap_stub.py --reconcile-oomrewrote them from the committedsacctextract (MaxRSS, real wall). Under@2, anoomrun is rerun once at twice its cell's request, and a secondoomis a failed attempt. Revert:git revertthe reconcile commit._posterior.chain_diagnostics, which relabelled byg0.centre. The fix isrelabel=Falsefor families with no label symmetry. Pilot verdicts stay@1(failed). Those 8 cells have no completed row, so they are probe-first in the scored wave. Revert: revert commit b3845e8's_posterior/_runnerhunks.Witness checklist
correlated_nd_pilotrow are closed with the pilot verdicts.correlated_nd@2is frozen (autofit_inference 44c5e77f1fb0), and the sha is recorded in both organs.🤖 Generated with Claude Code