AXIOM BOINC SESSION LOG - PART 3 SAVE SUMMARY Date: March 04, 2026 Time: 08:24 (America/Denver) Source logs: validate_2026-03-04_0822.txt, run_2026-03-03_1352.log PART 1 VALIDATION/CREDIT SUMMARY - Reviewed and credited 129 completed results (success payloads only in this batch). - Session credit awarded: 1,278 total. - Runtime quality for credited batch: min=67.73s, median=844.54s, max=918.95s. - Dominant reviewed families: interdep_flow_memory_shedding_tradeoff, nonmarkov_trap_release_window, metapop_allee_corridor, pit_delay_inhibitor_resonance, plus fiberbundle/grayscott delay variants. CREDIT DISTRIBUTION (SESSION INCREMENT) - ChelseaOilman +636 - Orange Kid +320 - Steve Dodd +136 - _Scandinavian_ +46 - WTBroughton +38 - Vato +30 - marmot +20 - PyHelix +12 - [DPC] hansR +10 - kotenok2000 +10 - makracz +10 - vanos0512 +10 QUEUE CLEANUP / TRIAGE - Dead-host stuck-task aborts (>12h run, >6h host silence): 0 - Hard-ceiling aborts (>48h run): 0 - Broken-prefix emergency aborts: none - Retired-prefix active checks remained at zero for the tracked broken set. PART 2 DEPLOYMENT / RESEARCH SUMMARY - New CPU experiment script created and uploaded: wd_batchnoise_interaction.py - Hypothesis: late WD benefit is stronger under small-batch gradient noise than large-batch training. - Script validated on server with python compile check. - Retirement pass executed before deployment: ABORT_TOTAL=0 (no unsent rows for retire-list prefixes). CPU DEPLOYMENT - Deployment scripts used: wd_batchnoise_interaction.py, wd_labelsmooth_interaction.py - CPU host scan: 81 hosts seen; 2 skipped (<6 GB RAM) - CPU workunits created in deployment run: 2,937 - Targeting policy used: fill to ~3x CPU queue depth per host with host-targeted naming and replication. GPU CHECKPOINT - GPU deployment pass used scripts: wd_curvature_trigger_gpu.py, wd_timing_scale_gpu.py - Run log shows GPU pass started as a separate mandatory phase. - Current queue snapshot for those GPU lines (live DB check at save time): - wd_curvature_trigger_gpu: 14 hosts represented, 107 total result rows, 6 queued - wd_timing_scale_gpu: 15 hosts represented, 96 total result rows, 7 queued - Combined snapshot: 15 GPU hosts represented, 203 total rows, 13 queued NOVELTY CHECK DOCUMENTATION (PART 2) - Novelty/literature checks were run prior to deployment using targeted web queries, including: - weight decay x label smoothing interaction - adaptive/scheduled weight decay mechanisms - batch-size x weight-decay generalization interaction - decoupled weight decay prior art (e.g., AdamW lineage) - New line selected for deployment focus: interaction-specific mechanism test (wd_batchnoise_interaction) rather than re-running already-settled WD families. KEY SCIENTIFIC FINDINGS 1. The March 04 validation batch was fully parseable and success-only (129/129 experiment_result payloads), indicating clean data quality for credited outputs. 2. Delay/control ecology families continue to produce substantial successful throughput in credited returns, with median runtime around 14.1 minutes. 3. No immediate queue pathology was observed in this cycle (no dead-host stuck aborts, no >48h aborts, no cross-host all-fail emergency prefix). 4. Active WD research is now centered on mechanism-level interaction tests (batch-noise interaction, label-smoothing interaction, and curvature-trigger GPU timing) rather than broad legacy WD sweeps. SESSION NOTES - This log intentionally omits cumulative result-ID ledgers; authoritative credit state remains in BOINC/MySQL.