-
Notifications
You must be signed in to change notification settings - Fork 26
Feature #2794 and #2818 WRF subgrid #3122
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
Conversation
…issions_dimension_stag, klevs_for_dvel, soil_layers_stag, seed_dim_stag. Clean up
…erver to link with automation
…to feature_2794_wrf_subgrid
…that is not on the subgrid can be read properly
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 read looked through the proposed code changes and have only very minor feedback.
I see that this PR reduces the overall number of code smells from 17,379 in develop to
17,371 in this feature branch, which is good.
I see that the only differences are the addition of 2 new PostScript files for the 2 new plot_data_plane unit tests. I inspected the plots and was at first confused, but now understand, that the regular grid and subgrid cover the same lat/lon extent, but the subgrid data has higher resolution. The plots look reasonable to me.
For traceability and clarity, I'd recommend the following:
- Complete your work for the #3121 pull request.
- Merge #3121 into develop.
- Merge develop into this feature_2794_wrf_subgrid feature branch.
- Re-request my review of this PR.
That should prevent the #3121 changes from being included in this PR and should prevent any merge conflicts from popping up.
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 approve of these changes.
Looks great George! Thanks for further reducing the SonarQube code smells down to 17,352 and for getting rid of the contributor's guide false alarm code changes.
I re-confirmed that the only diffs are the addition of 2 new expected plot_data_plane output files.
Additional changes included in this PR relating to unit testing is included in PR #3121
Expected Differences
If yes, please describe:
Just new env var
MET_USE_WRF_SUBGRID
to control reading subgrid from WRF filesIf yes, please describe:
Pull Request Testing
Added new unit tests.
Updated existing METplus use case to read WRF Fire data directly instead of using Python Embedding and confirmed that it worked as expected, producing the same statistics.
Review code changes
Added info about new env var
Do these changes include sufficient testing updates? [Yes]
Will this PR result in changes to the MET test suite? [Yes]
If yes, describe the new output and/or changes to the existing output:
Will this PR result in changes to existing METplus Use Cases? [No]
If yes, create a new Update Truth METplus issue to describe them.
Do these changes introduce new SonarQube findings? [No]
If yes, please describe:
Please complete this pull request review by 4/8/2025.
Pull Request Checklist
See the METplus Workflow for details.
Select: Reviewer(s) and Development issue
Select: Milestone as the version that will include these changes
Select: METplus-X.Y Support project for bugfix releases or MET-X.Y Development project for the next coordinated release