Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend docs to specify checklist of what's needed for experiment #424

Open
12 tasks
slabasan opened this issue Nov 6, 2024 · 0 comments
Open
12 tasks

Extend docs to specify checklist of what's needed for experiment #424

slabasan opened this issue Nov 6, 2024 · 0 comments
Assignees
Labels
docs Improvements or additions to documentation feature New feature or request help wanted Extra attention is needed

Comments

@slabasan
Copy link
Collaborator

slabasan commented Nov 6, 2024

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 Single node experiment #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?
  • 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
@slabasan slabasan added the docs Improvements or additions to documentation label Nov 6, 2024
@pearce8 pearce8 added the feature New feature or request label Dec 16, 2024
@pearce8 pearce8 added the help wanted Extra attention is needed label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation feature New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants