diff --git a/doc/UsersGuide/source/doc-snippets/hsd_check_results.rst b/doc/UsersGuide/source/doc-snippets/hsd_check_results.rst index faa851e41a..a5eef368a5 100644 --- a/doc/UsersGuide/source/doc-snippets/hsd_check_results.rst +++ b/doc/UsersGuide/source/doc-snippets/hsd_check_results.rst @@ -18,21 +18,4 @@ When the test case finishes running, users should see console output that includ Compilation and model run directories can be accessed in the local repository via the ``run_dir`` softlink, which points to the actual ``FV3_RT`` directory. Each test generates ``atm*.nc`` and ``sfc*.nc`` files at specified forecast hour intervals. -Users can view progress of compile or model run phases by using the ``tail -f `` command or ``vi``/``vim`` on the ``err`` or ``out`` files in the ``run_dir/compile*`` or ``run_dir/`` directories. - -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 - -.. note:: - - Once the tests run successfully with the ``-c`` option (baseline created), users can compare future test results with the newly created baseline using ``-m`` instead of ``-c``. - -For further test management, users may save the test directory location in an environment variable: - -.. code-block:: console - - export UFS_WM_TEST=/path/to/expt_dirs/ufs_test +Users can view progress of compile or model run phases by using the ``tail -f `` command or ``vi``/``vim`` on the ``err`` or ``out`` files in the ``run_dir/compile*`` or ``run_dir/`` directories. \ No newline at end of file