一键导入
doe-suite
Run remote experiments and process results using doe-suite. Use for launching experiments on AWS/Euler or aggregating results across multiple suite runs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Run remote experiments and process results using doe-suite. Use for launching experiments on AWS/Euler or aggregating results across multiple suite runs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | doe-suite |
| description | Run remote experiments and process results using doe-suite. Use for launching experiments on AWS/Euler or aggregating results across multiple suite runs. |
This skill provides two main workflows for the DoE-Suite framework:
Working Directory: All commands run from doe-suite/
cd doe-suite && source .envrc
# Running experiments
make run suite=<suite-name> id=new
# Processing results across suites
make etl-super config=<config-name> out=<output-dir> pipelines="<pipeline1>,<pipeline2>"
Launch and monitor remote experiments on AWS EC2, ETHZ Euler, or existing machines.
Key tasks:
→ Complete experiment workflow
Aggregate and visualize results from multiple suite runs.
Key tasks:
DoE-Suite manages remote experiments following Design of Experiments methodology:
doe-suite-config/designs/)Required .envrc variables:
DOES_PROJECT_DIR, DOES_PROJECT_ID_SUFFIX, DOES_SSH_KEY_NAMEDOES_CLOUD=aws, AWS_PROFILE, AWS_REGIONSSH key must exist in target AWS region.
# List available suites
ls doe-suite-config/designs/*.yml
# Validate suite design
make design-validate suite=<suite-name>
# Launch new experiment
make run suite=<suite-name> id=new
# Monitor (keeps checking until done)
make run suite=<suite-name> id=last
# Process results across suites
make etl-super config=poly_plots out=../doe-suite-results-super pipelines="overview,grid_kzg"
# Cleanup
make clean
doe-suite/docs/ - Framework documentation⚠️ Cost Warning: AWS EC2 charges per hour. Set billing alerts and verify cleanup.
💡 Parallel Execution: Run multiple suites in parallel using different agents/sub-processes.
🐛 Debugging: Use make run-keep to keep instances alive for debugging.
📊 Monitoring: make run handles monitoring properly (don't use bash sleep loops).
🔄 Retrying: Fix code, commit, push, then re-run with id=new or continue with id=last.