Configure spack install dir based on env_name
#495
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Configure spack install dir based on
env_name
This helps with saving redundant spack concretization, when experiments
under different workloads are actually using the same software environment.
Some more contexts (courtesy of Bob and Doug):
Historically the spack env was rendered during workspace render time,
that's why the existing namespacing.
That's changed in Convert environment generation logic to lazy / implcit instead of explicit #433.
And it's safe to assume same
env_name
always 1-1 maps to a spackenv. There's a check to guarantee that:
ramble/lib/ramble/ramble/software_environments.py
Lines 371 to 374 in f4e0e06
Tested: tested with the following:
A new created workspace with gromacs ran fine.
(backward-compt) An existing workspace created from the current
develop head ran fine after running
ramble workspace setup
under thecurrent branch.