WRF ARW User's Guide - MMM - UCAR

MODEL
wrfout_d01_2000-01-24_12:00:00
The time stamp on the file name is always the first time the output file is written. It is
always good to check the times written to the output file by typing:
ncdump -v Times wrfout_d01_2000-01-24_12:00:00
You may have other wrfout files depending on the namelist options (how often you split
the output files and so on using namelist option frames_per_outfile).You may
also create restart files if you have restart frequency (restart_interval in the
namelist.input file) set within your total integration length. The restart file should have
names like
wrfrst_d_
The time stamp on a restart file is the time that restart file is valid at.
For DM (distributed memory) parallel systems, some form of mpirun command will be
needed to run the executables. For example, on a Linux cluster, the command to run MPI
code and using 4 processors may look like:
mpirun -np 4 ./real.exe
mpirun -np 4 ./wrf.exe
On some IBMs, the command may be:
poe ./real.exe
poe ./wrf.exe
for a batch job, and
poe ./real.exe -rmpool 1 -procs 4
poe ./wrf.exe -rmpool 1 -procs 4
for an interactive run. (Interactive MPI job is not an option on NCAR IBM bluefire)
c. Restart Run
A restart run allows a user to extend a run to a longer simulation period. It is effectively a
continuous run made of several shorter runs. Hence the results at the end of one or more
restart runs should be identical to a single run without any restart.
In order to do a restart run, one must first create restart file. This is done by setting
namelist variable restart_interval (unit is in minutes) to be equal to or less than
the simulation length in the first model run, as specified by run_* variables or
start_* and end_* times. When the model reaches the time to write a restart file, a
WRF-ARW V3: User’s Guide 5-10