summaryrefslogtreecommitdiff
path: root/paper/figures/render_fig5_cross_arch.py
diff options
context:
space:
mode:
authorYurenHao0426 <Blackhao0426@gmail.com>2026-04-08 20:51:04 -0500
committerYurenHao0426 <Blackhao0426@gmail.com>2026-04-08 20:51:04 -0500
commit5995929511404ba3e0b8b4f1bfef69dbf291c7a9 (patch)
tree78ed5677f26799533511ff69eb0262dc52ca579d /paper/figures/render_fig5_cross_arch.py
parent29c2396ee6480e94d4543cb603587a4cc7b640cd (diff)
paper v2.37: §7 add 'Open questions and concrete next experiments'
§7 currently has only the Scope/limits/recommendation paragraph. Adding a second paragraph that explicitly flags the Mode 2 → Mode 1 hypothesis status as an open question and proposes two concrete falsification tests, plus a wider-scope replication path. The new paragraph: 1. Acknowledges the Mode 2 → Mode 1 causal reading is a hypothesis, not a theorem, and that the parallel-failure reading is also formally consistent with the data. 2. Proposes a *direct* test: measure per-block forward-state-change content along the training trajectory and check whether per-block loss decrease tracks per-block credit usefulness more tightly than per-block cosine. 3. Proposes a *falsification* test for the downstream-of-Mode-2 reading: substitute the random B_l with a high-quality credit signal (sparse, learned, or weight-transport-restored à la Akrout 2019) at fixed ‖f_l‖ and check whether Mode 1 activation growth still appears. If yes, Mode 1 is NOT downstream of Mode 2. 4. Notes the wider-scope replication path: CIFAR-100, Tiny-ImageNet, architectures outside ResMLP/ViT-Mini, with a pointer to Appendix A as the structured configuration entry point. This explicitly answers the reviewer question "what would falsify your hypothesis?" without overclaiming. It positions the paper as honest about open questions and points at concrete next steps. Page count: 20 (unchanged) — the paragraph fit within the existing slack. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Diffstat (limited to 'paper/figures/render_fig5_cross_arch.py')
0 files changed, 0 insertions, 0 deletions