diff --git a/docs/claude/planning-discussion-2026-11-19.md b/docs/claude/planning-discussion-2026-11-19.md new file mode 100644 index 000000000..791af943f --- /dev/null +++ b/docs/claude/planning-discussion-2026-11-19.md @@ -0,0 +1,22 @@ +# Planning discussion (Claude hosts, 2026-11-19; requested by Yanqi) + +This discussion changes no current experiment authorisation. Running: 1b fold 0 (GPU0). In preparation: Track B GINO reproduction (environment acceptance first). + +Where we stand (details in `research-tree.md` and `stage-review-2026-11-19.md`): +- H2 (learned mesh representation) is our best model: field 7.08 → 6.58 % vs A on the grouped Greif protocol, confirmed; last-fill location worse; seed spread small for field, large for last fill. +- Tabular additions (B-series), last-fill losses (B17, c) and B13 context inside H2 (b) all failed to add anything. +- Greif paper comparison is not legitimate yet (our A gives 3.99 % on random splits vs the paper's 3.31-3.38 %). +- The data-sufficiency test was not identified (overfitting signs on the longer schedule; 1b tests that). +- Constraints: Moldflow student licence only (no batch generation right); Horsea 4 × V100 (GPU3 single task); fresh holdout blocked. + +## Questions (answer independently, before reading anyone else's; at most one page) + +1. **Short term (weeks): how do we make the current approach solid?** What is missing before H2 can be called a reliable result (seeds, folds, holdout, last fill, protocol)? +2. **Medium term: which single comparison is most worth running?** (e.g. GINO ShapeNet reproduction then H2 on it, Ahmed, Gre24 protocol reproduction, a stronger published mesh baseline on Greif, pretraining arm.) +3. **Long term: how do we return to cross-geometry injection-molding prediction?** Data (new parts, generation, licence), model, evaluation on genuinely new part families. + +For each answer state: **key dependencies, cost (GPU-h, people time, licences), and what evidence would change your mind.** + +## Who + +MeltSol (executor + literature), MeltAssist (reviewer), MoldAstra (maths), NewMeltAstra (fresh view; has implemented nothing), TRON (coordination only, optional). Answers go to Git via MeltSol, links in Slack. Claude writes its own answer only after collecting the others (to avoid anchoring), then hosts one discussion round and rules.