WRF ARW User's Guide - MMM - UCAR

POST-PROCESSING
mkdir postprd
mkdir parm
3. Copy the default WPPV3/parm/wrf_cntrl.parm to your working. Edit the
wrf_cntrl.parm file to reflect the fields and levels you want wrfpost to output.
4. Copy the script (WPPV3/scripts/run_wrfpost*) of your choice to the postprd/.
5. Edit the run script as outlined below.
Once these directories are set up and the edits outlined above are completed, the scripts
can be run interactively from the postprd directory by simply typing the script name on
the command line.
Overview of the WPP run scripts
Note: It is recommended that the user refer to the script while reading this overview.
1. Set up environmental variables:
TOP_DIR: top level directory for source codes (WPPV3 and WRFV3)
DOMAINPATH: top level directory of WRF model run
Note: The scripts are configured such that wrfpost expects the WRF history files
(wrfout* files) to be in subdirectory wrfprd, the wrf_cntrl.parm file to be in the
subdirectory parm and the postprocessor working directory to be a subdirectory called
postprd under DOMAINPATH.
2. Specify dynamic core being run (“ARW” for the WRF-ARW model)
3. Specify the forecast cycles to be post-processed:
startdate: YYYYMMDDHH of forecast cycle
fhr: first forecast hour
lastfhr: last forecast hour
incrementhr: increment (in hours) between forecast files
4. Define the location of the post-processor executables.
5. Link the microphysical table ${WRFPATH}/run/ETAMP_DATA and the control file
../parm/wrf_control.parm to the working directory.
6. Set up how many domains will be post-processed:
For runs with a single domain, use “for domain d01”.
For runs with multiple domains, use “for domain d01 d02 .. dnn”
WRF-ARW V3: User’s Guide 9-42