JohnHalleyGotway · Sep 4, 2026 · Jul 23, 2024 · Jul 30, 2024 · Jul 30, 2024 · Aug 9, 2024
diff --git a/.github/workflows/linkcheck.yml b/.github/workflows/linkcheck.yml
@@ -0,0 +1,18 @@
+name: Linkcheck
+on:
+  schedule:
+    - cron: '0 6 * * 1'
+  pull_request:
+    paths:
+      - 'docs/**'
+  workflow_dispatch: {}
+
+jobs:
+  linkcheck:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: dtcenter/metplus-action-linkcheck@v1
+        with:
+          fail-on-broken-links: 'true'
+          upload-artifact: 'true'
diff --git a/docs/Contributors_Guide/code_profiling.rst b/docs/Contributors_Guide/code_profiling.rst
@@ -477,7 +477,7 @@ Overview of Steps for Performing Benchmarking
      View the consolidated metrics to identify potential performance enhancements.  Refer to the CTRACK documentation to
      learn about the metrics collected, under the **Metrics & Output** section:
 
-          https://github.com/Compaile/ctrack?tab=readme-ov-file#metrics--output
+          https://github.com/Compaile/ctrack#metrics--output
 
 
      .. note::

diff --git a/docs/Contributors_Guide/continuous_integration.rst b/docs/Contributors_Guide/continuous_integration.rst
@@ -17,9 +17,9 @@ These common workflows include:
 - `Testing (testing.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#testing-testing-yml>`_ to perform regression testing.
 - `Documentation (documentation.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#documentation-documentation-yml>`_ to check for problems building the documentation.
 - `SonarQube (sonarqube.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#sonarqube-sonarqube-yml>`_ to perform static code analysis.
-- `Build Docker Image and Trigger METplus Workflow (build_docker_and_trigger_metplus.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#build-docker-image-and-trigger-metplus-workflow-build-docker-trigger-metplus-yml>`_ to confirm that changes to METplus components do not break existing METplus use cases.
-- `Release Checksum (release-checksum.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#release-checksum-release-checksum-yml>`_ to create and attach checksum file assets to software releases.
-- `Release Docker Images (release-docker-images.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#release-docker-images-release-docker-images-yml>`_ to routinely recreate Docker images for recent software releases to minimize vulnerabilities.
+- `Build Docker Image and Trigger METplus Workflow (build_docker_and_trigger_metplus.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#build-docker-image-and-trigger-metplus-workflow-build-docker-and-trigger-metplus-yml>`_ to confirm that changes to METplus components do not break existing METplus use cases.
+- `Release Checksum (release-checksum.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#add-checksum-to-release-release-checksum-yml>`_ to create and attach checksum file assets to software releases.
+- `Release Docker Images (release-docker-images.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#create-release-docker-images-release-docker-images-yml>`_ to routinely recreate Docker images for recent software releases to minimize vulnerabilities.
 - `Update Truth (update_truth.yml) <https://metplus.readthedocs.io/en/latest/Contributors_Guide/continuous_integration.html#update-reference-branch-update-reference-branch-yml>`_ to update the reference truth data used by the testing workflow.
 
 .. _cg-ci-compilation_options:

diff --git a/docs/Users_Guide/appendixA.rst b/docs/Users_Guide/appendixA.rst
@@ -922,7 +922,7 @@ Q. How do I use “-sum”, “-add”, and “-subtract“ to achieve the same
      for comparison against 24-hourly StageIV precipitation with GFS data
      through the pcp_combine tool. Be aware that the 24-hour StageIV data is
      defined as an accumulation from 12Z on one day to 12Z on the next day:
-     http://www.emc.ncep.noaa.gov/mmb/ylin/pcpanl/stage4/
+     https://water.noaa.gov/about/precipitation-data-access
 
      Therefore, only the 24-hour StageIV data can be used to evaluate 12Z to
      12Z accumulations from the model. Alternatively, the 6- hour StageIV

diff --git a/docs/Users_Guide/config_options.rst b/docs/Users_Guide/config_options.rst
@@ -373,6 +373,13 @@ values and randomly perturbed ensemble member values. Values less than MIN are
 reset to the minimum value and values greater than MAX are reset to the maximum
 value. A value of NA indicates that the variable is unbounded.
 
+If the observation error table contains no entries for the variable being
+evaluated, MET prints a warning message and disables the observation error
+logic. If the table does contain entries for the variable, but the lookup for
+an individual observation fails, that observation is excluded from the analysis.
+This situation would occur, for example, when the observation value falls outside
+the range of values in the VAL_RANGE column.
+
 MET_GRIB_TABLES
 ---------------
 
