Skip to content

Commit

Permalink
Develop meso fix new ksmax -- added testing for UGWPv1 (#1923)
Browse files Browse the repository at this point in the history
* Updated fv3atm and ccpp-physics submodules as part of fixing ccpp UGWP OGWD stability issues in the upper atmosphere

* Change RF damping parameters and n_split for HR3

* Corrected new 'ugwpv1' SDF's in fv3atm

* Added UGWPv1 tests: control_p8_ugwpv1 and cpld_control_gfsv17_ugwpv1

* Changed n_split from 4 to 5 in tests/parm/cpld_control.nml.IN and cpld_control_ugwpv1.nml.IN
  • Loading branch information
mdtoyNOAA authored Oct 24, 2023
1 parent 001f6f1 commit 3182954
Show file tree
Hide file tree
Showing 23 changed files with 7,695 additions and 5,847 deletions.
5 changes: 4 additions & 1 deletion .readthedocs.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,10 @@

# Required
version: 2
build:
os: ubuntu-20.04
tools:
python: "3.9"

# Build documentation in the docs/ directory with Sphinx
sphinx:
Expand All @@ -18,6 +22,5 @@ formats: all

# Optionally set the version of Python and requirements required to build your docs
python:
version: 3.7
install:
- requirements: doc/UsersGuide/requirements.txt
2 changes: 1 addition & 1 deletion FV3
4 changes: 2 additions & 2 deletions doc/UsersGuide/source/AutomatedTesting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -31,14 +31,14 @@ The CI/CD workflow then executes the following steps:
subcomponents are up to date with the top of the ``develop`` branch.

#. If the check is successful, build jobs are started on GHA-provided virtual machines
by downloading the hpc-stack Docker container stored in Docker Hub.
by downloading the HPC-Stack Docker container stored in Docker Hub.

#. Once all build jobs are successful, the created executable files are stored as
artifacts in GHA.

#. A number of AWS EC2 instances are started.

#. Test jobs are started on AWS after downloading the hpc-stack Docker container,
#. Test jobs are started on AWS after downloading the HPC-Stack Docker container,
the executable file from the build job, and the input-data Docker container.

#. When all tests are complete, EC2 instances are stopped. Test results are reported
Expand Down
19 changes: 10 additions & 9 deletions doc/UsersGuide/source/BuildingAndRunning.rst
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,15 @@ through NOAA and its affiliates. These systems are named (e.g., Hera, Orion, Che
Level 3 & 4 systems include certain personal computers or non-NOAA-affiliated HPC systems.
The prerequisite software libraries for building the WM already exist in a centralized location on Level 1/preconfigured
systems, so users may skip directly to :ref:`getting the data <GetData>` and downloading the code.
On other systems, users will need to build the prerequisite libraries using :term:`HPC-Stack` or :term:`spack-stack`.
On other systems, users will need to build the prerequisite libraries using :term:`spack-stack` or :term:`HPC-Stack`.

=======================
Prerequisite Libraries
=======================

The UFS WM requires a number of libraries.
The WM uses two categories of libraries, which are available as a bundle via
:term:`HPC-Stack` or :term:`spack-stack`:
:term:`spack-stack` or :term:`HPC-Stack`:

#. :term:`NCEP` libraries (:term:`NCEPLIBS`): These are libraries developed for use with NOAA weather models.
Most have an NCEPLIBS prefix in the repository (e.g., NCEPLIBS-bacio). Select tools from the UFS
Expand All @@ -34,11 +34,12 @@ The WM uses two categories of libraries, which are available as a bundle via
instead.

.. note::
Currently, HPC-Stack is the software stack validated by the UFS WM for running :term:`regression tests <RT>`.
However, UFS applications are shifting to spack-stack, which is a Spack-based
method for installing UFS prerequisite software libraries. The spack-stack is currently
used on NOAA Cloud platforms and in containers, while HPC-Stack is still used on NOAA
Research & Development HPC Systems (RDHPCS).
Currently, spack-stack is the software stack validated by the UFS WM for running
:term:`regression tests <RT>`. Spack-stack is a Spack-based method for installing UFS
prerequisite software libraries. UFS applications and components are also shifting to
spack-stack from HPC-Stack but are at various stages of this transition.
Although users can still build and use HPC-Stack, the UFS WM no longer uses HPC-Stack
for validation, and support for this option is being deprecated.

----------------
Common Modules
Expand Down Expand Up @@ -70,8 +71,8 @@ The most updated list of common modules can be viewed in ``ufs_common.lua``
`here <https://github.com/ufs-community/ufs-weather-model/blob/develop/modulefiles/ufs_common.lua>`__.

.. attention::
Documentation is available for installing `HPC-Stack <https://hpc-stack.readthedocs.io/en/latest/>`__
and `spack-stack <https://spack-stack.readthedocs.io/en/latest/>`__, respectively.
Documentation is available for installing `spack-stack <https://spack-stack.readthedocs.io/en/latest/>`__
and `HPC-Stack <https://hpc-stack.readthedocs.io/en/latest/>`__, respectively.
One of these software stacks (or the libraries they contain) must be installed before running the UFS Weather Model.

.. _GetData:
Expand Down
4 changes: 2 additions & 2 deletions doc/UsersGuide/source/CodeOverview.rst
Original file line number Diff line number Diff line change
Expand Up @@ -19,16 +19,16 @@ Four levels of support have been defined for :term:`UFS` applications, and the U

Level 1 Systems
==================
Preconfigured (Level 1) systems for the UFS WM already have the required external libraries available in a central location via :term:`HPC-Stack` or :term:`spack-stack`. The WM is expected to build and run out-of-the-box on these systems, and users can download the WM code without first installing prerequisite software. Additionally, regression test data is already available on these systems. In general, users must have access to these Level 1 systems in order to use them.
Preconfigured (Level 1) systems for the UFS WM already have the required external libraries available in a central location via :term:`spack-stack`. The WM is expected to build and run out-of-the-box on these systems, and users can download the WM code without first installing prerequisite software. Additionally, regression test data is already available on these systems. In general, users must have access to these Level 1 systems in order to use them.

Currently, Level 1 (or Tier-1) platforms for regression testing are:

* WCOSS2 (Intel)
* Cheyenne (Intel/GNU compilers)
* Gaea (Intel)
* Hera (Intel/GNU compilers)
* Jet (Intel)
* Orion (Intel)
* Hercules (Intel/GNU compilers)
* AWS Docker container (Intel)

More information is available in the `UFS WM wiki <https://github.com/ufs-community/ufs-weather-model/wiki/Regression-Test-Policy-for-Weather-Model-Platforms-and-Compilers>`__.
Expand Down
4 changes: 2 additions & 2 deletions doc/UsersGuide/source/Glossary.rst
Original file line number Diff line number Diff line change
Expand Up @@ -120,11 +120,11 @@ Glossary

NCEPLIBS
The software libraries created and maintained by :term:`NCEP` that are required for running
:term:`chgres_cube`, the UFS Weather Model, and the :term:`UPP`. They are included in the `HPC-Stack <https://github.com/NOAA-EMC/hpc-stack>`__ and in `spack-stack <https://github.com/NOAA-EMC/spack-stack>`__.
:term:`chgres_cube`, the UFS Weather Model, and the :term:`UPP`. They are included in `spack-stack <https://github.com/NOAA-EMC/spack-stack>`__ and `HPC-Stack <https://github.com/NOAA-EMC/hpc-stack>`__.

NCEPLIBS-external
A collection of third-party libraries required to build :term:`NCEPLIBS`, :term:`chgres_cube`,
the UFS Weather Model, and the :term:`UPP`. They are included in the :term:`HPC-Stack` and in :term:`spack-stack`.
the UFS Weather Model, and the :term:`UPP`. They are included in :term:`spack-stack` and :term:`HPC-Stack`.

NEMS
The NOAA Environmental Modeling System is a common modeling framework whose purpose is
Expand Down
1 change: 1 addition & 0 deletions doc/UsersGuide/source/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,7 @@
# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
# ones.
extensions = [
'sphinx_rtd_theme',
'sphinx.ext.autodoc',
'sphinx.ext.doctest',
'sphinx.ext.intersphinx',
Expand Down
2 changes: 1 addition & 1 deletion tests/bl_date.conf
Original file line number Diff line number Diff line change
@@ -1 +1 @@
export BL_DATE=20231013
export BL_DATE=20231020
3 changes: 3 additions & 0 deletions tests/default_vars.sh
Original file line number Diff line number Diff line change
Expand Up @@ -454,6 +454,9 @@ export DO_GSL_DRAG_SS=.false.
export DO_GSL_DRAG_TOFD=.false.
export DO_UGWP_V1=.false.
export DO_UGWP_V1_OROG_ONLY=.false.
export KNOB_UGWP_DOKDIS=1
export KNOB_UGWP_NDX4LH=1


# resolution dependent settings
export CDMBWD_c48='0.071,2.1,1.0,1.0'
Expand Down
Loading

0 comments on commit 3182954

Please sign in to comment.