Note
Go to the end to download the full example code
MTD: Build Revision Series to Evaluate Forecast Consistency
model_applications/precipitation/MTD_fcstHRRR-TLE_FcstOnly _RevisionSeries_GRIB.conf
Scientific Objective
This use case demonstrates the use of the MTD tool to evaluate an updating forecast field and evaluate the forecast consistency. The use case looks for all forecasts valid at a given time and passes them into MTD. Objects are identified and tracked through time via the tool. The output can then be loaded into METviewer to compute the revision series and assess the consistency either of one case or many. See other HRRR-TLE use cases for a description of the Time Lagged Ensemble (TLE) field.
Datasets
Forecast dataset: HRRR-TLE forecasts in GRIB2
METplus Components
This use case runs MTD (MODE Time Domain) over multiple forecast leads.
METplus Workflow
The following tools are used for each run time:
MTD
This example loops by valid time. For each valid time it will run once, processing forecast leads 12 through 0. There is only one valid time in this example, so the following will be run:
Run times:
METplus Configuration
METplus first loads all of the configuration files found in parm/metplus_config, then it loads any configuration files passed to METplus via the command line with the -c option, i.e. -c parm/use_cases/model_applications/precipitation/MTD_fcstHRRR-TLE_FcstOnly_RevisionSeries_GRIB.conf
[config]
# Documentation for this use case can be found at
# https://metplus.readthedocs.io/en/latest/generated/model_applications/precipitation/MTD_fcstHRRR-TLE_FcstOnly_RevisionSeries_GRIB.html
# For additional information, please see the METplus Users Guide.
# https://metplus.readthedocs.io/en/latest/Users_Guide
###
# Processes to run
# https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#process-list
###
PROCESS_LIST = MTD
###
# Time Info
# LOOP_BY options are INIT, VALID, RETRO, and REALTIME
# If set to INIT or RETRO:
# INIT_TIME_FMT, INIT_BEG, INIT_END, and INIT_INCREMENT must also be set
# If set to VALID or REALTIME:
# VALID_TIME_FMT, VALID_BEG, VALID_END, and VALID_INCREMENT must also be set
# LEAD_SEQ is the list of forecast leads to process
# https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#timing-control
###
LOOP_BY = VALID
VALID_TIME_FMT = %Y%m%d%H
VALID_BEG=2018031300
VALID_END=2018031300
VALID_INCREMENT=86400
LEAD_SEQ = begin_end_incr(12, 0, -1)
###
# File I/O
# https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#directory-and-filename-template-info
###
FCST_MTD_INPUT_DIR = {INPUT_BASE}/model_applications/precipitation/PHPT
FCST_MTD_INPUT_TEMPLATE= {init?fmt=%Y%m%d}/{init?fmt=%Y%m%d}_i{init?fmt=%H}_f{lead?fmt=%3H}_HRRRTLE_PHPT.grb2
MTD_OUTPUT_DIR = {OUTPUT_BASE}/model_applications/precipitation/MTD_fcstHRRR-TLE_FcstOnly_RevisionSeries_GRIB
MTD_OUTPUT_TEMPLATE =
###
# Field Info
# https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#field-info
###
MODEL = HRRRTLE
OBTYPE = ANALYS
FCST_VAR1_NAME = APCP
FCST_VAR1_LEVELS = R001
FCST_MTD_CONV_RADIUS = 15
FCST_MTD_CONV_THRESH = >=5.0
FCST_MTD_INPUT_DATATYPE = GRIB
###
# MTD Settings
# https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#mtd
###
MTD_SINGLE_RUN = True
MTD_SINGLE_DATA_SRC = FCST
MTD_REGRID_TO_GRID = NONE
MTD_MIN_VOLUME = 2000
MET Configuration
METplus sets environment variables based on user settings in the METplus configuration file. See How METplus controls MET config file settings for more details.
YOU SHOULD NOT SET ANY OF THESE ENVIRONMENT VARIABLES YOURSELF! THEY WILL BE OVERWRITTEN BY METPLUS WHEN IT CALLS THE MET TOOLS!
If there is a setting in the MET configuration file that is currently not supported by METplus you’d like to control, please refer to: Overriding Unsupported MET config file settings
Note
See the MTD MET Configuration section of the User’s Guide for more information on the environment variables used in the file below:
////////////////////////////////////////////////////////////////////////////////
//
// MODE Time Domain configuration file.
//
// For additional information, see the MET_BASE/config/README file.
//
////////////////////////////////////////////////////////////////////////////////
//
// Output model name to be written
//
${METPLUS_MODEL}
//
// Output description to be written
//
${METPLUS_DESC}
//
// Output observation type to be written
//
${METPLUS_OBTYPE}
////////////////////////////////////////////////////////////////////////////////
//
// Verification grid
// May be set separately in each "field" entry
//
${METPLUS_REGRID_DICT}
////////////////////////////////////////////////////////////////////////////////
//
// Approximate grid resolution (km)
//
grid_res = 4;
////////////////////////////////////////////////////////////////////////////////
//
// Forecast and observation fields to be verified
//
fcst = {
${METPLUS_FCST_FILE_TYPE}
${METPLUS_FCST_FIELD}
censor_thresh = [];
censor_val = [];
conv_time_window = { beg = -1; end = 1; };
${METPLUS_FCST_CONV_RADIUS}
${METPLUS_FCST_CONV_THRESH}
}
obs = {
${METPLUS_OBS_FILE_TYPE}
${METPLUS_OBS_FIELD}
censor_thresh = [];
censor_val = [];
conv_time_window = { beg = -1; end = 1; };
${METPLUS_OBS_CONV_RADIUS}
${METPLUS_OBS_CONV_THRESH}
}
////////////////////////////////////////////////////////////////////////////////
//
// Intensity percentile value to be written
//
inten_perc_value = 99;
////////////////////////////////////////////////////////////////////////////////
//
// Throw away 3D objects with volumes smaller than this
//
${METPLUS_MIN_VOLUME}
////////////////////////////////////////////////////////////////////////////////
//
// Fuzzy engine weights
//
weight = {
space_centroid_dist = 1.0;
time_centroid_delta = 1.0;
speed_delta = 1.0;
direction_diff = 1.0;
volume_ratio = 1.0;
axis_angle_diff = 1.0;
start_time_delta = 1.0;
end_time_delta = 1.0;
}
////////////////////////////////////////////////////////////////////////////////
//
// Fuzzy engine interest functions
//
interest_function = {
space_centroid_dist = (
( 0.0, 1.0 )
( 50.0, 0.5 )
( 100.0, 0.0 )
);
time_centroid_delta = (
( -3.0, 0.0 )
( -2.0, 0.5 )
( -1.0, 0.8 )
( 0.0, 1.0 )
( 1.0, 0.8 )
( 2.0, 0.5 )
( 3.0, 0.0 )
);
speed_delta = (
( -10.0, 0.0 )
( -5.0, 0.5 )
( 0.0, 1.0 )
( 5.0, 0.5 )
( 10.0, 0.0 )
);
direction_diff = (
( 0.0, 1.0 )
( 90.0, 0.0 )
( 180.0, 0.0 )
);
volume_ratio = (
( 0.0, 0.0 )
( 0.5, 0.5 )
( 1.0, 1.0 )
( 1.5, 0.5 )
( 2.0, 0.0 )
);
axis_angle_diff = (
( 0.0, 1.0 )
( 30.0, 1.0 )
( 90.0, 0.0 )
);
start_time_delta = (
( -5.0, 0.0 )
( -3.0, 0.5 )
( 0.0, 1.0 )
( 3.0, 0.5 )
( 5.0, 0.0 )
);
end_time_delta = (
( -5.0, 0.0 )
( -3.0, 0.5 )
( 0.0, 1.0 )
( 3.0, 0.5 )
( 5.0, 0.0 )
);
} // interest functions
////////////////////////////////////////////////////////////////////////////////
//
// Total interest threshold for determining matches
//
total_interest_thresh = 0.7;
////////////////////////////////////////////////////////////////////////////////
//
// Output flags
//
nc_output = {
latlon = true;
raw = true;
object_id = true;
cluster_id = true;
}
txt_output = {
attributes_2d = true;
attributes_3d = true;
}
////////////////////////////////////////////////////////////////////////////////
${METPLUS_OUTPUT_PREFIX}
//version = "V9.0";
tmp_dir = "${MET_TMP_DIR}";
////////////////////////////////////////////////////////////////////////////////
${METPLUS_MET_CONFIG_OVERRIDES}
Running METplus
This use case can be run two ways:
Passing in MTD_fcstHRRR-TLE_FcstOnly_RevisionSeries_GRIB.conf then a user-specific system configuration file:
run_metplus.py -c /path/to/METplus/parm/use_cases/model_applications/precipitation/MTD_fcstHRRR-TLE_FcstOnly_RevisionSeries_GRIB.conf -c /path/to/user_system.conf
Modifying the configurations in parm/metplus_config, then passing in MTD_fcstHRRR-TLE_FcstOnly_RevisionSeries_GRIB.conf:
run_metplus.py -c /path/to/METplus/parm/use_cases/model_applications/precipitation/MTD_fcstHRRR-TLE_FcstOnly_RevisionSeries_GRIB.conf
The former method is recommended. Whether you add them to a user-specific configuration file or modify the metplus_config files, the following variables must be set correctly:
INPUT_BASE - Path to directory where sample data tarballs are unpacked (See Datasets section to obtain tarballs). This is not required to run METplus, but it is required to run the examples in parm/use_cases
OUTPUT_BASE - Path where METplus output will be written. This must be in a location where you have write permissions
MET_INSTALL_DIR - Path to location where MET is installed locally
Example User Configuration File:
[dir]
INPUT_BASE = /path/to/sample/input/data
OUTPUT_BASE = /path/to/output/dir
MET_INSTALL_DIR = /path/to/met-X.Y
NOTE: All of these items must be found under the [dir] section.
Expected Output
A successful run will output the following both to the screen and to the logfile:
INFO: METplus has successfully finished running.
Refer to the value set for OUTPUT_BASE to find where the output data was generated. Output for this use case will be found in model_applications/precipitation/MTD_fcstHRRR-TLE_FcstOnly_RevisionSeries_GRIB (relative to OUTPUT_BASE) and will contain the following files:
mtd_20180313_000000V_2d.txt
mtd_20180313_000000V_3d_single_simple.txt
mtd_20180313_000000V_obj.nc
Keywords
Note
MTDToolUseCase
PrecipitationAppUseCase
NOAAHMTOrgUseCase
GRIB2FileUseCase
NOAAWPCOrgUseCase
NOAAHMTOrgUseCase
NOAAHWTOrgUseCase
ConvectionAllowingModelsAppUseCase
RevisionSeriesUseCase
DiagnosticsUseCase
Navigate to the METplus Quick Search for Use Cases page to discover other similar use cases.
sphinx_gallery_thumbnail_path = ‘_static/precipitation-MTD_fcstHRRR-TLE_FcstOnly_RevisionSeries_GRIB.png’
Total running time of the script: (0 minutes 0.000 seconds)