@@ -401,7 +408,7 @@ The following lines consist of 4 integers followed by 3 strings:
 
 References:
 | `Office Note 388 GRIB1 <http://www.nco.ncep.noaa.gov/pmb/docs/on388>`_
-| `A Guide to the Code Form FM 92-IX Ext. GRIB Edition 1 <http://www.wmo.int/pages/prog/www/WMOCodes/Guides/GRIB/GRIB1-Contents.html>`_
+| `A Guide to the Code Form FM 92-IX Ext. GRIB Edition 1 <https://community.wmo.int/site/knowledge-hub/programmes-and-initiatives/wmo-information-system-wis/grib-edition-1>`_
 
 
 GRIB2 table files begin with "grib2" prefix and end with a ".txt" suffix.
@@ -2444,7 +2451,7 @@ used by the World Meteorological Organization (WMO) can be found in "ConfigConst
   WMO_DPT2M_LAPSE_RATE_K_per_M = 0.0012;
 
 Note that the lapse rate value depends on the units of temperature and elevation
-and the user is responsibile for defining it appropriately.
+and the user is responsible for defining it appropriately.
 
 All "lapse_rate_correction" entries can be set separately in each "obs.field" entry.
 

diff --git a/docs/Users_Guide/gsi-tools.rst b/docs/Users_Guide/gsi-tools.rst
@@ -6,7 +6,7 @@ GSI Tools
 
 Gridpoint Statistical Interpolation (GSI) diagnostic files are binary files written out from the data assimilation code before the first and after each outer loop. The files contain useful information about how a single observation was used in the analysis by providing details such as the innovation (O-B), observation values, observation error, adjusted observation error, and quality control information.
 
-For more detail on generating GSI diagnostic files and their contents, see the `GSI User's Guide. <http://www.dtcenter.org/com-GSI/users/docs/index.php>`_
+For more detail on generating GSI diagnostic files and their contents, see the `GSI User's Guide (pdf) <https://dtcenter.org/sites/default/files/community-code/gsi/docs/users-guide/GSIUserGuide_v3.7.pdf>`_.
 
 When MET reads GSI diagnostic files, the innovation (O-B; generated prior to the first outer loop) or analysis increment (O-A; generated after the final outer loop) is split into separate values for the observation (OBS) and the forecast (FCST), where the forecast value corresponds to the background (O-B) or analysis (O-A).
 

diff --git a/docs/Users_Guide/installation.rst b/docs/Users_Guide/installation.rst
@@ -41,8 +41,8 @@ The required libraries are listed below:
   in C and CXX, for intermediate and output file formats
 * `HDF5 <https://support.hdfgroup.org/ftp/HDF5/releases/hdf5-1.12/hdf5-1.12.2/src/hdf5-1.12.2.tar.gz>`__
   is required to support NetCDF 4. HDF5 should be built with
-  `zlib <http://www.zlib.net/>`_
-* `GSL <http://www.gnu.org/software/gsl>`_
+  `zlib <https://www.zlib.net/>`_
+* `GSL <https://www.gnu.org/software/gsl/doc/html/index.html>`_
   GNU Scientific Library Developer's Version for computing
   confidence intervals (use **GSL-1.11** for **PGI** compilers)
 * `Proj <https://proj.org/>`_ Library used to instantiate grids within MET
@@ -84,7 +84,7 @@ They are not required for MET to function, but depending on the user’s intende
   for re-gridding GRIB version 2 data
 * `Integrated Data Viewer (IDV) <http://www.unidata.ucar.edu/software/idv>`_
   for displaying gridded data, including GRIB and NetCDF
-* `ncview utility <http://meteora.ucsd.edu/~pierce/ncview_home_page.html>`_
+* `ncview utility <https://anaconda.org/channels/conda-forge/packages/ncview/overview>`_
   for viewing gridded NetCDF data (e.g. the output of pcp_combine)
 
 .. _compile_script_install:
@@ -108,7 +108,7 @@ installed. Assuming that the following guidance uses “/d1” as the parent dir
 a suggested format is a path to a “met” directory, followed by the version number
 subdirectory (e.g. /d1/met/13.0.0).
 Next, download the
