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

Modifiers to capture runtime parameters #532

Open
pearce8 opened this issue Jan 7, 2025 · 0 comments
Open

Modifiers to capture runtime parameters #532

pearce8 opened this issue Jan 7, 2025 · 0 comments
Assignees
Labels
feature New feature or request

Comments

@pearce8
Copy link
Collaborator

pearce8 commented Jan 7, 2025

We should write 2 modifiers:

  1. Export_modifier: writes export at the beginning of the run to grab the environment variables and save the output.
  2. Execution_inventory_modifier: at runtime records ramble variables. We should look at what Ramble hashes and determine what of that data is useful to us.

Notes from 25/1/7: Ramble hashes ramble.yaml and the tpl (template) files. Ramble hash docs:

https://ramble.readthedocs.io/en/latest/workspace.html#workspace-inventory-and-hash

  • Workspace hashes contain experiments
  • Look at the hash digest
  • Chained experiments
  • Spack log is in here as well? This throws a wrench into being able to look at the runtime parameter differences if the builds are different.

Variables: look at ramble.yaml, it could come from outside of the workspace as well.
All other sections are config sections and could be impacted from outside of the workspace as well.

@pearce8 pearce8 added the feature New feature or request label Jan 7, 2025
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

2 participants