of all the requested trajectories at all the trajectory time steps, called rip-executionname.traj.The second is a file that contains requested diagnostic quantities along thetrajectories at all data times during the trajectory period, called rip-execution-name.diag.The .diag file is only created if diagnostic fields were requested in the PST.b. Trajectory plottingOnce the trajectories have been calculated, they can be plotted in subsequent RIPexecutions. Because the plotting of trajectories is performed with a different execution ofRIP than the trajectory calculation, the plotting run should have a different rip-executionnamethan any previous trajectory calculation runs.Trajectories are plotted by including an appropriate PSL in the PST. There are threekeywords that are necessary to plot trajectories, and several optional keywords. Thenecessary keywords are feld, ptyp, and tjfl. Keyword feld should be set to one of fivepossibilities: arrow, ribbon, swarm, gridswarm, or circle (these fields are described indetail below). Keyword ptyp should be set to either ht (for "horizontal trajectory plot") orvt (for "vertical (cross section) trajectory plot"). And keyword tjfl tells RIP whichtrajectory position file you want to access for the trajectory plot.As mentioned above, there are four different representations of trajectories, as specifiedby the feld keyword:• feld=arrow: This representation shows trajectories as curved arrows, witharrowheads drawn along each trajectory at a specified time interval. If the plot is ahorizontal trajectory plot (ptyp=ht), the width of each arrowhead is proportionalto the height of the trajectory at that time. If the plot is a vertical (cross section)trajectory plot (ptyp=vt), the width of each arrowhead is constant. The arrowheadthat corresponds to the time of the plot is boldened.• feld=ribbon: This representation shows trajectories as curved ribbons, witharrowheads drawn along each trajectory at a specified time interval. If the plot is ahorizontal trajectory plot (ptyp=ht), the width of each arrowhead, and the width ofthe ribbon, is proportional to the height of the trajectory at that time. If the plot isa vertical (cross section) trajectory plot (ptyp=vt), the width of each arrowhead(and the ribbon) is constant. The arrowhead that corresponds to the time of theplot is boldened.• feld=swarm: This representation shows a group of trajectories attached to eachother by straight lines at specified times. The trajectories are connected to eachother in the same order at each time they are plotted, so that the time evolution ofa material curve can be depicted. Swarms can be plotted either as horizontal orvertical trajectory plots (ptyp=ht or ptyp=vt).• feld=gridswarm: This is the same as swarm, except it works on the assumptiointhat part or all of the trajectories in the position file were initially arranged in arow-oriented 2-D array, or "gridswarm". The evolution of this gridswarm array isdepicted as a rectangular grid at the initial time, and as a deformed grid at otherspecified times. The gridswarm being plotted can have any orientation in 3D<strong>WRF</strong>-NMM V3: User’s Guide 7-35
space, although the means to create arbitrarily oriented gridswarms when RIP isused in trajectory calculation mode are limited. Creative use of the "3D grid oftrajectories" capability descirbed above under the description of zktraj can be usedto initialize horizontal gridswarms of arbitrary horizontal orientation (but onconstant vertical levels).• feld=circle: This representation shows the trajectories as circles located at thepositions of the trajectories at the current plotting time, in which the diameter ofthe circles is proportional to the net ascent of the trajectories (in terms of thechosen vertical coordinate) during the specified time interval. It is only availableas a horizontal trajectory plot (ptyp=ht).See “Keywords”, in Appendix A in the full RIP User’s Guide for more details on optionalkeywords that affect trajectory plots.c. Printing out trajectory positionsSometimes, you may want to examine the contents of a trajectory position file. Since it isa binary file, the trajectory position file cannot simply be printed out. However, a shortprogram is provided in the src/ directory in the RIP tar file called showtraj.f, which readsthe trajectory position file and prints out its contents in a readable form. The programshould have been compiled when you originally ran make, and when you run showtraj, itprompts you for the name of the trajectory position file to be printed out.d. Printing out diagnostics along trajectoriesAs mentioned above, if fields are specified in the PST for a trajectory calculation run,then RIP produces a .diag file that contains values of those fields along the trajectories.This file is an unformatted Fortran file, so another program is required to view thediagnostics. Among the Fortran files included in the src directory in the RIP tar file istabdiag.f which serves this purpose. It is compiled when make is run.In order to use the program, you must first set up a special input file that contains twolines. The first line should be the column headings you want to see in the table that willbe produced by tabdiag, with the entire line enclosed in single quotes. The second line isa Fortran I/O format string, also enclosed in single quotes, which determines how thediagnostic values are printed out. An example of an input file for tabdiag is included inthe RIP tar file, called tabdiag.in.Once the input file is set up, tabdiag is run as follows:tabdiag diagnostic-output-file tabdiag-input-fileThe result will be a text file with a table for each trajectory, showing the time evolutionof the diagnostic quantities. Some adjustment of the column headings and formatstatement will probably be necessary to make it look just right.<strong>WRF</strong>-NMM V3: User’s Guide 7-36
- 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 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 100 and 101: fine grid), f (forcing, how the lat
- 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