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

Feature/wam update #14

Conversation

GeorgeGayno-NOAA
Copy link
Owner

  • Use this template to give a detailed message describing the change you want to make to the code.

  • You may delete any sections labeled "optional".

  • If you are unclear on what should be written here, see https://github.com/ufs-community/UFS_UTILS/wiki/9.-Creating-a-Pull-Request for some guidance.

  • The title of this pull request should be a brief summary (ideally less than 100 characters) of the changes included in this PR. Please also include the branch to which this PR is being issued.

  • Use the "Preview" tab to see what your PR will look like when you hit "Create pull request"

--- Delete this line and those above before hitting "Create pull request" ---

DESCRIPTION OF CHANGES:

One or more paragraphs describing the problem, solution, and required changes.

TESTS CONDUCTED:

State whether the contingency tests were run or are pending, and if they were already run, state the result. If contingency test baselines need to be updated as a result of this PR, please specify the machine(s) and path(s) to the new files. Note that running the contigency tests is required for every PR and should be run at least once after all commits or changes have been made after review of the PR. Make note of the compilers used, the platform/machine, and other relevant details as necessary. Please also note whether new unit tests or updates to existing ones were required and their file names.

DEPENDENCIES:

Add any links to pending PRs that are required prior to merging this PR. For example:

ufs-community/UFS_UTILS/pull/<pr_number>

DOCUMENTATION:

If this PR is contributing new capabilities that need to be documented, please also include updates to the RST files in the docs/source directory as supporting material.

ISSUE:

If this PR is resolving or referencing one or more issues, in this repository or elsewhere, list them here. For example, "Fixes issue mentioned in ufs-community#123" or "Related to bug in https://github.com/NOAA-EMC/other_repository/pull/63"

CONTRIBUTORS (optional):

If others have contributed to this work aside from the PR author, list them here

GeorgeGayno-NOAA and others added 9 commits February 21, 2023 10:19
…#774)

Updates to recognize and process Noah-MP restart files. Currently, only the greenness fraction is updated for Noah-MP. Other required fields for Noah-MP will be added later after consultation with the land team. 

All changes are backwards compatible when processing Noah restart files.

Part of ufs-community#761.
The IP and IP2 libraries were combined as IPLIB v4.0.0. Update 
UFS_UTILS to use this version. This update was done so that
it is backwards compatible with IPLIB v3.

Fixes ufs-community#242
…ommunity#777)

New option to build only GFS-specific utilities, triggered
by specifying -DGFS=ON through the build_all.sh script.

Retains the default of building all utilities.

Fixes ufs-community#776
…y#741)

Users choose which orography data to use by setting new 
configuration variable FRAC_ORO. The names of the orography
files and the location of the 'fixed' directory are set by new script
"set_fixed_files.sh".
…unity#773)

Place the copy of the coldstart files in a common script called
copy_coldstart_files.sh.

Fixes ufs-community#772.
@GeorgeGayno-NOAA GeorgeGayno-NOAA merged commit db94b85 into GeorgeGayno-NOAA:feature/wam_update Mar 15, 2023
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.

5 participants