|
Back to Example List
Running
MM5 with Overlapping Nests
- Nests MAY NOT overlap in TERRAIN
- Nest MAY overlap in an MM5 run - this DOES NOT involve running
TERRAIN with overlapping nests.
- To run MM5 with nests as in the figure below
- Run TERRAIN creating DOMAIN1 ONLY
- Set up configure.user and mm5.deck as below

configure.user
MAXNES = 4
MIX
= 88
MJX = 97
make clean
make
mm5.deck
LEVIDN
= 0, 1, 1, 2, 1, 1, 1, 1, 1, 1,
; level of nest for each domain
NUMNC = 1, 1, 1, 3, 1, 1, 1, 1, 1, 1,
; ID of mother domain for each nest
NESTIX = 35, 49, 43, 88, 46, 46,
46, 46, 46, 46, ; domain size i
NESTJX = 41, 46, 76, 97, 61, 61, 61,
61, 61, 61, ; domain size j
NESTI = 1, 12, 6, 6,
1, 1, 1, 1, 1, 1,
; start location i
NESTJ = 1, 6, 10,
38,
1, 1, 1, 1, 1, 1,
; start location i
IOVERW = 1, 0, 0, 0,
0, 0, 0, 0, 0, 0, ;
overwrite nest input
| |
IOVERW is set
to 0 for domains 2,3,4
Thus TERRAIN_DOMAIN2/3/4 is not needed as model input.
As all information for domains 2-4 will be interpolated
from MMINPUT_DOMAIN1, overlapping nests are allowed. |
| |
There is very little advantage in running
the model with this configuration.
|
|