Per #3006, make -format ioda or -format python error out, but add uni…

…t tests demonstrating those errors. Also note this in the user's guide.

.github/workflows/testing.yml

@@ -301,7 +301,7 @@ jobs:
       matrix:
         include:
           - jobid: 'job1'
-            tests: 'point_stat pair_stat stat_analysis_ps'
+            tests: 'point_stat stat_analysis_ps pair_stat'
           - jobid: 'job2'
             tests: 'grid_stat stat_analysis_gs'
           - jobid: 'job3'

docs/Users_Guide/pair-stat.rst

@@ -21,6 +21,11 @@ The statistical methods and measures computed by the Pair-Stat tool are describe
 Practical Information
 =====================
 
+.. note::
+
+  Only **-format mpr** is supported at this time. Support for **-format python** and **-format ioda** will be added in future development cycles.
+
+
 The Pair-Stat tool is used to perform verification of a gridded model field using point observations. The gridded model field to be verified must be in one of the supported file formats. The point observations must be formatted as the NetCDF output of the point reformatting tools described in :numref:`reformat_point`. The Pair-Stat tool provides the capability of interpolating the gridded forecast data to the observation points using a variety of methods as described in :numref:`matching-methods`. The Pair-Stat tool computes a number of continuous statistics on the matched pair data as well as discrete statistics once the matched pair data have been thresholded.
 
 If no matched pairs are found for a particular verification task, a report listing counts for reasons why the observations were not used is written to the log output at the default verbosity level of 2. If matched pairs are found, this report is written at verbosity level 3. Inspecting these rejection reason counts is the first step in determining why Pair-Stat found no matched pairs. The order of the log messages matches the order in which the processing logic is applied. Start from the last log message and work your way up, considering each of the non-zero rejection reason counts. Verbosity level 9 prints a very detailed explanation about why each observation is used or skipped for each verification task.

internal/test_unit/bin/unit_test.sh

@@ -45,8 +45,8 @@ UNIT_XML_ORG="unit_ascii2nc.xml \
           unit_pcp_combine.xml \
           unit_wwmca_regrid.xml \
           unit_point_stat.xml \
-          unit_pair_stat.xml \
           unit_stat_analysis_ps.xml \
+          unit_pair_stat.xml \
           unit_duplicate_flag.xml \
           unit_obs_summary.xml \
           unit_grid_stat.xml \