25.12.2012 Views

WRF ARW User's Guide - MMM - UCAR

WRF ARW User's Guide - MMM - UCAR

WRF ARW User's Guide - MMM - UCAR

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

&share<br />

wrf_core = '<strong>ARW</strong>',<br />

max_dom = 2,<br />

start_date = '2008-03-24_12:00:00','2008-03-24_12:00:00',<br />

end_date = '2008-03-24_18:00:00','2008-03-24_12:00:00',<br />

interval_seconds = 21600,<br />

io_form_geogrid = 2<br />

/<br />

&geogrid<br />

parent_id = 1, 1,<br />

parent_grid_ratio = 1, 3,<br />

i_parent_start = 1, 31,<br />

j_parent_start = 1, 17,<br />

s_we = 1, 1,<br />

e_we = 74, 112,<br />

s_sn = 1, 1,<br />

e_sn = 61, 97,<br />

geog_data_res = '10m','2m',<br />

dx = 30000,<br />

dy = 30000,<br />

map_proj = 'lambert',<br />

ref_lat = 34.83,<br />

ref_lon = -81.03,<br />

truelat1 = 30.0,<br />

truelat2 = 60.0,<br />

stand_lon = -98.<br />

geog_data_path = '/mmm/users/wrfhelp/WPS_GEOG/'<br />

/<br />

The namelist variables that are affected by nests are shown in the (partial) namelist<br />

records above. The example shows namelist variables for a two-domain run (the coarse<br />

domain plus a single nest), and the effect on the namelist variables generalize to multiple<br />

nests in the obvious way: rather than specifying lists of two values, lists of N values must<br />

be specified, where N is the total number of model grids.<br />

WPS<br />

In the above example, the first change to the “share” namelist record is to the max_dom<br />

variable, which must be set to the total number of nests in the simulation, including the<br />

coarse domain. Having determined the number of nests, all of the other affected namelist<br />

variables must be given a list of N values, one for each grid. The only other change to the<br />

“share” namelist record is to the starting and ending times. Here, a starting and ending<br />

time must be given for each nest, with the restriction that a nest cannot begin before its<br />

parent domain or end after its parent domain; also, it is suggested that nests be given<br />

starting and ending times that are identical to the desired starting times of the nest when<br />

running WPS. This is because the nests get their lateral boundary conditions from their<br />

parent domain, and thus, only the initial time for a nest needs to be processed by WPS,<br />

except when grid nudging, also called analysis nudging, is used in <strong>WRF</strong>. It is important<br />

to note that, when running <strong>WRF</strong>, the actual starting and ending times for all nests must be<br />

given in the <strong>WRF</strong> namelist.input file.<br />

The remaining changes are to the “geogrid” namelist record. In this record, the parent of<br />

each nest must be specified with the parent_id variable. Every nest must be a child of<br />

exactly one other nest, with the coarse domain being its own parent. Related to the<br />

identity of a nest's parent is the nest refinement ratio with respect to its parent, which is<br />

<strong>WRF</strong>-<strong>ARW</strong> V3: User’s <strong>Guide</strong> 3-19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!