Extend docs to specify checklist of what's needed for experiment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 78
- Forks
- 52
- Avg merge
- 4d 19m
- Merged PRs (30d)
- 10
Description
How can each item be tested in GitHub CI, and at which stage:
- [ ] benchpark audit
- [ ] ramble dryrun
- [ ] ramble setup
- [ ] ramble on - a test will run a problem on a single x86 node
**Mandatory**:
- [ ] single node #492
- [ ] CPU-only problem - an x86 test? The allocation modifier makes sure there is an experiment with 0 GPUs required?
- [ ] 1 prog model (i.e., derived from ??) - can benchpark audit be used for this?
- [x] add a ``dryrun``
- [ ] exit code from main - can only be tested when the test is running (ramble on) - how does GitLab CI test this?
**Optional**:
- [ ] caliper/adiak integration (i.e., derived from CaliperExperiment?) - can benchpark audit be used for this?
- [ ] GPU prog models (i.e., derived from CudaExperiment, RocmExperiment?) - can benchpark audit be used for this?
- [ ] FOM+problem size
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.