dtcenter · JohnHalleyGotway · Jul 15, 2026 · Jul 2, 2024 · Jul 2, 2024 · Jul 9, 2024
diff --git a/.github/jobs/set_job_controls.sh b/.github/jobs/set_job_controls.sh
@@ -5,11 +5,26 @@
 run_unit_tests=false
 run_diff=false
 run_update_truth=false
-met_base_repo=met-base
-met_base_tag=3.4-latest
 input_data_version=develop
 truth_data_version=develop
 
+# set constants for the MET base repository names (regular and unit test)
+MET_BASE_REPO_NAME=met-base
+MET_BASE_UNIT_REPO_NAME=met-base-unit-test
+
+# set MET base repo to regular repo by default for compilation check
+met_base_repo=${MET_BASE_REPO_NAME}
+
+# default MET base tag
+# TODO: Change 3.4 back to 3.5 after solving TC-Diag failure
+met_base_tag=3.4-latest
+
+# override the MET base tag if set
+if [[ -n "${met_base_tag_override}" ]]; then
+    met_base_tag=${met_base_tag_override}
+fi
+
+
 if [ "${GITHUB_EVENT_NAME}" == "pull_request" ]; then
 
   # only run diff logic if pull request INTO 
@@ -122,11 +137,20 @@
 # if running unit tests, use unit_test MET base image and push image
 if [ "$run_unit_tests" == "true" ]; then
 
-  met_base_repo=met-base-unit-test
+  # set MET base repo to the unit test version to get the test tools
+  met_base_repo=${MET_BASE_UNIT_REPO_NAME}
+
   run_push=true
 
 fi
 
+# add -dev to the MET base repo if the tag does not start with a number
+# this assumes that met-base and met-base-unit-test tags start with a number and
+# development tags, e.g. branch names, do not
+if [[ ! ${met_base_tag} =~ ^[0-9] ]]; then
+  met_base_repo=${met_base_repo}-dev
+fi
+
 echo "run_compile=${run_compile}" >> $GITHUB_OUTPUT
 echo "run_push=${run_push}" >> $GITHUB_OUTPUT
 echo "run_unit_tests=${run_unit_tests}" >> $GITHUB_OUTPUT

diff --git a/.github/workflows/testing.yml b/.github/workflows/testing.yml
@@ -39,6 +39,10 @@ on:
         description: 'Run the unit tests'
         default: true
         type: boolean
+      met_base_tag:
+        description: 'Override the MET base tag'
+        default: ''
+        required: false
 
 env:
   DOCKERHUB_REPO: dtcenter/met-dev
@@ -57,6 +61,7 @@ jobs:
         env:
           commit_msg: ${{ github.event.head_commit.message }}
           force_tests: ${{ github.event.inputs.force_tests }}
+          met_base_tag_override: ${{ github.event.inputs.met_base_tag }}
 
     outputs:
       run_compile: ${{ steps.job_status.outputs.run_compile }}
@@ -148,7 +153,7 @@ jobs:
           - jobid: 'job1' 
             tests: 'ascii2nc'
           - jobid: 'job2'
-            tests: 'pb2nc madis2nc pcp_combine gen_ens_prod regrid'
+            tests: 'pb2nc madis2nc pcp_combine gen_ens_prod regrid winds'
       fail-fast: false
     steps:
       - uses: actions/checkout@v6

diff --git a/data/config/ConfigConstants b/data/config/ConfigConstants
@@ -22,6 +22,18 @@ output_precision = 5;
 // MET_TMP_DIR.
 tmp_dir = "/tmp";
 
+////////////////////////////////////////////////////////////////////////////////
+//
+// Settings to define wind vector metadata.
+//
+////////////////////////////////////////////////////////////////////////////////
+
+// Comma-separated lists of wind variable names for rotating and deriving
+u_wind_field_name = "UGRD,U";
+v_wind_field_name = "VGRD,V";
+wind_speed_field_name = "WIND,SP";
+wind_direction_field_name = "WDIR,DD";
+
 ////////////////////////////////////////////////////////////////////////////////
 //
 // Standard unit conversion functions.

diff --git a/docs/Users_Guide/config_options.rst b/docs/Users_Guide/config_options.rst
@@ -661,6 +661,41 @@ Some tools override the temporary directory by the command line argument
 A description of the use of temporary files in MET can be found in
 :numref:`Contributor's Guide Section %s <tmp_file_use>`.
 
+.. _config_wind_field_names:
+
+wind_field_names
+----------------
+
+As described in :numref:`PS_wind_rotation_derivation`, MET can automatically
+derive wind variables and also rotate them from being grid-relative to earth-relative.
+Logic is provided for each supported input file type to identify input wind components
+and determine whether they are defined as being grid-relative or earth-relative.
+
+The following configuration options can be set to refine the metadata, when needed:
+
+.. code-block:: none
+
+  is_u_wind         = boolean;
+  is_v_wind         = boolean;
+  is_grid_relative  = boolean;
+  is_wind_speed     = boolean;
+  is_wind_direction = boolean;
+
+When deriving and rotating winds, MET searches the input file for matching wind
+components. That search is driven by the following configuration options and
+default values found in the "data/config/ConfigConstants" file:
+
+.. code-block:: none
+
+  u_wind_field_name = "UGRD,U";
+  v_wind_field_name = "VGRD,V";
+  wind_speed_field_name = "WIND,SP";
+  wind_direction_field_name = "WDIR,DD";
+
+Each is a comma-separated list of wind variable names to be searched. Users can
+explicity set these options to configure what data should be used in the wind
+derivation and rotation logic.
+
 message_type_group_map
 ----------------------
 

diff --git a/docs/Users_Guide/point-stat.rst b/docs/Users_Guide/point-stat.rst
@@ -117,6 +117,35 @@ _______________________
 
 The forecast value at P is chosen as the grid point inside the interpolation area whose value most closely matches the observation value.
 
+.. _PS_wind_rotation_derivation:
+
+Wind Rotation and Derivation
+----------------------------
+
+Numerical weather prediction model output often defines winds relative to the orientation of the model grid rather than true north-south and east-west directions on the earth.
+However point observations typically define winds relative to true earth directions. Prior to comparing them, the model wind data must be rotated from grid-relative to
+to earth-relative. While the degree of grid-to-earth rotation varies based on the projection type and location, failing to rotate the winds can have a significant impact on
+the verification results.
+
+For simplicity, the MET library code attempts to rotate all wind components from being grid-relative to earth-relative regardless of whether they are being compared to point
+observations with the Point-Stat tool or gridded analyses with the Grid-Stat tool. Running the MET tools at verbosity level 3 (-v 3) prints log messages to describing the wind
+rotation process. While the logic to determine whether input winds are grid-relative varies by file type, specifying the **is_grid_relative = FALSE;** configuration option
+manually overrides that logic and prevents winds from being rotated.
+
+Wind fields which must be rotated include wind direction and both the U and V components of the wind vector. While wind direction can be rotated by itself, both U and V are
+required to rotate either component. When processing U-wind data, MET attempts to read corresponding V-wind data and vice-versa.
+
+The configuration options for wind rotation and derivation in MET are described in section :numref:`config_wind_field_names`.
+
+When reading V-wind data to rotate U-wind or U-wind data to rotate V-wind, MET first searches using the same field name, but with both upper and lowercase U's and V's
+swapped (e.g. for "U_PL" search for "V_PL"). If the result is unsuccesful, it searches other common field names specified by the **u_wind_field_name** and **v_wind_field_name**
+configuration options. If needed, users should set these configuration options to indicate how the U-wind and V-wind data should be paired.
+
+In addition to rotating winds, MET can also derive them. If U-wind and V-wind are present in the input file, request field names of **WDIR**, **WIND**, or **KENG**
+to derive wind direction, wind speed, and kinetic engery from the U and V components, respectively. If wind speed and direction are present in the input file, request field
+names of **UGRD** or **VGRD** for MET to derive the U and V components from them. Depending on the wind field naming conventions, the configuration options described in
+:numref:`config_wind_field_names` may be required to configure this derivation logic.
+
 .. _PS_HiRA_framework:
 
 HiRA Framework

diff --git a/docs/Users_Guide/release-notes.rst b/docs/Users_Guide/release-notes.rst
@@ -182,6 +182,14 @@ MET Version 13.0.0 Upgrade Instructions
      * The "ensemble_flag.eas" and "ensemble_flag.eas_width" entries are added to enable the
        writing of EAS output fields.
 
+   * ConfigConstanst configuration file
+
+     * The "u_wind_field_name", "v_wind_field_name", "wind_speed_field_name", and "wind_direction_field_name"
+       entries are comma-separated lists of field names to search when read wind data needed to derive winds
+       or rotate them from being grid-relative to earth-relative. See :numref:`PS_wind_rotation_derivation`
+       for a description of wind rotation and derivation and :numref:`config_wind_field_names` for the
+       corresponding configuration options.
+
 .. dropdown:: Output format changes - NONE
 
 .. dropdown:: Output format changes - NONE

