Files
Atomizer/projects/hydrotech-beam/playbooks/DOE.md
Anto01 ed6874092f chore: clean hydrotech-beam syncthing conflicts and add new docs
- Remove all .sync-conflict-* files
- Remove temp _temp_part_properties.json files
- Add USER_GUIDE.md
- Add dashboard docs (Executive, Technical, Operations, Master Plan)
- Add playbooks (DOE, NX_REAL_RUN, SYNCTHING_RECOVERY)
- Update iteration results

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-16 12:11:16 -05:00

40 lines
1.2 KiB
Markdown

# Playbook — DOE (Phase 1 Landscape)
## Scope
Design of Experiments for Hydrotech Beam: baseline + LHS samples to map design space.
## Standard flow
1. Prepare clean state (archive previous results if needed)
2. Run DOE with explicit backend
3. Validate outputs
4. Evaluate gate criteria
5. Decide next phase (rerun bounds/constraints or move to TPE)
## Commands
### Real engineering DOE
```powershell
python .\run_doe.py --backend nxopen --model-dir "<PATH_TO_NX_MODELS>" --clean --study-name hydrotech_beam_doe_phase1_real
```
### Debug DOE only (synthetic)
```powershell
python .\run_doe.py --backend stub --clean --study-name hydrotech_beam_doe_phase1_stub
```
## Interpretation checklist
- `geo_infeasible` high: geometry bounds/checks may be too broad or too strict
- `fully_feasible = 0`: constraints may be too strict for current design space
- Very low runtime and suspiciously smooth outputs: likely stub execution
## Decision branch
- If gate passed: proceed to TPE seeded by feasible points
- If gate failed:
- adjust constraints and/or DV bounds
- rerun clean DOE
## Documentation requirement
After each DOE run, update:
- run record
- decision and rationale
- next action owner