Note
Go to the end to download the full example code
ExtractTiles: MTD Input
met_tool_wrapper/ExtractTiles/ExtractTiles_mtd.conf
Scientific Objective
Read a MODE Time Domain (MTD) output file and use the centroid latitude and longitude values of the MTD cluster object pairs to create a cutout of forecast and observation data valid at each time.
Datasets
METplus Components
This use case utilizes the METplus ExtractTiles wrapper to search for files that are valid at a given run time and generate a command to run the MET tool regrid_data_plane if all required files are found.
METplus Workflow
ExtractTiles is the only tool called in this example. It processes the following run time:
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/met_tool_wrapper/ExtractTiles/ExtractTiles_mtd.conf
[config]
# Documentation for this use case can be found at
# https://metplus.readthedocs.io/en/latest/generated/met_tool_wrapper/ExtractTiles/ExtractTiles_mtd.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 = ExtractTiles
###
# 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 = INIT
INIT_TIME_FMT = %Y%m%d%H
INIT_BEG = 2005080700
INIT_END = 2005080700
INIT_INCREMENT = 6H
LEAD_SEQ = 6H
###
# File I/O
# https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#directory-and-filename-template-info
###
EXTRACT_TILES_MTD_INPUT_DIR = {INPUT_BASE}/met_test/new/mtd
EXTRACT_TILES_MTD_INPUT_TEMPLATE = mtd_WRF_APCP_vs_MC_PCP_APCP_03_A03_{valid?fmt=%Y%m%d_%H%M%S}V_2d.txt
FCST_EXTRACT_TILES_INPUT_DIR = {INPUT_BASE}/met_test/data/sample_fcst
FCST_EXTRACT_TILES_INPUT_TEMPLATE = {init?fmt=%Y%m%d%H}/wrfprs_ruc13_{lead?fmt=%2H}.tm00_G212
OBS_EXTRACT_TILES_INPUT_DIR = {INPUT_BASE}/met_test/new
OBS_EXTRACT_TILES_INPUT_TEMPLATE = ST2ml{valid?fmt=%Y%m%d%H}_A03h.nc
EXTRACT_TILES_OUTPUT_DIR = {OUTPUT_BASE}/met_tool_wrapper/ExtractTiles
FCST_EXTRACT_TILES_OUTPUT_TEMPLATE = {init?fmt=%Y%m%d_%H}/FCST_TILE_F{lead?fmt=%3H}_wrfprs_{init?fmt=%Y%m%d}_{init?fmt=%H}00_{lead?fmt=%3H}.nc
OBS_EXTRACT_TILES_OUTPUT_TEMPLATE = {init?fmt=%Y%m%d_%H}/OBS_TILE_F{lead?fmt=%3H}_wrfprs_{valid?fmt=%Y%m%d}_{valid?fmt=%H}00_000.nc
EXTRACT_TILES_SKIP_IF_OUTPUT_EXISTS = no
###
# Field Info
# https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#field-info
###
FCST_VAR1_NAME = APCP
FCST_VAR1_LEVELS = A03
OBS_VAR1_NAME = APCP_03
OBS_VAR1_LEVELS = "(*,*)"
###
# ExtractTiles Settings
# https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#extracttiles
###
EXTRACT_TILES_NLAT = 60
EXTRACT_TILES_NLON = 60
EXTRACT_TILES_DLAT = 0.5
EXTRACT_TILES_DLON = 0.5
EXTRACT_TILES_LON_ADJ = 15
EXTRACT_TILES_LAT_ADJ = 15
MET Configuration
None. RegridDataPlane does not use configuration files.
Running METplus
This use case can be run two ways:
Passing in ExtractTiles_mtd.conf then a user-specific system configuration file:
run_metplus.py -c /path/to/METplus/parm/use_cases/met_tool_wrapper/ExtractTiles/ExtractTiles_mtd.conf -c /path/to/user_system.conf
Modifying the configurations in parm/metplus_config, then passing in ExtractTiles_mtd.conf:
run_metplus.py -c /path/to/METplus/parm/use_cases/met_tool_wrapper/ExtractTiles/ExtractTiles_mtd.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 met_tool_wrapper/ExtractTiles/20050807_00 (relative to OUTPUT_BASE) and will contain the following files:
FCST_TILE_F006_wrfprs_20050807_0000_006.nc
FCST_TILE_F009_wrfprs_20050807_0000_009.nc
FCST_TILE_F012_wrfprs_20050807_0000_012.nc
OBS_TILE_F006_wrfprs_20050807_0600_000.nc
OBS_TILE_F009_wrfprs_20050807_0900_000.nc
OBS_TILE_F012_wrfprs_20050807_1200_000.nc
Keywords
Note
RegridDataPlaneToolUseCase
GRIB2FileUseCase
Navigate to the METplus Quick Search for Use Cases page to discover other similar use cases.
sphinx_gallery_thumbnail_path = ‘_static/met_tool_wrapper-ExtractTiles.png’
Total running time of the script: (0 minutes 0.000 seconds)