You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/source/BuildingRunningTesting/TestingLandDA.rst
+1-23Lines changed: 1 addition & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
Testing the Land DA Workflow
5
5
************************************
6
6
7
-
This chapter provides instructions for using the Land DA CTest suite. These steps are designed for use on :ref:`Level 1 <LevelsOfSupport>` systems (e.g., Ursa and Hercules) and may require significant changes on other systems.
7
+
This chapter provides instructions for using the Land DA CTest suite. These steps are designed for use on :ref:`Level 1 <LevelsOfSupport>` systems (e.g., Ursa and Hercules) and may require significant changes on other systems. They cannot be run via container at this time.
8
8
9
9
.. attention::
10
10
@@ -85,25 +85,3 @@ The bottom of the ``out.ctest`` file will include a message with test results. F
85
85
Total Test time (real) = 66.90 sec
86
86
87
87
If one or more tests fail, users can check the logs at ``${BASEDIR}/land-DA_workflow/sorc/build/Testing/Temporary/LastTest.log`` for more information on the failure.
88
-
89
-
Running Tests Using a Container
90
-
=================================
91
-
92
-
.. COMMENT: Update this container section for the release
93
-
94
-
.. attention::
95
-
96
-
The container CTest functionality has been tested in Jenkins. It should be able to run on a sufficiently large cloud instance. However, it is considered unsupported functionality because it has not been thoroughly tested on the cloud for use by the public.
97
-
98
-
For containers, the CTest functionality is wrapped in a Dockerfile. Therefore, users will need to build the Dockerfile to run the CTests. Since the Land DA container is quite large, this process can take a long time --- potentially hours. In the future, the development team hopes to simplify and shorten this process.
These files and their parameters are described in the following subsections. Although this download provides all files needed to run the provided sample cases, users wishing to configure their own cases will need to read :numref:`Section %s <InputFiles>` to determine what additional data they may need to download and where to find it.
57
50
58
51
@@ -125,7 +118,7 @@ The files contain the following data:
125
118
- "volumetric soil liquid"
126
119
- "m3/m3"
127
120
128
-
The full Land DA data bucket download (see :numref:`Section %s <sample-case-data>`) includes :term:`ICs` for Land DA in the ``inputs/NOAHMP_IC`` directory. These are essentially dummy ICs that can be used with LND and warmstart ATML cases. For :term:`ATML` coldstart cases, the ``fcst_ic`` task will generate the ICs by running the model for one cycle before performing DA, and users need not worry about staging ICs. For :term:`LND` or ATML warmstart cases, ICs must be provided. Users can use the ICs from the ``inputs/NOAHMP_IC`` directory (downloaded from the data bucket) for any case. In theory, users can also choose to use/produce their own ICs, either by running the ATML coldstart case for the cycle before the desired date or by generating them fro the :term:`GDAS` results. However, this is not yet supported functionality for the Land DA System.
121
+
The full Land DA data bucket download (see :numref:`Section %s <sample-case-data>`) includes :term:`ICs` for Land DA in the ``inputs/NOAHMP_IC`` directory. These are essentially dummy ICs that can be used with LND and warmstart ATML cases. For :term:`ATML` coldstart cases, the ``fcst_ic`` task will generate the ICs by running the model for one cycle before performing DA, and users need not worry about staging ICs. For :term:`LND` or ATML warmstart cases, ICs must be provided. Users can use the ICs from the ``inputs/NOAHMP_IC`` directory (downloaded from the data bucket) for any case. In theory, users can also choose to use/produce their own ICs, either by running the ATML coldstart case for the cycle before the desired date or by generating them from the :term:`GDAS` results. However, this is not yet supported functionality for the Land DA System.
129
122
130
123
.. _fv3-fix-tiled:
131
124
@@ -188,13 +181,13 @@ Observation Data
188
181
189
182
* Required for: All Land DA cases
190
183
191
-
The Land DA System can accepts:term:`GHCN`, :term:`IMS`, and :term:`SFCSNO` snow observation data. It accepts :term:`SMAP` or :term:`SMOPS` soil moisture observation data. Users need only provide one type of observation data depending on whether they plan to perform snow or soil moisture data assimilation.
184
+
The Land DA System can accept:term:`GHCN`, :term:`IMS`, and :term:`SFCSNO` snow observation data. It accepts :term:`SMAP` or :term:`SMOPS` soil moisture observation data. Users need only provide one type of observation data depending on whether they plan to perform snow or soil moisture data assimilation.
192
185
193
186
Currently, snow observation data is primarily drawn from the `Global Historical Climatology Network <https://www.ncei.noaa.gov/products/land-based-station/global-historical-climatology-network-daily>`_ (GHCN) and the U.S. National Ice Center (USNIC) Interactive Multisensor Snow and Ice Mapping System (`IMS <https://usicecenter.gov/Products/ImsHome>`_). GHCN and IMS data for provided sample cases are available in the ``inputs/DA_obs`` directory. These data are converted to :ref:`IODA <IODA>` format in the ``prep_data`` task.
194
187
195
188
Soil moisture data is primarily drawn from the National Snow and Ice Data Center `Soil Moisture Active Passive <https://nsidc.org/data/smap/data>`_ (SMAP) data set or from the NOAA `Soil Moisture Operational Products System <https://www.ospo.noaa.gov/products/land/smops/>`_ (SMOPS) data set. SMAP and SMOPS data for provided sample cases are available in the ``inputs/DATA_[smap|smops]`` directories. These data are converted to :ref:`IODA <IODA>` format in the ``prep_data`` task.
196
189
197
-
In each experiment, the ``land_analysis.yaml`` file sets the type(s) of observation files to be used in the experiment via the ``OBS_*_SNOW`` variables (based on selections in ``config.yaml``). Before assimilation, the files for the specified observation type are copied to the run directory (usually ``$BASEDIR/ptmp/<envir>/com/landda/${model_ver}/landda.${PDY}${cyc}/obs`` by default --- see :numref:`Section %s <nco-dir-entities>` for more on these variables), sometimes with a naming-convention change (e.g., ``ghcn_snwd_ioda_${YYYY}${MM}${DD}.nc`` to ``ghcn_snow_${YYYY}${MM}${DD}${HH}.nc``).
190
+
In each experiment, the ``land_analysis.yaml`` file sets the type(s) of observation files to be used in the experiment via the ``OBS_*_SNOW`` variables (based on selections in ``config.yaml``). Before assimilation, the files for the specified observation type are copied to the run directory (usually ``${BASEDIR}/ptmp/<envir>/com/landda/${model_ver}/landda.${PDY}${cyc}/obs`` by default --- see :numref:`Section %s <nco-dir-entities>` for more on these variables), sometimes with a naming-convention change (e.g., ``ghcn_snwd_ioda_${YYYY}${MM}${DD}.nc`` to ``ghcn_snow_${YYYY}${MM}${DD}${HH}.nc``).
198
191
199
192
.. _ghcn-io:
200
193
@@ -272,7 +265,7 @@ For additional download options, visit the `NSIDC NASA Earthdata Cloud Data Acce
272
265
SMOPS Soil Moisture Files
273
266
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
274
267
275
-
The `Soil Moisture Operational Products System <https://www.ospo.noaa.gov/products/land/smops/>` (SMOPS) "combines soil moisture retrievals from multi-satellites/sensors to provide a global soil moisture map with more spatial and temporal coverage." Observations for Land DA sample cases are available in the ``inputs/DATA_smops`` directory (downloaded in :numref:`Section %s <sample-case-data>`). However, users can download additional observation data for specific dates of choice from the National Environmental Satellite, Data, and Information Service (NESDIS) by navigating to the `NESDIS STAR file share <https://www.star.nesdis.noaa.gov/pub/smcd/emb/SMOPS/SMOPScdr/V2.0/>` and selecting/downloading data for those dates.
268
+
The `Soil Moisture Operational Products System <https://www.ospo.noaa.gov/products/land/smops/>`_ (SMOPS) "combines soil moisture retrievals from multi-satellites/sensors to provide a global soil moisture map with more spatial and temporal coverage." Observations for Land DA sample cases are available in the ``inputs/DATA_smops`` directory (downloaded in :numref:`Section %s <sample-case-data>`). However, users can download additional observation data for specific dates of choice from the National Environmental Satellite, Data, and Information Service (NESDIS) by navigating to the `NESDIS STAR file share <https://www.star.nesdis.noaa.gov/pub/smcd/emb/SMOPS/SMOPScdr/V2.0/>`_ and selecting/downloading data for those dates.
276
269
277
270
Cartopy Natural Earth Files
278
271
----------------------------
@@ -475,6 +468,8 @@ The FV3 component requires global fix files and FV3 initial conditions files. On
475
468
Global Fix Files
476
469
-------------------
477
470
471
+
* Required for: :term:`ATML` configurations
472
+
478
473
Global fix file data for the :term:`FV3` component are required to run the :term:`ATML` configurations. They are located in the ``inputs/FV3_fix_global`` directory (downloaded in :numref:`Section %s <sample-case-data>`).
479
474
480
475
.. code-block:: console
@@ -507,6 +502,8 @@ Note that options in brackets indicate multiple files with similar naming conven
507
502
``ATML`` Input Data for Initial Conditions Generation
Input data from GDAS or GFS is required to run the :term:`ATML` configurations. The data are located in the ``inputs/DATA_[gdas|gfs]`` directories (downloaded :ref:`above <InputFiles>`) and are used as initial conditions for the ``fcst_ic`` task. The :github:`exlandda_fcst_ic.sh <blob/develop/scripts/exlandda_fcst_ic.sh>` script sets the default path to this data using the ``COMINgdas`` and ``COMINgfs`` variables. The operational :nco:`WCOSS Implementation Standards <>` designate ``COMIN*`` directories as directories containing input data for the model indicated in the directory name (e.g., ``COMINgfs`` contains input data for the GFS model). In addition, these directories (``DATA_[gdas|gfs]``) contain the IMS raw data files. Within each ``COMIN*`` directory, data is organized by cycle date. For example, for ``20250119``, the following data is present in the ``DATA_gdas/20250119`` directory:
511
508
512
509
.. code-block:: console
@@ -699,190 +696,6 @@ To restart the Land DA System successfully after land model execution, all param
699
696
700
697
Restart files are located in the ``inputs/DATA_RESTART`` directory (downloaded :ref:`above <InputFiles>` from the data bucket). Each forecast cycle also outputs restart files that can be used as input for the next cycle date(s). These restart files will appear in the ``/ptmp/<envir>/com/landda/v<X.Y.Z>/landda.${PDY}/RESTART`` directory. However, users can generate their own RESTART files by running a coldstart GDAS or WM experiment and using the RESTART files produced.
701
698
702
-
.. _data-flow:
703
-
704
-
Data Flow Through the Land DA System
705
-
=======================================
706
-
707
-
Each step in the Land DA workflow requires particular ``sfc_data`` and restart files; tasks then produce output that may be used as input for the next step in a given cycle. :numref:`Table %s <LND-io>` and :numref:`Table %s <ATML-io>` illustrate the flow of data through the system. These tables demonstrate the important role that surface data files (``sfc_data.tile#.nc``) and restart files (``ufs.cpld.lnd.out.tile#.nc`` or ``ufs_land_restart.tile#.nc``) play as input for Land DA workflow tasks.
0 commit comments