PARSL_MPI_PREFIX moved to the espresso calculator #2422
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.
Summary of Changes
As discussed in (#2419) this is an attempt to fix the current issue with the
Expected behavior
Users can redecorate their job, adding the
parsl_resource_specification
, Parsl take these informations and define environment variables such asPARSL_MPI_PREFIX
. If the users redecorate multiple jobs, differentPARSL_MPI_PREFIX
will be accessible on a per job basis.Example:
In this case, each job will have access to a different
PARSL_MPI_PREFIX
environment variable.The problem
Right now, the
ESPRESSO_PARALLEL_CMD
is modified insettings.py
based on thePARSL_MPI_PREFIX
, the problem is that this env variable is only defined within jobs.ESPRESSO_PARALLEL_CMD
end up being defined before that, leading to wrong commands.The problem
One solution is to modify the command being lunched at the last moment inside the espresso calculator before the command is lunched.
Requirements
main
).Note: If you are an external contributor, you will see a comment from @buildbot-princeton. This is solely for the maintainers.