-
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 #2924 fcst climo, PR 2 of 3 #2942
Conversation
…uplicate existing climo values, update the header tables and MPR/ORANK documentation tables.
…R and ORANK climatology columns.
…climo data... but more work to come. Committing this first set of changes that are incomplete but do compile.
…s a segfault for ensemble-stat
…lumn names are requested, the new ones are used.
…names rather than the old ones.
…ut column. This compiles but not sure if it actually runs yet
…as SOCP and OCDP, resp
…ClimoGrid::init_from_scratch() member function. The constructor had been calling clear() to delete pointers that weren't properly initialized to nullptr. Also, simplify some map processing logic.
…nd to avoid conflicts in member function implementations.
… NetCDF output option.
…ThreshType value
@j-opatz please find this code compiled on seneca for further testing in For future reference, here are the commands I used to compile there:
|
…ed for the corresponding METplus Use Case. Note that there are 22 other TRI values not currently supported.
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.
With data provided by EMC, this PR was tested with both a forecast and observation climatology. Observing both the netCDF output and CNT line type values, it appears that each field (forecast and observation) are correctly having their independent climatology applied. Values are reasonable and reflect what is expected given the dataset.
The column changes were already checked and confirmed for accuracy.
Although the SonarQube check is currently failing, I believe that is expected(?) and this PR is approved.
Expected Differences
MET #2924 is a large development task that has been split into 2 pull requests. PR #2939 contained this first set of changes and this PR contains the second set of changes.
This second pull request includes changes to 25 files, outlined below:
[2] Header data files (
met_header_columns_V12.0.txt
andmet_12.0.hdr
) renames existing and adds new columns to the MPR and ORANK line types.[3]
stat_column_defs.h
,stat_columns.cc
, andpair_data_point.cc
add/modify MPR/ORANK column names.[2]
gsi_tools
are updated to handle the MPR and ORANK line type changes.[3]
docs/Users_Guide
files update the documentation and make more consistent use of the.. note::
option (unrelated to this issue).config_options.rst
adds the example config setting, as requested.[7] Unit test files.
unit_climatology_mixed.xml
defines 1 new calls to Grid-Stat with mixed fcst/obs climo data. Column names updated inunit_climatology_1.5deg.xml
. 1 new and 2 updated config files ininternal/test_unit/config
.unit_test.sh
andtesting.yml
now call the new xml file.[1] Minor changes to comments in
threshold.cc
[7]
read_climo.h/.cc
are updated to print more descriptive log messages about the data being read, andensemble_stat.cc
,grid_stat.cc
,point_stat.cc
,series_analysis.cc
, andgen_ens_prod.cc
are updated to pass those description strings.Do these changes introduce new tools, command line arguments, or configuration file options? [No]
If yes, please describe:
Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [Yes]
If yes, please describe:
CLIMO_MEAN
,CLIMO_STDEV
, andCLIMO_CDF
asOBS_CLIMO_MEAN
,OBS_CLIMO_STDEV
, andOBS_CLIMO_CDF
, respectively.FCST_CLIMO_MEAN
andFCST_CLIMO_STDEV
.CLIMO_MEAN
,CLIMO_STDEV
asOBS_CLIMO_MEAN
,OBS_CLIMO_STDEV
, respectively.FCST_CLIMO_MEAN
andFCST_CLIMO_STDEV
.Pull Request Testing
Describe testing already performed for these changes:
Tested by adding new unit test. After GHA testing workflow is done, I'll add a description of the diffs ehre.
Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
Review code changes and documentation updates. Recommend testing with data provided by NOAA.
Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]
Please review the updates docs for this PR: https://met--2942.org.readthedocs.build/en/2942/
Do these changes include sufficient testing updates? [Yes]
Adds 1 new unit test in a new
unit_climatology_mixed.xml
file.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:
All the MPR and ORANK output is modified.
Expect updated NetCDF variable names in the Grid-Stat matched pairs files.
Adds new output for new unit test.
Will this PR result in changes to existing METplus Use Cases? [Yes]
If yes, create a new Update Truth METplus issue to describe them.
Changes to the MPR and ORANK line types.
See Update Truth: For dtcenter/MET#2942 METplus#2656
Do these changes introduce new SonarQube findings? [Yes]
If yes, please describe:
In this SonarQube scan flags 1 code smell about a function with > 7 args. This is an existing smell and we actually have many instances of it. We have not decided to tackle this one yet.
It also flags 10% duplication, and we've also decided not to attack this yet either.
Please complete this pull request review by [Monday 8/5/24].
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: Coordinated METplus-X.Y Support project for bugfix releases or MET-X.Y.Z Development project for official releases