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

Parameterizing the compiler to use for an experiment #238

Open
pearce8 opened this issue May 8, 2024 · 0 comments
Open

Parameterizing the compiler to use for an experiment #238

pearce8 opened this issue May 8, 2024 · 0 comments
Assignees
Labels
feature New feature or request
Milestone

Comments

@pearce8
Copy link
Collaborator

pearce8 commented May 8, 2024

Update: @rfhaque Please verify that this works with the new experiment.py and system.py definitions.

Application.py can give suggestions on where an experiment might be run, but not requirements. However, application.py could define a workload variable that can then be used in experiment variables.

Example of using a variable in the experiment to impact the build requirements:

https://github.com/LLNL/benchpark/tree/develop/experiments/amg2023/cuda/ramble.yaml

applications:
    amg2023:
      workloads:
        problem1:
          variables:
             cuda_arch: '{cuda_arch}'
spack:
    concretized: true
    packages:
      amg2023:
        spack_spec: amg2023@develop +mpi+cuda{modifier_spack_variant} cuda_arch=={cuda_arch} 
        compiler: default-compiler

How should we connect this to what is available on the system?

Note: environments are lazily rendered in Ramble, that is they are only rendered when the experiment phases are started.

@pearce8 pearce8 added the feature New feature or request label May 8, 2024
@pearce8 pearce8 added this to the v0.1.1 milestone May 8, 2024
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

No branches or pull requests

3 participants