You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per Elena (ml-research-methodologist) + Reviewer 2 consensus:
- Replace L (hotpotqa, fixed-300) with L (hotpotqa, rotation-300 via static_r)
- All 3 treatment runs (L/M/N) now use problem=static_r + prompts=hotpotqa
- Control (K) stays on static + default prompts (mirrors Run E)
- Two variables change K→L/M/N (prompts + val set); pre-registered compound treatment
- Fixes the n=1 uninterpretable condition issue flagged by both advisors
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
-Standard pipeline (NOT hotpotqa_asi) -- we do NOT include P2 (ASI) in the base treatment
86
-
-Fixed 300-sample validation (NOT P1 rotation) -- we do NOT include P1 either
87
-
- Rationale: P1 and P2 showed null-to-negative effects. Adding them would confound the prompt intervention. If NLP prompts show a positive signal, we can test P1+P2 combination in a follow-up.
85
+
-Rotation val set (`problem.name=chains/hotpotqa/static_r`) — each program evaluated on a different hash-seeded 300/1000 subset
86
+
-Standard pipeline (NOT hotpotqa_asi) -- we do NOT include P2 (ASI)
87
+
- Rationale: P2 (ASI) showed null-to-negative effect alone (Run F: 53.7%). Rotation is included to reduce selection noise from the fixed-300 val set's ~5-10pp val-test gap.
88
88
89
-
The control run uses the exact same config as Run E (standard pipeline, fixed 300 validation, default prompts).
89
+
The control run uses the exact same config as Run E (standard pipeline, fixed 300 validation (`static`), default prompts).
90
90
91
-
### 4.3 Val Set Decision: Fixed 300
91
+
### 4.3 Val Set Decision: Rotation for Treatment, Fixed for Control
92
92
93
-
**Rationale**: P1 (rotation) showed null effect on test EM and a *worse* val-test gap than Run E in some conditions. Fixed-300 matches the control condition (Run E), enabling clean comparison. The 5.7pp val-test gap in Run E is a known property of this setup; it does not prevent detecting mutation quality improvements (a better mutation engine should improve both val and test EM).
93
+
**Treatment (L/M/N)**: Use `static_r` (rotation, 300/1000 samples, hash-seeded per chain spec). Rationale: the 5.7-9.7pp val-test gap in P1xP2 was partially caused by stable val-set overfitting. Rotation ensures val scores are unbiased estimators of generalisation; programs that truly improve will show consistent gains across different subsets.
94
+
95
+
**Control (K)**: Uses `static` (fixed first-300 samples), matching Run E exactly. This preserves the historical comparison.
96
+
97
+
**Tradeoff**: Two variables change between K and L/M/N (prompts + val set). This is a deliberate compound treatment: the research question is "does the NLP-prompts-with-rotation package improve test EM?" rather than isolating each variable. The pre-registered contrast is K vs. L/M/N mean.
94
98
95
99
## 5. Design Table
96
100
97
-
| Run | Label | Prompts | Pipeline | Problem Dir | DB | Mutation Server | Chain Server | Seed |
0 commit comments