-`compile_MET_all.sh <https://raw.githubusercontent.com/dtcenter/MET/main_v13.0/internal/scripts/installation/compile_MET_all.sh>`_
+`compile_MET_all.sh <https://raw.githubusercontent.com/dtcenter/MET/HEAD/internal/scripts/installation/compile_MET_all.sh>`_
 script and
 `tar_files.tgz <https://dtcenter.ucar.edu/dfiles/code/METplus/MET/installation/tar_files.tgz>`_
 file and place both of these files in the
@@ -118,7 +118,7 @@ the terminal while in the directory MET will be installed in:
 
 .. code-block:: ini
 
-  wget https://raw.githubusercontent.com/dtcenter/MET/main_v13.0/internal/scripts/installation/compile_MET_all.sh
+  wget https://raw.githubusercontent.com/dtcenter/MET/HEAD/internal/scripts/installation/compile_MET_all.sh
   wget https://dtcenter.ucar.edu/dfiles/code/METplus/MET/installation/tar_files.tgz
 
 The tar files will need to be extracted in the MET installation directory:
@@ -170,7 +170,7 @@ environment variables is in an environment configuration file
 configuration file to start with (**install_met_env.generic_gnu**),
 as well as the environment configuration files used on HPCs at NCAR and NOAA,
 can be found in the `MET GitHub repository <https://github.com/dtcenter/MET>`_ in the
-`scripts/installation/config <https://github.com/dtcenter/MET/tree/main_v13.0/internal/scripts/installation/config>`_
+`scripts/installation/config <https://github.com/dtcenter/MET/tree/HEAD/internal/scripts/installation/config>`_
 directory.
 
 .. note:: Starting with MET-12.0.0, C++17 is the default C++ standard for MET due to the requirements of its dependent libraries. However, MET itself only makes use of C++11 features.

diff --git a/docs/Users_Guide/met-tc_overview.rst b/docs/Users_Guide/met-tc_overview.rst
@@ -105,7 +105,7 @@ The BEST is in ATCF file format and contains all the above listed common fields.
 
 All operational model aids and the BEST can be obtained from the `NHC ftp server. <ftp://ftp.nhc.noaa.gov/atcf/archive/>`_
 
-`Click here for detailed information on the ATCF format description and specifications. <http://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt>`_
+`Click here for detailed information on the ATCF format description and specifications. <https://science.nrlmry.navy.mil/atcf/docs/database/new/abdeck.txt>`_
 
 If a user has gridded model output, the model data must be run through a vortex tracking algorithm in order to obtain the ATCF-formatted input that MET-TC requires. Many vortex tracking algorithms have been developed in order to obtain basic position, maximum wind, and minimum sea level pressure information from model forecasts. One vortex tracking algorithm that is supported and freely available is the `GFDL vortex tracker package. <https://dtcenter.org/community-code/gfdl-vortex-tracker>`_
 

diff --git a/docs/Users_Guide/mode.rst b/docs/Users_Guide/mode.rst
@@ -11,7 +11,7 @@ Introduction
 
 This section provides a description of the Method for Object-Based Diagnostic Evaluation (MODE) tool, which was developed at the Research Applications Laboratory, NCAR/Boulder, USA. More information about MODE can be found in :ref:`Davis et al. (2006a,b) <Davis-2006>`, :ref:`Brown et al. (2007) <Brown-2007>` and :ref:`Bullock et al. (2016) <Bullock-2016>`.
 
-MODE was developed in response to a need for verification methods that can provide diagnostic information that is more directly useful and meaningful than the information that can be obtained from traditional verification approaches, especially in application to high-resolution NWP output. The MODE approach was originally developed for application to spatial precipitation forecasts, but it can also be applied to other fields with coherent spatial structures (*e.g.*, clouds, convection). MODE is only one of a number of different approaches that have been developed in recent years to meet these needs. In the future, we expect that the MET package will include additional methods. References for many of these methods are provided at the `MesoVict website <http://www.rap.ucar.edu/projects/icp/index.html.>`_.
+MODE was developed in response to a need for verification methods that can provide diagnostic information that is more directly useful and meaningful than the information that can be obtained from traditional verification approaches, especially in application to high-resolution NWP output. The MODE approach was originally developed for application to spatial precipitation forecasts, but it can also be applied to other fields with coherent spatial structures (*e.g.*, clouds, convection). MODE is only one of a number of different approaches that have been developed in recent years to meet these needs. In the future, we expect that the MET package will include additional methods. References for many of these methods are provided at the `MesoVict website <http://www.rap.ucar.edu/projects/icp/index.html>`_.
 
 MODE may be used in a generalized way to compare any two fields. For simplicity, field_1 may be thought of in this section as "the forecast", while field_2 may be thought of as "the observation", which is usually a gridded analysis of some sort. The convention of field_1/field_2 is also used in :numref:`MODE_object_attribute`. MODE resolves objects in both the forecast and observed fields. These objects mimic what humans would call "regions of interest". Object attributes are calculated and compared, and are used to associate ("merge") objects within a single field, as well as to "match" objects between the forecast and observed fields. Finally, summary statistics describing the objects and object pairs are produced. These statistics can be used to identify correlations and differences among the objects, leading to insights concerning forecast strengths and weaknesses.
 

