summaryrefslogtreecommitdiff
path: root/results/confirmatory/clean_sparsity/cifar_dfa_s42.json
diff options
context:
space:
mode:
authorYurenHao0426 <Blackhao0426@gmail.com>2026-04-07 23:17:45 -0500
committerYurenHao0426 <Blackhao0426@gmail.com>2026-04-07 23:17:45 -0500
commit5771a122300f9d30a6290fcbfc9bffb5f380e648 (patch)
tree66cc0c179dd103c3003953ab91d8e4e816f5f4f2 /results/confirmatory/clean_sparsity/cifar_dfa_s42.json
parent5dadf7b78cbd3332b48a3ec0c385e3aeaea253a6 (diff)
Partial protocol audit on penalized DFA: (a)+(b) pass, (d) still fires
3-seed analysis of DFA + lambda=1e-2 ||f||^2 penalty using only the data already in the existing penalty JSON logs (no checkpoint or full layer norms needed): (a) per-block growth: avg ~8x per block (geom mean), well below 50x threshold. PASS likely (with small caveat that max could differ from mean). (b) BP grad floor: g_2 = 8-10e-7 across 3 seeds, 10x above the 1e-7 floor. PASS exact. (d) frozen baseline: margin = 1.35-1.45 pp (mean 1.38) < 2 pp required. FIRE on all 3 seeds. Aggregate partial verdict: protocol catches the SECOND failure mode (direction quality / passive blocks) on penalized DFA even though it PASSES the scale-related diagnostics. This is the cleanest possible evidence that the two failure modes are separable: the penalty fixes the scale failure but not the direction failure. The protocol's (d) diagnostic is the right test for the second failure mode and it still fires after the penalty rescue. This is the ยง4 'two failure modes' evidence that doesn't depend on the direction-quality direct test (which is still running). The (d) diagnostic alone shows the separation.
Diffstat (limited to 'results/confirmatory/clean_sparsity/cifar_dfa_s42.json')
0 files changed, 0 insertions, 0 deletions