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

Single node experiment #492

Open
pearce8 opened this issue Dec 10, 2024 · 1 comment · May be fixed by #500
Open

Single node experiment #492

pearce8 opened this issue Dec 10, 2024 · 1 comment · May be fixed by #500
Assignees
Labels
feature New feature or request

Comments

@pearce8
Copy link
Collaborator

pearce8 commented Dec 10, 2024

  • enforce that a single node experiment is implemented
  • sub-select and run a single node experiment
  • enforce (in the allocation modifier?) that the experiment doesn't request more experiments
@scheibelp scheibelp self-assigned this Dec 11, 2024
@scheibelp
Copy link
Collaborator

scheibelp commented Dec 11, 2024

sub-select and run a single node experiment

ramble -D $WRKSPC on --where '{n_nodes} == 1' --executor='{execute_experiment}'

(with --executor='{execute_experiment}', we don't need to use different templates: the sbatch directives will be ignored)

enforce that a single node experiment is implemented

we could modify the prior statement to make sure there is at least one experiment that runs on a single node:

ramble --workspace-dir workspace/kripke/rocm/tioga-system/workspace/ on --where '{n_nodes} == 1' --executor="echo matchx" | grep "matchx" | wc -l

(Update Dec. 17) You can test this for example by running

./bin/benchpark system init --dest=tioga-system llnl-elcapitan rocm=5.4.3 compiler=cce ~gtl
./bin/benchpark setup kripke/rocm ./tioga-system workspace/

(notably, you do not have to execute ramble workspace setup prior to checking the number of single-node experiments)

enforce (in the allocation modifier?) that the experiment doesn't request more experiments

I assume this should be "...doesn't request more resources": ramble on --where=... will enforce this to some degree. We allow per-experiment custom templates, and I think even without that, experiments could attempt to do their own allocations (the allocation modifier would not be able to detect either of these scenarios). In terms of requests made at the level of ramble.yaml, ramble on --where=... would be enough to control that.

@pearce8 pearce8 added the feature New feature or request label Dec 17, 2024
@pearce8 pearce8 linked a pull request Dec 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants