5.1.14.8. PCPCombine: Bucket Interval Use Case

met_tool_wrapper/PCPCombine/PCPCombine_bucket.conf

Scientific Objective

Build a 15 hour precipitation accumulation field from varying accumulation fields.

Datasets

Forecast: GFS precipitation accumulation
Location: All of the input data required for this use case can be found in the met_test sample data tarball. Click here to the METplus releases page and download sample data for the appropriate release: https://github.com/dtcenter/METplus/releases
This tarball should be unpacked into the directory that you will set the value of INPUT_BASE. See Running METplus section for more information.
Data Source: GFS

METplus Components

This use case utilizes the METplus PCPCombine wrapper to search for files to build the desired accumulation for a given run time using a filename template and a list of available input accumulations. If enough files meeting the criteria are found to build the output accumulation, it will generate a command to run PCPCombine to combine the data.

METplus Workflow

PCPCombine is the only tool called in this example. It processes the following run times:

Valid: 2012-04-09_00Z
Forecast lead: 15 hour

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/PCPCombine/PCPCombine_bucket.conf

# PCPCombine Bucket Interval Example

[config]
# time looping - options are INIT, VALID, RETRO, and REALTIME
LOOP_BY = INIT

# Format of INIT_BEG and INIT_END
INIT_TIME_FMT = %Y%m%d%H

# Start time for METplus run
INIT_BEG = 2012040900

# End time for METplus run
INIT_END = 2012040900

# Increment between METplus runs in seconds. Must be >= 60
INIT_INCREMENT = 86400

# list of forecast leads to process
LEAD_SEQ = 15H

# Options are times, processes
# times = run all items in the PROCESS_LIST for a single initialization
# time, then repeat until all times have been evaluated.
# processes = run each item in the PROCESS_LIST for all times
#   specified, then repeat for the next item in the PROCESS_LIST.
LOOP_ORDER = times

# List of applications to run
PROCESS_LIST = PcpCombine

# verbosity of PCPCombine MET output
#LOG_PCP_COMBINE_VERBOSITY = 2

#FCST_VAR1_NAME = APCP
#FCST_VAR1_LEVELS = 15M

FCST_PCP_COMBINE_MAX_FORECAST = 2d

# run PCPCombine on forecast data
FCST_PCP_COMBINE_RUN = True

# mode of PCPCombine to use (SUM, ADD, SUBTRACT)
FCST_PCP_COMBINE_METHOD = ADD

# list of variables to compare
#FCST_VAR1_NAME = A001500

# description of data to be processed
# used in output file path
MODEL = GFS
#OBTYPE = ANLYS

# Forecast data description variables
#FCST_PCP_COMBINE_INPUT_DATATYPE = GRIB
FCST_IS_PROB = false

FCST_PCP_COMBINE_BUCKET_INTERVAL = 6H
FCST_PCP_COMBINE_INPUT_ACCUMS = {lead}

FCST_PCP_COMBINE_OUTPUT_ACCUM = 15H
FCST_PCP_COMBINE_OUTPUT_NAME = APCP

[dir]
# input and output data directories
FCST_PCP_COMBINE_INPUT_DIR = {INPUT_BASE}/met_test/new/gfs
FCST_PCP_COMBINE_OUTPUT_DIR = {OUTPUT_BASE}/met_tool_wrapper/PCPCombine/PCPCombine_bucket

[filename_templates]
# format of filenames
# GFS
FCST_PCP_COMBINE_INPUT_TEMPLATE = gfs_{init?fmt=%Y%m%d%H}_F{lead?fmt=%3H}.grib
FCST_PCP_COMBINE_OUTPUT_TEMPLATE = gfs_{valid?fmt=%Y%m%d%H}_A{level?fmt=%3H}.nc

MET Configuration

None. PCPCombine does not use configuration files.

Running METplus

This use case can be run two ways:

  1. Passing in PCPCombine_bucket.conf then a user-specific system configuration file:

    run_metplus.py -c /path/to/METplus/parm/use_cases/met_tool_wrapper/PCPCombine/PCPCombine_bucket.conf -c /path/to/user_system.conf
    
  2. Modifying the configurations in parm/metplus_config, then passing in PCPCombine_bucket.conf:

    run_metplus.py -c /path/to/METplus/parm/use_cases/met_tool_wrapper/PCPCombine/PCPCombine_bucket.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/PCPCombine/PCPCombine_bucket (relative to OUTPUT_BASE) and will contain the following files:

  • gfs_2012040915_A015.nc

Keywords

sphinx_gallery_thumbnail_path = ‘_static/met_tool_wrapper-PCPCombine.png’

Total running time of the script: ( 0 minutes 0.000 seconds)

Gallery generated by Sphinx-Gallery