Update develop-ref after #2203 and #2205

data/config/Ascii2NcConfig_default

@@ -25,7 +25,7 @@ time_summary = {
   width = 600;
   grib_code = [ 11, 204, 211 ];
   obs_var   = [];
-  type = [ "min", "max", "range", "mean", "stdev", "median", "p80" ];
+  type = [ "min", "max", "range", "mean", "stdev", "median", "p80", "sum" ];
   vld_freq = 0;
   vld_thresh = 0.0;
 }

data/config/IODA2NCConfig_default

@@ -117,7 +117,7 @@ time_summary = {
   width = 600;
   grib_code = [];
   obs_var   = [ "TMP", "WDIR", "RH" ];
-  type = [ "min", "max", "range", "mean", "stdev", "median", "p80" ];
+  type = [ "min", "max", "range", "mean", "stdev", "median", "p80", "sum" ];
   vld_freq = 0;
   vld_thresh = 0.0;
 }

data/config/Madis2NcConfig_default

@@ -25,7 +25,7 @@ time_summary = {
   width = 600;
   grib_code = [ 11, 204, 211 ];
   obs_var   = [];
-  type = [ "min", "max", "range", "mean", "stdev", "median", "p80" ];
+  type = [ "min", "max", "range", "mean", "stdev", "median", "p80", "sum" ];
   vld_freq = 0;
   vld_thresh = 0.0;
 }

data/config/PB2NCConfig_default

@@ -148,7 +148,7 @@ time_summary = {
   width = 600;
   grib_code = [];
   obs_var   = [ "TMP", "WDIR", "RH" ];
-  type = [ "min", "max", "range", "mean", "stdev", "median", "p80" ];
+  type = [ "min", "max", "range", "mean", "stdev", "median", "p80", "sum" ];
   vld_freq = 0;
   vld_thresh = 0.0;
 }

docs/Users_Guide/appendixA.rst

@@ -147,9 +147,10 @@ Q. How do I choose a time slice in a NetCDF file?
 
 A.
 When processing NetCDF files, the level information needs to be
-specified to tell MET which 2D slice of data to use. There is
-currently no way to explicitly define which time slice to use
-other than selecting the time index.
+specified to tell MET which 2D slice of data to use. The index is selected from
+a value when it starts with "@" for vertical level (pressure or height)
+and time. The actual time, @YYYYMMDD_HHMM, is allowed instead of selecting
+the time index.
 
 Let's use plot_data_plane as an example:
 
@@ -160,6 +161,11 @@ Let's use plot_data_plane as an example:
 		obs.ps \ 
 		'name="APCP"; level="(5,*,*)";'
 
+		plot_data_plane \
+		gtg_obs_forecast.20130730.i00.f00.nc \
+		altitude_20000.ps \
+		'name = "edr"; level = "(@20130730_0000,@20000,*,*)";'
+
 Assuming that the first array is the time, this will select the 6-th
 time slice of the APCP data and plot it since these indices are 0-based.
 

docs/Users_Guide/config_options.rst

@@ -204,7 +204,7 @@ convenient to use them. For example, when applying the same configuration to
 the output from multiple models, consider defining the model name as an
 environment variable which the controlling script sets prior to verifying the
 output of each model. Setting MODEL to that environment variable enables you
-to use one configuration file rather than maintianing many very similar ones.
+to use one configuration file rather than maintaining many very similar ones.
 
 An error in the syntax of a configuration file will result in an error from the
 MET tool stating the location of the parsing error.
@@ -991,7 +991,8 @@ File-format specific settings for the "field" entry:
 
       * (i,...,j,*,*) for a single field, where i,...,j specifies fixed
         dimension values and *,* specifies the two dimensions for the
-        gridded field. For example:
+        gridded field. @ specifies the vertical level value or time value
+        instead of offset, (i,...,@NNN,*,*). For example:
 
       .. code-block:: none
 
@@ -1006,6 +1007,17 @@ File-format specific settings for the "field" entry:
              }
            ];
 
+        field = [
+             {
+               name       = "QVAPOR";
+               level      = "(@20220601_1200,@850,*,*)";
+             },
+             {
+               name       = "TMP_P850_ENS_MEAN";
+               level      = [ "(*,*)" ];
+             }
+           ];
+
   * Python (using PYTHON_NUMPY or PYTHON_XARRAY):
 
     * The Python interface for MET is described in Appendix F of the MET
@@ -2236,10 +2248,17 @@ one hour prior:
 
   width = { beg = -3600; end = 0; }
 
-The summaries will only be calculated for the specified GRIB codes.
-The supported summaries are "min" (minimum), "max" (maximum), "range",
-"mean", "stdev" (standard deviation), "median" and "p##" (percentile, with
-the desired percentile value specified in place of ##).
+The summaries will only be calculated for the specified GRIB codes
+or observation variable ("obs_var") names.
+
+When determining which observations fall within a time interval, data for the
+beginning timestamp is included while data for the ending timestamp is excluded.
+Users may need to adjust the "beg" and "end" settings in the "width" dictionary
+to include the desired observations in each time interval.
+
+The supported time summaries are "min" (minimum), "max" (maximum), "range",
+"mean", "stdev" (standard deviation), "median", "sum", and "p##" (percentile,
+with the desired percentile value specified in place of ##).
 
 The "vld_freq" and "vld_thresh" options may be used to require that a certain
 ratio of observations must be present and contain valid data within the time
@@ -2250,6 +2269,9 @@ setting "vld_thresh = 0.5" requires that at least 15 of the 30 expected
 observations be present and valid for a summary value to be written. The
 default "vld_thresh = 0.0" setting will skip over this logic.
 
+When using the "sum" option, users should specify "vld_thresh = 1.0" to avoid
+missing data values from affecting the resulting sum value.
+
 The variable names are saved to NetCDF file if they are given instead of
 grib_codes which are not available for non GRIB input. The "obs_var" option
 was added and works like "grib_code" option (string value VS. int value).