Change diagnostic counter zero warning from warning level 1 to 2 #148
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
This warning is not necessarily concerning but the default settings in HEMCO_Config.rc make the prints appear every emissions timestep . Changing the warning level to 2 suppresses the warnings unless the user manually increases the warning level to 2 or higher in HEMCO_Config.rc, which is the recommendation for debugging. Signed-off-by: Lizzie Lundgren <elundgren@seas.harvard.edu>
msulprizio
approved these changes
Jun 14, 2022
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 increases the HEMCO warning level for zero diagnostic counters from 1 to 2 so that the warnings are not printed by default (default warning level is 1 in all GEOS-Chem run directories). These warnings occur when HEMCO diagnostics are created but never populated, something that is common given the way we configure HEMCO diagnostics from config files. The prints happen every timestep and therefore clutter the log. Users can still find out if HEMCO diagnostics are created but not populated by increasing the warning level, something we recommend when debugging.