Add environment variables to set verbosity levels on initialization #2425
Conversation
This file contains 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
…s to set default verbosity level at initialization
…e stdout from all meep workers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR closes #2421 by adding the following environment variables that meep checks for upon initialization:
MEEP_VERBOSITY_LEVEL: Verbosity level ofverbosity.meep(default = 1).MPB_VERBOSITY_LEVEL: Verbosity level ofverbosity.mpb(default = 1).MEEP_MPI_SILENCE_WORKERS: Whether non-masterstdoutshould be overridden or not (default = true).The defaults are set so that current behavior does not change.
The variable
MEEP_MPI_SILENCE_WORKERSwas not discussed in #2421 but I have found it very helpful while debugging in the past and thought it might go well with this PR.