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

[develop]: Add documentation for HSD cases in tests-dev #2498

Draft
wants to merge 30 commits into
base: develop
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
30 commits
Select commit Hold shift + click to select a range
7dc7eb0
rm unmaintainable rt-specific config info
gspetro-NOAA Oct 21, 2024
8b857fc
add HSD ch, rename RTConf ch, update index and bib
gspetro-NOAA Oct 22, 2024
d9dfc5f
add back ConfParams doc
gspetro-NOAA Oct 22, 2024
f7dd5ad
rm old Configurations doc
gspetro-NOAA Oct 22, 2024
cb3ba89
misc minor updates
gspetro-NOAA Oct 25, 2024
0705cc7
Added infoabout Baroclinic case and provided information on running I…
Oct 30, 2024
34535fa
resolve merge conflict
gspetro-NOAA Oct 31, 2024
b8bb06b
change file name
selbigmtnwx23 Oct 31, 2024
d25c4cf
Merge branch 'text/us-415' of https://github.com/jdkublnick/ufs-weath…
selbigmtnwx23 Oct 31, 2024
0254e40
jdk updates
selbigmtnwx23 Oct 31, 2024
1a52f2c
Updated Baroclinic wave information
Nov 8, 2024
472ba13
finish details for 2020 july cape case
selbigmtnwx23 Nov 12, 2024
859c31f
Merge branch 'ufs-community:develop' into text/us-414
gspetro-NOAA Nov 13, 2024
933d580
update/rename cases&configs ch
gspetro-NOAA Nov 13, 2024
c355cf0
resolve merge conflict
gspetro-NOAA Nov 13, 2024
015a69b
Merge branch 'text/us-414' of github.com:gspetro-NOAA/ufs-weather-mod…
gspetro-NOAA Nov 13, 2024
997d85e
Merge branch 'text/us-415' of https://github.com/jdkublnick/ufs-weath…
gspetro-NOAA Nov 13, 2024
7d2889e
update TOC
gspetro-NOAA Nov 14, 2024
87bb385
edit instructions for HSD
gspetro-NOAA Nov 14, 2024
a6de59c
update bibliography and HSD intro
gspetro-NOAA Nov 14, 2024
13ee1c0
add test config info
gspetro-NOAA Nov 14, 2024
a9ae084
update bibliography and baroclinic wave summary
gspetro-NOAA Nov 14, 2024
00a403b
update baroclinic wave case
gspetro-NOAA Nov 14, 2024
7da1017
update CAPE case
gspetro-NOAA Nov 14, 2024
e995553
update 2020 CAPE case
gspetro-NOAA Nov 14, 2024
018225b
add data info
gspetro-NOAA Nov 14, 2024
6730f45
refactor HSD docs
gspetro-NOAA Nov 15, 2024
305d43f
update WM docs to use extlinks
gspetro-NOAA Nov 15, 2024
2399d6c
update CAPE expt for different resolutions
gspetro-NOAA Nov 15, 2024
39e5508
add Jet instructions
gspetro-NOAA Nov 15, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions doc/UsersGuide/source/BuildingAndRunning.rst
Original file line number Diff line number Diff line change
Expand Up @@ -452,7 +452,7 @@ Running the Model

.. attention::
Although the following discussions are general, users may not be able to execute the script successfully "as is" unless they are on a
`Tier-1 platform <https://github.com/ufs-community/ ufs-weather-model/wiki/Regression-Test-Policy-for-Weather-Model-Platforms-and-Compilers>`__.
:wm-wiki:`Tier-1 platform <Regression-Test-Policy-for-Weather-Model-Platforms-and-Compilers>`.

.. _UsingRegressionTest:

Expand Down Expand Up @@ -504,8 +504,7 @@ or (2) create a new file (e.g., ``my_rt.conf``), add the tests, and execute ``./
On NOAA RDHPCS
------------------

On `Tier-1 platforms <https://github.com/ufs-community/ufs-weather-model/wiki
/Regression-Test-Policy-for-Weather-Model-Platforms-and-Compilers>`__, users can run
On :wm-wiki:`Tier-1 platforms <Regression-Test-Policy-for-Weather-Model-Platforms-and-Compilers>`, users can run
regression tests by editing the ``rt.conf`` file and executing:

.. code-block:: console
Expand Down Expand Up @@ -733,8 +732,7 @@ operational requirement test. The only difference is that the ``opnReqTest`` scr
The ``tests/opnReqTests`` directory contains
opnReqTest-specific lower-level scripts used to set up run configurations.

On `Tier-1 platforms <https://github.com/ufs-community/ ufs-weather-model/wiki
/Regression-Test-Policy-for-Weather-Model-Platforms-and-Compilers>`_, tests can
On :wm-wiki:`Tier-1 platforms <Regression-Test-Policy-for-Weather-Model-Platforms-and-Compilers>`, tests can
be run by invoking

.. code-block:: console
Expand Down
99 changes: 99 additions & 0 deletions doc/UsersGuide/source/CAPE2020.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
.. role:: raw-html(raw)
:format: html

.. _cape-2020:

====================
July 2020 CAPE Case
====================