diff --git a/internal/scripts/docker/Dockerfile b/internal/scripts/docker/Dockerfile
@@ -1,5 +1,5 @@
 ARG MET_BASE_REPO=met-base
-ARG MET_BASE_TAG=3.5-latest
+ARG MET_BASE_TAG=3.4-latest
 
 FROM dtcenter/${MET_BASE_REPO}:${MET_BASE_TAG}
 MAINTAINER John Halley Gotway <johnhg@ucar.edu>
@@ -10,7 +10,7 @@ MAINTAINER John Halley Gotway <johnhg@ucar.edu>
 ARG SOURCE_BRANCH
 
 #
-# SOURCE_BRANCH is not defined when built via Docker Hub.
+# Fail if SOURCE_BRANCH is not defined
 #
 RUN if [ "x${SOURCE_BRANCH}" = "x" ]; then \
       echo "ERROR: SOURCE_BRANCH undefined! Rebuild with \"--build-arg SOURCE_BRANCH={branch name}\""; \
@@ -24,11 +24,6 @@ ENV MET_REPO_DIR=/met/MET-${MET_GIT_NAME}
 ENV MET_GIT_URL=https://github.com/dtcenter/MET
 ENV MET_DEVELOPMENT=true
 
-#
-# Update the OS, as needed.
-#
-RUN apt update
-
 #
 # Set the working directory.
 #
@@ -38,8 +33,10 @@ WORKDIR /met
 # Download and install MET.
 # Delete the MET source code for tagged releases matching "v"*.
 #
-RUN echo "Checking out MET ${MET_GIT_NAME} from ${MET_GIT_URL}" \
- && git clone ${MET_GIT_URL} ${MET_REPO_DIR} \
- && cd ${MET_REPO_DIR} \
- && git checkout ${MET_GIT_NAME} \
- && internal/scripts/docker/build_met_docker.sh
+RUN \
+    echo "Checking out MET ${MET_GIT_NAME} from ${MET_GIT_URL}" &&\
+    git clone ${MET_GIT_URL} ${MET_REPO_DIR} \
+ && echo "Build MET" &&\
+    (cd ${MET_REPO_DIR} &&\
+     git checkout ${MET_GIT_NAME} &&\
+     internal/scripts/docker/build_met_docker.sh)
diff --git a/internal/scripts/docker/Dockerfile.copy b/internal/scripts/docker/Dockerfile.copy
@@ -1,5 +1,5 @@
 ARG MET_BASE_REPO=met-base-unit-test
-ARG MET_BASE_TAG=3.5-latest
+ARG MET_BASE_TAG=3.4-latest
 
 FROM dtcenter/${MET_BASE_REPO}:${MET_BASE_TAG}
 MAINTAINER John Halley Gotway <johnhg@ucar.edu>
@@ -24,11 +24,6 @@ ENV MET_REPO_DIR=/met/MET-${MET_GIT_NAME}
 ENV MET_GIT_URL=https://github.com/dtcenter/MET
 ENV MET_DEVELOPMENT=true
 
-#
-# Update the OS, as needed.
-#
-RUN apt update
-
 #
 # Set the working directory.
 #
@@ -48,6 +43,6 @@ RUN if [ ! -e "${MET_REPO_DIR}/configure.ac" ]; then \
     exit 1; \
   fi
 
-RUN cd ${MET_REPO_DIR} \
- && internal/scripts/docker/build_met_docker.sh
-
+RUN \
+    echo "Build MET" &&\
+    (cd ${MET_REPO_DIR} && internal/scripts/docker/build_met_docker.sh)
diff --git a/internal/scripts/docker/Dockerfile.sonarqube b/internal/scripts/docker/Dockerfile.sonarqube
@@ -1,5 +1,5 @@
 ARG MET_BASE_REPO=met-base
-ARG MET_BASE_TAG=3.5-latest
+ARG MET_BASE_TAG=3.4-latest
 
 FROM dtcenter/${MET_BASE_REPO}:${MET_BASE_TAG}
 MAINTAINER John Halley Gotway <johnhg@ucar.edu>
