News

2024-10-11

The UFS WM incorporated the GFDL Land Model 4.0 (LM4) component via PR #2146.

2024-10-01

PR #2224 added initial build and run support for the Intel LLVM-based Fortran compiler (ifx), along with a small set of LLVM compiler regression tests on RDHPCS. Eventually, the UFS will transition fully to the LLVM compiler suite as the default (instead of the Intel Fortran Compiler Classic [ifort]).

2024-09-17

The UFS WM incorporated the Community Fire Behavior Model with FV3ATM coupling via PR #2220.

2024-08-16

The Derecho allocation for NRAL accounts has run out (see dashboard for allocation details). As a result, testing on Derecho will be slowed down until the end of September when allocations are reset for FY 2025.

2024-07-24

Several recent PRs have made upgrades for HR4, including PRs #2290, #2340, and #2354. These PRs contain land surface upgrades to address surface cold biases, improvements to convection/radiation interaction in the GFS physics suite, and Gravity Wave Drag (GWD) updates for FV3.

2024-06-11

Added active atmosphere applications with data OCN and data ICE components (ATM_DS2S and ATM_DS2S-PCICE) and corresponding regression tests (atm_ds2s_docn_dice and atm_ds2s_docn_pcice) (#2186).

2024-06-05

The UFS WM has been updated to use spack-stack-1.6.0 on UFS Tier-1 platforms. This is an upgrade from spack-stack-1.5.0.

2023-10-30

Spack Stack version is updated on UFS Tier-1 platforms from spack-stack-1.4.1 to spack-stack-1.5.0. Update GOCART submodule pointer points to hash f7b34e.

2021-11-10

The following intermediate ESMF libraries are planned to be removed on the UFS Tier-1 platforms.

8_1_0_beta_snapshot_27        8_1_0_beta_snapshot_36        8_1_0_beta_snapshot_47        
8_1_0_beta_snapshot_27-debug  8_1_0_beta_snapshot_36-debug  8_1_0_beta_snapshot_47-debug  

For developers who are using those ESMF versions, please merge your branches to use a later version of ESMF library that are available. Currently the develop ufs-weather-model branch is using the ESMF public release 8_2_0. Please create an issue in the ufs-weather-model repository if you have any concerns/questions.

2021-06-10

UFS-weather-model code commit tutorial was given by Dom and Laurie on June 9/10. The recordings of the tutorial are available at:

https://github.com/ufs-community/ufs-weather-model/wiki/UFS-weather-model-code-commit-tutorial-recordings

2021-05-26

Recently two changes on NEMS driver cleanup (PR#533) and the fv3-jedi coupling (#586) were committed to the ufs-weather-model develop branch. Due to these changes, an updated NUOPC field dictionary file "fd_nems.yaml" is now required for all the ufs-weather-model application runs. This file is currently located in ufs-weather-model/tests/parm/fd_nems.yaml in the  ufs-weather-model repository. Please copy this file to your run directory when you update model code with the latest ufs-weather-model develop branch.

Another minor change is that the configuration variable "cpl" in model_configure file was removed in PR#586, having it in model_configure does not impact the model run, but we recommend removing it from the model_configure when you sync code with the latest develop branch.

2021-05-14

PR#534 was merged to the ufs-weather-model repository to speed up compiling the model executable. The FMS submodule has been moved out of the ufs-weather-model repository, it is built as a library and used as a prebuilt library in ufs-weather-model build system. This code update significantly reduced the compile time in many UFS applications.

Developers are encouraged to merge their branches to the top develop branch to take advantage of this new feature. Currently the FMS library is available on the tier-1 UFS supported platforms. Developers using these systems should be able to build the model after the merge without additional code changes. Developers using other platforms will need to build the FMS library before building the model executable.

2020-07-17

To report a bug or start a new feature, please click on new issue and two issue templates will show up. Please follow the relevant tabs to fill up the details.

• Template for pull request is available. Please fill in information when creating pull request.