Controlled Submission Experiment

Use when: (1) a new submission scores worse than baseline and the reason is unclear, (2) multiple changes were made simultaneously (new model + new post-processing + new features), (3) need to isolate which component caused a regression, (4) CV improves but LB degrades, (5) comparing "smart" vs "simple" approaches, (6) verifying that model improvements are real vs artifacts of post-processing changes. CRITICAL: Never change more than one variable between submissions without controlled comparison.

topprismdata Updated 5 repo stars
TopPrism dual-prism visual

File contents

topprismdata/cultivating-ml-agent commit 18d7b734f5

Frequently asked questions

npx get-skill add topprismdata/controlled-submission-experiment