fine grid), f (forcing, how the lateral boundaries are processed), and s (smoothing). Aswith other entries, the best coarse of action is to find a field nearly identical to the onethat you are inserting into the Registry file, and copy that line. The user needs to makethe determination whether or not it is reasonable to smooth the field in the area of thecoarse grid, where the fine-grid feeds back to the coarse grid. Variables that are definedover land and water, non-masked, are usually smoothed. The lateral boundary forcing isprimarily for dynamics variables, and is ignored in this overview. For non-masked fields(such as wind, temperature, pressure), the downward interpolation (controlled by d) andthe feedback (controlled by u) use default routines. Variables that are land fields (such assoil temperature TSLB) or water fields (such as sea ice XICE) have special interpolators,as shown in the examples below (again, interleaved for readability):# state real TSLB iljstate real XICE ij misc 1 Zmisc 1 -i02rhd=(interp_mask_land_field:lu_index)u=(copy_fcnm)i0124rhd=(interp_mask_water_field:lu_index)u=(copy_fcnm) "TSLB" "SOIL TEMPERATURE" "K""SEAICE" "SEA ICE FLAG" ""Note that the d and u entries in the section are followed by an “=” then aparenthesis enclosed subroutine, and a colon separated list of additional variables to passto the routine. It is recommended that users follow the existing pattern: du for nonmaskedvariables, and the above syntax for the existing interpolators for maskedvariables.Registry RconfigThe Registry file is the location where the run-time options to configure the model aredefined. Every variable in the <strong>WRF</strong> namelist is described by an entry in the Registryfile. The default value for each of the namelist variables is as assigned in the Registry.The standard form for the entry for two namelist variables is given (broken across linesand interleaved):# rconfig integer run_daysrconfig integer start_year<strong>WRF</strong>-NMM V3: User’s Guide 6-9
namelist,time_control 1 0namelist,time_control max_domains 1993The keyword for this type of entry in the Registry file is rconfig (run-timeconfiguration). As with the other model fields (such as state and i1), the columnassigns the Fortran kind of the variable: integer, real, or logical. The name of thevariable in the <strong>WRF</strong> namelist is given in the column, and is part of the deriveddata type structure as are the state fields. There are a number of Fortran namelist recordsin the file namelist.input. Each namelist variable is a member of one of the specificnamelist records. The previous example shows that run_days and start_year are bothmembers of the time_control record. The column refers to thedimensionality of the namelist variable (number of entries). For most variables, the column has two eligible values, either 1 (signifying that the scalar entry isvalid for all domains) or max_domains (signifying that the variable is an array, with avalue specified for each domain). Finally, a default value is given. This permits anamelist entry to be removed from the namelist.input file if the default value isacceptable.The registry program constructs two subroutines for each namelist variable, one toretrieve the value of the namelist variable, and the other to set the value. For an integervariable named my_nml_var, the following code snippet provides an example of the easyaccess to the namelist variables.INTEGER :: my_nml_var, dom_idCALL nl_get_my_nml_var ( dom_id , my_nml_var )The subroutine takes two arguments. The first is the input integer domain identifier (forexample, 1 for the most coarse grid, 2 for the second domain), and the second argumentis the returned value of the namelist variable. The associated subroutine to set thenamelist variable, with the same argument list, is nl_set_my_nml_var. For namelistvariables that are scalars, the grid identifier should be set to 1.The rconfig line may also be used to define variables that are convenient to pass aroundin the model, usually part of a derived configuration (such as the number of microphysicsspecies associated with a physics package). In this case, the column entry isderived. This variable does not appear in the namelist, but is accessible with the samegenerated nl_set and nl_get subroutines.Registry Halo, Period, and XposeThe distributed memory, inter-processor communications are fully described in theRegistry file. An entry in the Registry constructs a code segment which is included (withcpp) in the source code. Following is an example of a halo communication (split acrosstwo lines and interleaved for readability).<strong>WRF</strong>-NMM V3: User’s Guide 6-10
- Page 1 and 2:
ForewordUser's Guide for the NMM Co
- Page 3 and 4:
• WPP Directory Structure 7-3•
- Page 5 and 6:
The WRF modeling system software is
- Page 7 and 8:
WRF-NMM FLOW CHARTTerrestrialDataMo
- Page 9 and 10:
Vendor Hardware OS CompilerCray X1
- Page 11 and 12:
If all of these executables are def
- Page 13 and 14:
Once the tar file is obtained, gunz
- Page 15 and 16:
HWRF is set, then (3) will be autom
- Page 17 and 18:
In addition to these three links, a
- Page 19 and 20:
• Real-data simulations• Non-hy
- Page 21 and 22:
k. Morrison double-moment scheme (1
- Page 23 and 24:
g. GFDL surface layer (88): (This s
- Page 25 and 26:
Other physics optionsa. gwd_opt: Gr
- Page 27 and 28:
to the convergence of meridians app
- Page 29 and 30:
Variable NamesValue(Example)Descrip
- Page 31 and 32:
Variable NamesValue(Example)Descrip
- Page 33 and 34:
Variable NamesValue(Example)Descrip
- Page 35 and 36:
Variable NamesValue(Example)Descrip
- Page 37 and 38:
Variable NamesValue(Example)Descrip
- Page 39 and 40:
mpirun.lsf wrf.exeand for interacti
- Page 41 and 42:
The boundary conditions for the nes
- Page 43 and 44:
Examples:1. One nest and one level
- Page 45 and 46:
ottom_top_stag = 28 ;soil_layers_st
- Page 47 and 48:
float HLENSW(Time, south_north, wes
- Page 49 and 50: float HBOTS(Time, south_north, west
- Page 51 and 52: operational mesoscale Eta model. J.
- Page 53 and 54: Mlawer, E. J., S. J. Taubman, P. D.
- Page 55 and 56: NCEP WRF Postprocessor (WPP)WPP Int
- Page 57 and 58: ./configureYou will be given a list
- Page 59 and 60: equested output field. If the pre-r
- Page 61 and 62: RAINCV SNOW HBOTRAINNCVSNOWCNote: F
- Page 63 and 64: Running WPPFour scripts for running
- Page 65 and 66: i. As the grid id of a pre-defined
- Page 67 and 68: The GrADS package is available from
- Page 69 and 70: Height on pressure surface HEIGHT O
- Page 71 and 72: MELTPrecipitation type (4 types) -
- Page 73 and 74: Press at tropopause PRESS AT TROPOP
- Page 75 and 76: RIP4RIP IntroductionRIP (which stan
- Page 77 and 78: A successful compilation will resul
- Page 79 and 80: iinterp = 0v v v v vH V H V h h h h
- Page 81 and 82: espectively, of the centered domain
- Page 83 and 84: This can be either 'h' (for hours),
- Page 85: eal variable expect values that are
- Page 88 and 89: of all the requested trajectories a
- Page 90 and 91: Creating Vis5D Dataset with RIPVis5
- Page 92 and 93: User’s Guide for the NMM Core of
- Page 94 and 95: Configuration: The configure script
- Page 96 and 97: This program reads the contents of
- Page 98 and 99: Period - Describes communications f
- Page 102 and 103: # halo HALO_NMM_K dyn_nmm8:q2;24:t
- Page 104 and 105: (http://www.mmm.ucar.edu/wrf/WG2/Ti
- Page 106 and 107: User's Guide for the NMM Core of th
- Page 108 and 109: 2. Make sure the files listed below
- Page 110 and 111: User's Guide for the NMM Core of th
- Page 112 and 113: Program geogridThe purpose of geogr
- Page 114 and 115: 1. Define a model coarse domain and
- Page 116 and 117: to GEOGRID.TBL in the geogrid direc
- Page 118 and 119: the GRIB data were downloaded to th
- Page 120 and 121: By this point, there is generally n
- Page 122 and 123: two nests are defined to have the s
- Page 124 and 125: Note: For the WRF-NMM the variables
- Page 126 and 127: simulations may use a constant SST
- Page 128 and 129: entire simulation domain, and data
- Page 130 and 131: that lists the variables and attrib
- Page 132 and 133: http://www.ecmwf.int/products/data/
- Page 134 and 135: intermediate formats (metgrid/src/r
- Page 136 and 137: GRIB1| Level| From | To |Param| Typ
- Page 138 and 139: corresponding source grid point. Gi
- Page 140 and 141: tile_x = 1200tile_y = 1200tile_z =
- Page 142 and 143: 1. PARENT_ID : A list of MAX_DOM in
- Page 144 and 145: V -DX- H| / |DY dx DY| / |H - DX- V
- Page 146 and 147: intermediate files if ungrib is to
- Page 148 and 149: the index and data tiles for the da
- Page 150 and 151:
1. PROJECTION : A character string
- Page 152 and 153:
25. SCALE_FACTOR : A real value tha
- Page 154 and 155:
10. INTERP_MASK : The name of the f
- Page 156 and 157:
1. four_pt : Four-point bi-linear i
- Page 158 and 159:
8. search : Breadth-first search in
- Page 160 and 161:
19 Mixed Tundra20 Barren TundraTabl
- Page 162 and 163:
LU_INDEX:units = "category" ;LU_IND
- Page 164 and 165:
netcdf met_em.d01.2009-01-05_12:00:
- Page 166:
}:ISOILWATER = 14 ;:grid_id = 1 ;:p