Note
Click here to download the full example code
5.2.11.3. TCRMW: Hurricane Gonzalo
model_applications/tc_and_extra_tc/TCRMW_fcstGFS_fcstOnly _gonzolo.conf
Scientific Objective
The TC-RMW tool regrids tropical cyclone model data onto a moving range-azimuth grid centered on points along the storm track. This capability replicates the NOAA Hurricane Research Division DIA-Post module.
Datasets
METplus Components
This use case utilizes the METplus TCRMW wrapper to search for the desired ADECK file and forecast files that are correspond to the track. It generates a command to run the MET tool TC-RMW if all required files are found.
METplus Workflow
TCRMW is the only tool called in this example. It processes the following 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/tc_and_extra_tc/TCRMW_fcstGFS_fcstOnly_gonzalo.conf
# TCRMW Gonzalo - METplus Configuration
# section heading for [config] variables - all items below this line and
# before the next section heading correspond to the [config] section
[config]
# List of applications to run - only TCRMW for this case
PROCESS_LIST = TCRMW
# time looping - 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
LOOP_BY = INIT
# Format of INIT_BEG and INT_END using % items
# %Y = 4 digit year, %m = 2 digit month, %d = 2 digit day, etc.
# see www.strftime.org for more information
# %Y%m%d%H expands to YYYYMMDDHH
INIT_TIME_FMT = %Y%m%d%H
# Start time for METplus run - must match INIT_TIME_FMT
INIT_BEG = 2014101312
# End time for METplus run - must match INIT_TIME_FMT
INIT_END = 2014101312
# Increment between METplus runs (in seconds if no units are specified)
# Must be >= 60 seconds
INIT_INCREMENT = 6H
# List of forecast leads to process for each run time (init or valid)
# In hours if units are not specified
# If unset, defaults to 0 (don't loop through forecast leads)
# begin_end_incr(x,y,z) expands to a list where
# x = begin, y = end (inclusive), and z = increment between each value
#LEAD_SEQ = begin_end_incr(0, 126, 6)
LEAD_SEQ = begin_end_incr(0, 24, 6)
# Order of loops to process data - Options are times, processes
# Not relevant if only one item is in the PROCESS_LIST
# times = run all wrappers in the PROCESS_LIST for a single run time, then
# increment the run time and run all wrappers again until all times have
# been evaluated.
# processes = run the first wrapper in the PROCESS_LIST for all times
# specified, then repeat for the next item in the PROCESS_LIST until all
# wrappers have been run
LOOP_ORDER = times
# Verbosity of MET output - overrides LOG_VERBOSITY for TCRMW only
LOG_TC_RMW_VERBOSITY = 3
# Location of MET config file to pass to TCRMW
# References CONFIG_DIR from the [dir] section
TC_RMW_CONFIG_FILE = {CONFIG_DIR}/TCRMWConfig_wrapped
# type of data used for input to TCRMW data dictionary
# The value set here will be used to add 'data_type = <value>;'
# If this option is removed/commented out/empty, nothing will be set
TC_RMW_INPUT_DATATYPE = GRIB2
MODEL = HCLT
# list of pressure values to be referenced by other config variables
# this is not a variable name known to METplus, but added to avoid repeating values
PRESSURE_LEVELS = "P1000","P850","P700","P500","P300","P200","P150","P100"
# List of variables to process in TCRMW
# must use BOTH_ config variables regardless if input is forecast or observation
BOTH_VAR1_NAME = PRMSL
BOTH_VAR1_LEVELS = L0
BOTH_VAR2_NAME = PRES
BOTH_VAR2_LEVELS = L0
BOTH_VAR3_NAME = TMP
BOTH_VAR3_LEVELS = {PRESSURE_LEVELS}
BOTH_VAR4_NAME = RH
BOTH_VAR4_LEVELS = {PRESSURE_LEVELS}
BOTH_VAR5_NAME = UGRD
BOTH_VAR5_LEVELS = {PRESSURE_LEVELS}
BOTH_VAR5_NAME = VGRD
BOTH_VAR5_LEVELS = {PRESSURE_LEVELS}
# The following variables set MET configuration variables of the same name,
# i.e. TC_RMW_BASIN sets basin, TC_RMW_STORM_NAME sets storm_name, etc.
TC_RMW_BASIN =
TC_RMW_STORM_ID =
TC_RMW_CYCLONE =
# Regrid options in TCRMW config file
# If these options are removed/commented out/empty, they will use
# the values from default MET config file
TC_RMW_REGRID_METHOD = BILIN
TC_RMW_REGRID_WIDTH = 2
TC_RMW_REGRID_VLD_THRESH = 0.5
TC_RMW_REGRID_SHAPE = SQUARE
# The following variables set values in the MET
# configuration file used by this example
# Leaving these values commented will use the value
# found in the default MET configuration file
#TC_RMW_INIT_INCLUDE =
#TC_RMW_VALID_BEG =
#TC_RMW_VALID_END =
#TC_RMW_VALID_INCLUDE_LIST =
#TC_RMW_VALID_EXCLUDE_LIST =
#TC_RMW_VALID_HOUR_LIST =
# Other TCRMW config file options
# If these options are removed/commented out/empty, they will use
# the values from default MET config file
#TC_RMW_N_RANGE = 100
#TC_RMW_N_AZIMUTH = 180
#TC_RMW_MAX_RANGE_KM = 1000.0
#TC_RMW_DELTA_RANGE_KM = 10.0
#TC_RMW_SCALE = 0.2
#
# DIRECTORIES
#
[dir]
# location of configuration files used by MET applications
CONFIG_DIR={PARM_BASE}/met_config
# Location of input track data directory
# for DECK data
TC_RMW_DECK_INPUT_DIR = {INPUT_BASE}/model_applications/tc_and_extra_tc/rmw/adeck
# directory containing input data files
TC_RMW_INPUT_DIR = {INPUT_BASE}/model_applications/tc_and_extra_tc/rmw/fcst
# directory to write output files
TC_RMW_OUTPUT_DIR = {OUTPUT_BASE}/model_applications/tc_and_extra_tc/TCRMW_gonzalo
[filename_templates]
# template to use to find DECK files relative to TC_RMW_DECK_INPUT_DIR
TC_RMW_DECK_TEMPLATE = gonzalo08l.{init?fmt=%Y%m%d%H}.f00-24.trak.hwrf.atcfunix.06hr
# template to use to find input files relative to TC_RMW_INPUT_DIR
TC_RMW_INPUT_TEMPLATE = gonzalo08l.subset.{init?fmt=%Y%m%d%H}.hwrfprs.core.0p02.f{lead?fmt=%3H}.grb2
# template to use write output files relative to TC_RMW_OUTPUT_DIR
TC_RMW_OUTPUT_TEMPLATE = tc_rmw_gonzal09l.{init?fmt=%Y%m%d%H}.nc
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 TCRMW MET Configuration section of the User’s Guide for more information on the environment variables used in the file below:
////////////////////////////////////////////////////////////////////////////////
//
// TC-RMW configuration file.
//
// For additional information, see the MET_BASE/config/README_TC file.
//
////////////////////////////////////////////////////////////////////////////////
// The following environment variables set the text if the corresponding
// variables at defined in the METplus config. If not, they are set to
// and empty string, which will cause MET to use the value defined in the
// default configuration file.
${METPLUS_MODEL}
${METPLUS_STORM_ID}
${METPLUS_BASIN}
${METPLUS_CYCLONE}
${METPLUS_INIT_INCLUDE}
${METPLUS_VALID_BEG}
${METPLUS_VALID_END}
${METPLUS_VALID_INCLUDE_LIST}
${METPLUS_VALID_EXCLUDE_LIST}
${METPLUS_VALID_HOUR_LIST}
${METPLUS_LEAD_LIST}
//
// May be set separately in each "field" entry
//
censor_thresh = [];
censor_val = [];
//
// Data fields
//
data = {
${METPLUS_DATA_FILE_TYPE}
${METPLUS_DATA_FIELD}
}
////////////////////////////////////////////////////////////////////////////////
//
// Regridding options
//
${METPLUS_REGRID_DICT}
//
// Range-Azimuth grid parameters
//
// The following environmnet variables set the text if the corresponding
// variables at defined in the METplus config. If not, they are set to
// and empty string, which will cause MET to use the value defined in the
// default configuration file.
${METPLUS_N_RANGE}
${METPLUS_N_AZIMUTH}
${METPLUS_MAX_RANGE_KM}
${METPLUS_DELTA_RANGE_KM}
${METPLUS_RMW_SCALE}
////////////////////////////////////////////////////////////////////////////////
//version = "V10.0";
////////////////////////////////////////////////////////////////////////////////
${METPLUS_MET_CONFIG_OVERRIDES}
Running METplus
This use case can be run two ways:
Passing in the use case configuration file then a user-specific system configuration file:
run_metplus.py -c /path/to/METplus/parm/model_applications/tc_and_extra_tc/TCRMW_fcstGFS_fcstOnly_gonzalo.conf -c /path/to/user_system.conf
Modifying the configurations in parm/metplus_config, then passing in use case configuration file:
run_metplus.py -c /path/to/METplus/parm/use_cases/model_applications/tc_and_extra_tc/TCRMW_fcstGFS_fcstOnly_gonzalo.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/tc_and_extra_tc/TCRMW_gonzalo (relative to OUTPUT_BASE) and will contain the following files:
tc_rmw_aal142016.nc
Keywords
sphinx_gallery_thumbnail_path = ‘_static/tc_and_extra_tc-TCRMW_fcstGFS_fcstOnly_gonzolo.png’
Total running time of the script: ( 0 minutes 0.000 seconds)