@@ -67,11 +67,6 @@ RUN echo "Installing SonarQube into $HOME/.sonar" \
  && unzip -o $HOME/.sonar/build-wrapper-linux-x86.zip -d $HOME/.sonar/ \
  && echo export PATH="$HOME/.sonar/build-wrapper-linux-x86:\$PATH" >> $HOME/.bashrc
 
-#
-# Update the OS, as needed.
-#
-RUN apt update
-
 #
 # Set the working directory.
 #
@@ -80,8 +75,7 @@ WORKDIR /met
 #
 # Copy MET Download and install MET.
 #
-RUN echo "Copying MET into ${MET_REPO_DIR}" \
- && mkdir -p ${MET_REPO_DIR}
+RUN echo "Copying MET into ${MET_REPO_DIR}" && mkdir -p ${MET_REPO_DIR}
 
 COPY . ${MET_REPO_DIR}
 
@@ -90,5 +84,6 @@ RUN if [ ! -e "${MET_REPO_DIR}/configure.ac" ]; then \
     exit 1; \
   fi
 
-RUN cd ${MET_REPO_DIR} \
- && internal/scripts/docker/build_met_sonarqube.sh
+RUN \
+    echo "Build MET for SonarQube" &&\
+    (cd ${MET_REPO_DIR} && internal/scripts/docker/build_met_sonarqube.sh)
diff --git a/internal/scripts/environment/development.docker b/internal/scripts/environment/development.docker
@@ -12,7 +12,7 @@ export CXXFLAGS=${CFLAGS}
 
 # Set LDFLAGS to include -rpath settings when compiling MET
 export LDFLAGS="-Wl,--disable-new-dtags"
-export LDFLAGS="${LDFLAGS} -Wl,-rpath,/usr/local/lib:/usr/lib64"
+export LDFLAGS="${LDFLAGS} -Wl,-rpath,/usr/local/lib:/usr/local/lib64:/usr/lib64"
 
 # Variables required to run MET
 export MET_TEST_INPUT=${MET_PROJ_DIR}/MET_test_data/unit_test

diff --git a/internal/test_unit/bin/unit_test.sh b/internal/test_unit/bin/unit_test.sh
@@ -40,6 +40,7 @@ UNIT_XML="unit_ascii2nc.xml \
           unit_gen_ens_prod.xml \
           unit_pcp_combine.xml \
           unit_regrid.xml \
+          unit_winds.xml \
           unit_wwmca_regrid.xml \
           unit_point_stat.xml \
           unit_stat_analysis_ps.xml \

diff --git a/internal/test_unit/xml/unit_grib_tables.xml b/internal/test_unit/xml/unit_grib_tables.xml
@@ -36,8 +36,8 @@
         <param> \
             &DATA_DIR_MODEL;/grib2/um_raw/PS.557WW_SC.U_DI.F_GP.GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20160424_CY.00_FH.000_DF.GR2 \
             &OUTPUT_DIR;/grib_tables/um_raw/PS.557WW_SC.U_DI.F_GP.GALWEM-GD_GR.C17KM_AR.GLOBAL_DD.20160424_CY.00_FH.000_DF.ps \
-            'name = "TCDC"; level = "L0";' \
-            -title "GRIB2 um_raw L0 TCDC" \
+            'name = "TCC"; level = "L0";' \
+            -title "GRIB2 um_raw L0 TCC" \
             -v 1
         </param>
         <output>

diff --git a/internal/test_unit/xml/unit_plot_data_plane.xml b/internal/test_unit/xml/unit_plot_data_plane.xml
@@ -615,7 +615,7 @@
     <param> \
       &DATA_DIR_MODEL;/wrf/wrfout_solarwind_d02_2019-08-31_12:00:00 \
       &OUTPUT_DIR;/plot_data_plane/wrf_west_east_stag.ps \
-      'name="U"; level="(0,0,*,*)";' \
+      'name="U"; level="(0,0,*,*)"; is_grid_relative=false;' \
       -title "X-wind component (staggered)" \
       -v 1
     </param>
@@ -629,7 +629,7 @@
     <param> \
       &DATA_DIR_MODEL;/wrf/wrfout_solarwind_d02_2019-08-31_12:00:00 \
       &OUTPUT_DIR;/plot_data_plane/wrf_south_north_stag.ps \
-      'name="V"; level="(0,0,*,*)";' \
+      'name="V"; level="(0,0,*,*)"; is_grid_relative=false;' \
       -title "Y-wind component (staggered)" \
       -v 1
     </param>