-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature 1921 warnings #1935
Feature 1921 warnings #1935
Conversation
… entries to debug(4) since they were producing excessive, un-useful warning messages.
…fo for each term to DEBUG(3) and printing a warning if there were issues for any of the terms.
…nfiguration option to suppress copious warning messages that we being printed.
…It had been analyzing both 3 and 6-hour accumulated precip in the same run, which is not a very sensible thing to do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed the code changes and inspected the regression test output, confirming that the only diffs are the expected changes to Grid-Diag. I approve this request.
Waiting for the rerun of the commands to regenerate the warning list before approving.
@jprestop please proceed with this PR review. The total number of non-empty warning lines produced by the unit test commands have been reduced from 1127 to 227. In addition, the changes for "ipdtmpl" warnings lower that number even further.
Please see this issue comment for the details. |
Wow! Those are significant changes! I will approve this PR again now. |
Co-authored-by: Seth Linden <[email protected]> Co-authored-by: John Halley Gotway <[email protected]> Co-authored-by: Howard Soh <[email protected]> Co-authored-by: johnhg <[email protected]> Co-authored-by: Julie.Prestopnik <[email protected]> Co-authored-by: ericgilleland <[email protected]> Co-authored-by: George McCabe <[email protected]> Co-authored-by: John Halley Gotway <[email protected]> Co-authored-by: jprestop <[email protected]> Co-authored-by: Julie Prestopnik <[email protected]> Co-authored-by: hsoh-u <[email protected]> Co-authored-by: Keith Searight <[email protected]> Co-authored-by: Seth Linden <[email protected]> Co-authored-by: MET Tools Test Account <[email protected]> Co-authored-by: lisagoodrich <[email protected]> Co-authored-by: MET Tools Test Account <[email protected]> Co-authored-by: j-opatz <[email protected]>
Pull Request Testing
Describe testing already performed for these changes:
Lots of small changes here in an attempt to reduce the number of warnings MET prints out. While the largest categories of warnings have been investigated, not all of them have been. Since this is a relatively low priority task, recommend that we proceed with the current set of changes instead of waiting for every single one to be investigated.
Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
Review code changes. Inspect regression test output to confirm that the only diffs are the expected change to Grid-Diag:
/d1/projects/MET/MET_pull_requests/met-10.1.0/met-10.1.0_beta3/feature_1921/test_regression.log
(see below)
None needed.
No additional testing required to reduce warning messages. Did modify a Grid-Diag unit test to improve it rather than running it on a mixed set of APCP accumulation intervals.
If yes, describe the new output and/or changes to the existing output:
Changes the output of the Grid-Diag unit test, switching from running on a mixed set of APCP accumulation intervals to RH instead:
test_output/grid_diag/grid_diag_out.nc
Pull Request Checklist
See the METplus Workflow for details.
Select: Reviewer(s)
Select: Organization level software support Project or Repository level development cycle Project
Select: Milestone as the version that will include these changes