diff --git a/docs/Users_Guide/reformat_point.rst b/docs/Users_Guide/reformat_point.rst
@@ -622,7 +622,7 @@ The NetCDF output of the ASCII2NC tool is structured in the same way as the outp
 MADIS2NC Tool
 =============
 
-This section describes how to run the MADIS2NC tool. The MADIS2NC tool is used to reformat `Meteorological Assimilation Data Ingest System (MADIS) <http://madis.noaa.gov>`_ point observations into the NetCDF format expected by the MET statistics tools. An optional configuration file controls the processing of the point observations. The MADIS2NC tool supports many of the MADIS data types, as listed in the usage statement below. Support for additional MADIS data types may be added in the future based on user feedback.
+This section describes how to run the MADIS2NC tool. The MADIS2NC tool is used to reformat `Meteorological Assimilation Data Ingest System (MADIS) <https://madis.ncep.noaa.gov>`_ point observations into the NetCDF format expected by the MET statistics tools. An optional configuration file controls the processing of the point observations. The MADIS2NC tool supports many of the MADIS data types, as listed in the usage statement below. Support for additional MADIS data types may be added in the future based on user feedback.
 
 madis2nc Usage
 --------------

diff --git a/docs/Users_Guide/refs.rst b/docs/Users_Guide/refs.rst
@@ -215,7 +215,7 @@ References
 |   *Probabilistic Forecasting Using Ensemble Model Output Statistics and*
 |   *Minimum CRPS Estimation*. Technical Report no. 449, Department of
 |   Statistics, University of Washington. Available at
-|   http://www.stat.washington.edu/www/research/reports/
+|   https://stat.uw.edu/research/tech-reports/calibrated-probabilistic-forecasting-using-ensemble-model-output-statistics-and-minimum-crps
 |
 
 .. _Haiden-2012:

diff --git a/docs/Users_Guide/tc-pairs.rst b/docs/Users_Guide/tc-pairs.rst
@@ -43,7 +43,7 @@ Diagnostics from the SHIPS Development Datasets (SHIPS_DIAG_DEV) will be support
 
 A future version of MET will also allow the CIRA model diagnostics to be computed directly from model forecast fields. Until then, users may obtain the SHIPS diagnostics at the following locations:
 
-  * SHIPS_DIAG_DEV: https://rammb2.cira.colostate.edu/research/tropical-cyclones/ships/#DevelopmentalData
+  * SHIPS_DIAG_DEV: https://rammb2.cira.colostate.edu/research/tropical-cyclones/ships/development_data
 
   * SHIPS_DIAG_RT: https://ftp.nhc.noaa.gov/atcf/lsdiag/
 

diff --git a/docs/conf.py b/docs/conf.py
@@ -124,6 +124,28 @@
     'figure': 'Figure %s',
 }
 
+# -- linkcheck builder configuration ----------------------------------
+# https://www.sphinx-doc.org/en/master/usage/configuration.html#options-for-the-linkcheck-builder
+
+linkcheck_timeout = 10
+linkcheck_retries = 2
+linkcheck_workers = 8
+
+linkcheck_ignore = [
+    # add regex patterns for URLs that should be skipped, e.g.:
+    # r'https://dtcenter\.org/.*',   # if this site blocks automated requests
+    # r'https://doi\.org/.*',
+    # r'https://journals\.ametsoc\.org/.*',
+    # 'https://agupubs\.onlinelibrary\.wiley\.com/.*',  # AGU journals, similar bot-blocking behavior
+]
+
+linkcheck_allowed_redirects = {
+    # map of regex -> regex for redirects that are fine to follow
+}
+
+linkcheck_anchors = True
+linkcheck_anchors_ignore = ['^!']
+
 # -- Export variables --------------------------------------------------------
 
 rst_epilog = f"""
@@ -132,3 +154,4 @@
 .. |release_date| replace:: {release_date}
 .. |release_year| replace:: {release_year}
 """
+