Modifiers to capture the environment and runtime parameters
@joshuamvining is already working on this.
Since May 29, 2026.
- Dominant language
- Python
- Stars
- 78
- Forks
- 52
- Avg merge
- 4d 19m
- Merged PRs (30d)
- 10
Description
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. @nhanford will that capture all we need from the environment?
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.
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.