Skip to content
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

Update develop-ref after #2061 #2069

Merged
merged 164 commits into from
Feb 24, 2022
Merged

Update develop-ref after #2061 #2069

merged 164 commits into from
Feb 24, 2022

Conversation

JohnHalleyGotway
Copy link
Collaborator

Expected Differences

PR #2061 for issue #1918 adds a new Gen-Ens-Prod output file which is flagged as a difference. This PR gets past these differences.

ERROR: folder /data/output/met_test_truth missing 1 files
    gen_ens_prod/gen_ens_prod_NORMALIZE.nc

jprestop and others added 30 commits October 26, 2021 13:08
…tead of only the filename so that the function can tell whether or not the file exists. (#1952)

Co-authored-by: Julie Prestopnik <[email protected]>
* Per issue #1761 in set_perc() adding code to get FBIAS numeric value, like 1.0 or 0.9, etc. SL

* Per issue #1761: in set_perc(), modified actual percentile calculation at end to use the extracted FBIAS numeric value (float). SL

* Per issue #1761: modified the check on the perc_thresh_freq_bias, just has to be > 0 now. SL

* Per issue #1761: cleaned up code in set_perc(). SL

* Per #1761, updates to Simple_Node::set_perc() to handle variable frequency bias amounts.
Changes include:
- Reverting the formatting of this back to how it originally was in the develop branch. In general, just match the formatting of the existing file, so as the minimize the number of difference lines.
- Add logic to adjust the percentile to be found based on the requested FBIAS value. Multiplying or dividing the percentile by the FBIAS value depends on the inequality type and whether we're bias adjusting the forecast or observation data.
- Adjust the log messages slightly.

Please be aware that I'm not totally confident in these changes. They warrant much more testing. This logic is very, very confusing.

* Per #1761, call compute_percentile() when double-checking the percentile values.

* Per #1761, remove unused variable.

* Per #1761, add warning for percentiles > 100.

* Per #1761. In set_perc(), after testing cleaned up code. SL

* Per issue #1761: adding new config file for testing dynamic FBIAS values. SL

* Per issue #1761: added new unit test for dynamic FBIAS values when running grid_stat. SL

* Per issue #1761, modified FBIAS section to indicated that the user can use dynamic values that are not 1.0. SL

* Update met/docs/Users_Guide/config_options.rst

Co-authored-by: johnhg <[email protected]>

* Update met/docs/Users_Guide/config_options.rst

Co-authored-by: johnhg <[email protected]>

* Update met/docs/Users_Guide/config_options.rst

Co-authored-by: johnhg <[email protected]>

* Update test/config/GridStatConfig_fbias_perc_thresh

Co-authored-by: johnhg <[email protected]>

* Update test/config/GridStatConfig_fbias_perc_thresh

Co-authored-by: johnhg <[email protected]>

* Update test/config/GridStatConfig_fbias_perc_thresh

Co-authored-by: johnhg <[email protected]>

* Update test/config/GridStatConfig_fbias_perc_thresh

Co-authored-by: johnhg <[email protected]>

* Per issue #1761, set nc_pairs_flag = FALSE. SL

Co-authored-by: Seth Linden <[email protected]>
Co-authored-by: John Halley Gotway <[email protected]>
…ing the logic for computing the ensemble range back to what it was previously. The new version produced very slight differences in the 6-th or 7-th decimal place when compared to previous results. There's not good reason for these changes which were caused by the order of operations in casting from doubles to floats. Reverting back to the old logic prevents diffs for anyone else downstream and is the prudent choice.
* #1949 Added CF compliant NetCDF into data IO

* #1949 Added commas

* #1948 Some corrections for typo and added the links for CF attributes

* #1948 Added Performance with NetCDF input data

* #1949 Corrected tyoe and applied Juloie's suggestions

Co-authored-by: Howard Soh <[email protected]>
…OSS. The intel compiler does not allow adjacent >> characters when defining maps.
hsoh-u and others added 26 commits February 11, 2022 11:44
#2047 Removed the debug message
Removing variable that was set but never used because SonarQube might complain about that, like Fortify does.
Co-authored-by: Julie Prestopnik <[email protected]>
…rection

Feature 2027 grid stat wind direction
…ar entry should really be obs_bufr_map and not commented out.
#1824 ci-run-test Reset itype to 1 for regular CAPE
* found and made three changes replacing [email protected] with the MetPlus gitub discussions page

* Update met/docs/Users_Guide/appendixA.rst

Thanks, a typo plus I am completely neutral as to the exact wording.

Co-authored-by: jprestop <[email protected]>

* Update met/src/libcode/vx_data2d_grib2/data2d_grib2.cc

Co-authored-by: jprestop <[email protected]>

* Update met/README

Co-authored-by: jprestop <[email protected]>

Co-authored-by: jprestop <[email protected]>
* Updated set_job_controls.sh to add a check for the skip all keyword

* Added a space to check keyword ci-skip-all

Co-authored-by: Julie Prestopnik <[email protected]>
@JohnHalleyGotway JohnHalleyGotway added this to the MET 10.1.0 milestone Feb 24, 2022
@JohnHalleyGotway JohnHalleyGotway merged commit 3d7c550 into develop-ref Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants