Remove legacy virtual environment overrides #141
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
By default, OpenMP applications use all CPU cores unless one exports environment variable
OMP_NUM_THREADS=1, but doing so changes the behavior of Linux commandnprocto return that variable value instead of the actual number of CPU cores. This can be confusing to users who aren't familiar with OpenMP parallelization. Most clusters will build ESPResSo 5.0 with OpenMP enabled for performance reasons. The latest version of ESPResSo automatically sets the number of OpenMP threads to 1 a few milliseconds afterimport espressomdis executed, if that environment variable wasn't set by the user. We therefore no longer have to alter environment variables in the user's Python environment.