The July 2020 CAPE case is an atmosphere-only forecast run at C48 resolution with 127 vertical levels. It is set to run a 24-hour forecast from 2020-07-23 at 0z using the `FV3_GFS_v16 <https://dtcenter.ucar.edu/GMTB/v7.0.0/sci_doc/_g_f_s_v16_page.html>`_ physics suite and default values from the WM's `default_vars.sh <https://github.com/ufs-community/ufs-weather-model/blob/develop/tests/default_vars.sh>`_ ``export_fv3_v16`` function.

The original July 2020 CAPE case illustrated a shortcoming of the Global Forecast System (GFS) v16 --- low Convective Available Potential Energy (CAPE) predictions during summertime (:cite:t:`SunEtAl2024`). :cite:t:`SunEtAl2024` (2024) used this case study to investigate the low CAPE bias in the GFS and determined that "the GFS simulates smaller surface latent heat flux and larger surface sensible heat flux than the observations" due to "slightly drier-than-observed soil moisture" within the offline Global Data Assimilation System (GDAS) initial conditions used in the study. This resulted in less latent heat and moisture being fed back to the lower levels of the atmosphere and ultimately changed the overall vertical profile of the atmosphere, which lowered CAPE values relative to the older GFS v15.2.

The UFS WM and its subcomponents have undergone signficant changes since the original July 2020 CAPE case study was posted and since :cite:t:`SunEtAl2024`'s experiment, so the current GFS v16 CAPE bias may have shifted. However, users may still wish to run this case and then experiment with different (potentially user-generated) initial conditions, a coupled land surface model (LSM), or other factors to explore factors that improve or worsen CAPE bias. Additionally, :cite:t:`SunEtAl2024`'s findings only apply to this case study, so users may wish to expand their research to include other warm-season cases.

============================================
Obtaining Data for the July 2020 CAPE Case
============================================

.. include:: ./doc-snippets/hsd_data.rst

.. _chgres-data:

User-Generated Data
---------------------

Users can enable the WM to run using GFS initial conditions (ICs) from the UFS Case Studies page. Users can use these files


.. _run-cape:

=================================
Running the July 2020 CAPE Case
=================================

This section explains how to run the July 2020 CAPE case described above using the ``ufs-test.sh`` script.

Clone the Repository
--------------------

.. include:: ./doc-snippets/clone_hsd.rst

Machine Configuration
-----------------------

.. include:: ./doc-snippets/hsd_machine_config.rst

.. _cape-config:

Test Configuration
----------------------

The July 2020 CAPE case can be run as-is without adjusting the configuration. If users choose to run the case at higher resolutions, they can generate GFS ICs at C192, C384, or C768 resolutions following the instructions :ref:`above <chgres-data>`. However, they will also need to adapt the experiment configuration files (``${UFS_WM}/tests-dev/test_cases/tests/2020_CAPE`` and potentially ``${UFS_WM}/tests-dev/test_cases/exp_conf/2020_CAPE``). Configurations at these higher resolutions are untested, and users can expect to do some troubleshooting to make them work.

It is recommended that users view the :wm-repo:`control_c192 <blob/develop/tests/tests/control_c192>`, :wm-repo:`control_c384 <blob/develop/tests/tests/control_c384>`, or :wm-repo:`control_c768 <blob/develop/tests/tests/control_c768>` test files as a starting point. Those test files will provide guidance on variable settings and model_configure/input namelist settings. Additionally, users will need to ensure that the ``FV3_RUN`` file (named ``2020_CAPE.IN`` for the 2020_CAPE experiment) points to the correct input data. Users can modify the ``parm/fv3_conf`` files associated with the sample ``control_*`` tests to enable use of v2 surface data (as in the :wm-repo:`control_c48.v2.sfc <blob/develop/tests/tests/control_c48.v2.sfc>` or 2020_CAPE cases).

.. attention::

Although it is *possible* to adjust the July 2020 CAPE case to run at non-default resolutions, this is unsupported functionality. Users may experiment with the capability but will need to commit to significant troubleshooting/experimentation to run the case at those resolutions.

Baseline Configuration
----------------------

.. include:: ./doc-snippets/hsd_baseline_config.rst

Running Tests
-------------

.. include:: ./doc-snippets/hsd_run_tests.rst

Examples
^^^^^^^^^^

A user with access to the ``epic`` account can run the ``2020_CAPE`` test case with the ``intel`` compiler on ``Hera``, ``Orion``, or ``Gaea`` using the following command:

.. code-block:: console

./ufs_test.sh -a epic -s -c -k -r -n "2020_CAPE intel"

Running Multiple Cases
^^^^^^^^^^^^^^^^^^^^^^^^

.. include:: ./doc-snippets/hsd_run_multiple.rst

.. _check-results:

Checking Results
-----------------

.. include:: ./doc-snippets/hsd_check_results.rst

For example, to monitor progress or check results for the ``2020_CAPE_intel`` case, run:

.. code-block:: console

tail -f ${UFS_WM}/tests-dev/run_dir/2020_CAPE_intel/err
tail -f ${UFS_WM}/tests-dev/run_dir/2020_CAPE_intel/out

.. include:: ./doc-snippets/hsd_notes.rst
2 changes: 1 addition & 1 deletion doc/UsersGuide/source/CodeOverview.rst
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Currently, Level 1 (or Tier-1) platforms for regression testing are:
* 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>`__.
More information is available in the :wm-wiki:`UFS WM wiki <Regression-Test-Policy-for-Weather-Model-Platforms-and-Compilers>`.

Level 2-4 Systems
===================
Expand Down
Loading