Nested Model Run: 2-way, with 2 Input Files

Both domains must have a wrfinput_d0x file that begins at the same time as the start of the model run.

At the WRF model step, one can choose how the nested domain data is used:

i. Use all the meteorological and static data from nested domains as input
In this case all static and meteorological data for the nest(s) are obtained from the nest's input file.
**This is the recommended way to make a nested run.

ii. Use only the static data for nested domains as input.
In this case only static data for the nest(s) are obtained from the nest's input file. Meteorological data are interpolated from the coarse grid.
**This option should only be used if the nest will be started at a later time.

 

Program flow:
NOTE: (A) WPS can be set up to generate multiple met_em.d02.* files for the nested domain, but only the initial time is required. (B) Up to this point the steps required for both case "i" and "ii" above are identical. (C) The nested domain will always gets its boundary conditions from the coarse domain, so no wrfbdy_d02 will be created.

 

For this case study we are going to add a nest to the Single Domain Hurricane Matthew Case. As we have already unpacked GRIB date (ungrib.exe) for this case, we only need to run geogrid.exe and metgrid.exe to generate the additional input data.
 

Let's set up the model domains