Changes between Version 9 and Version 10 of WRF4G2.0/Geogrid


Ignore:
Timestamp:
Oct 7, 2015 12:21:35 PM (7 years ago)
Author:
carlos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WRF4G2.0/Geogrid

    v9 v10  
    55First of all, WPS binaries are needed. If you don't have them in your system, you will need to build them from source. Instructions for doing this are available too in the [http://www.mmm.ucar.edu/wrf/OnLineTutorial/Compile/index.html WRF-ARW online tutorial]. Once you have the binaries, you will need to prepare a `namelist.wps` file defining your requirements for the domain (e.g. size, location, resolution, etc.).
    66
    7 Here we are going to explain the variables that usually need modification and we will show an example for 2-nesting domain:
     7Variables that usually need modification and we will show an example for 2-nesting domain:
    88
    9 * parent_id --> List of integers specifying the domain number of the nest’s parent (One per domain).   
     9* '''parent_id:''' List of integers specifying the domain number of the nest’s parent (One per domain).   
    1010 
    1111 ||   parent_id=1,1
    12 * parent_grid_ratio  --> It is a list of integers specifying for each domain the nesting ratio relative to the domain's parent.   
     12* '''parent_grid_ratio:''' It is a list of integers specifying for each domain the nesting ratio relative to the domain's parent.   
    1313
    1414 ||   parent_grid_ratio=1,3
    15 * i_parent_start, j_parent_start --> Coordinates of the lower left corner of the nest in the domain's parent.   
     15* ''''i_parent_start, j_parent_start:''' Coordinates of the lower left corner of the nest in the domain's parent.   
    1616
    1717 ||   i_parent_start=1,16, j_parent_start=1,34
    18 * e_we --> It represents the nest’s full west-east dimension. For nested domains, e_we must be one greater than an integer multiple of the nest's parent_grid_ratio   
     18* '''e_we:''' It represents the nest’s full west-east dimension. For nested domains, e_we must be one greater than an integer multiple of the nest's parent_grid_ratio   
    1919
    2020 ||   e_we=60,82
    21 * e_sn --> It represents the nest’s full south-north dimension. For nested domains, e_sn must be one greater than an integer multiple of the nest's parent_grid_ratio. 
     21* '''e_sn:''' It represents the nest’s full south-north dimension. For nested domains, e_sn must be one greater than an integer multiple of the nest's parent_grid_ratio. 
    2222
    2323 ||   e_sn=81,112
    24 * dx --> Number specifying the grid distance in the x-direction where the map scale factor is 1. It should be in meters for the 'polar', 'lambert', and 'mercator' projection, and in degrees longitude for the 'lat-lon' projection. 
     24* '''dx:''' Number specifying the grid distance in the x-direction where the map scale factor is 1. It should be in meters for the 'polar', 'lambert', and 'mercator' projection, and in degrees longitude for the 'lat-lon' projection. 
    2525
    2626 ||   dx=0.15
    27 * dy --> Number specifying the grid distance in the y-direction where the map scale factor is 1. As stated for dx, this value should be in meters for the 'polar', 'lambert', and 'mercator' projection, but for the 'lat-lon' projection, it should be in degrees latitude.   
     27* '''dy:''' Number specifying the grid distance in the y-direction where the map scale factor is 1. As stated for dx, this value should be in meters for the 'polar', 'lambert', and 'mercator' projection, but for the 'lat-lon' projection, it should be in degrees latitude.   
    2828
    2929 ||   dy=0.15
    30 * map_proj --> Name of the projections available 'lambert', 'polar', 'mercator', and 'lat-lon'   
     30* '''map_proj:''' Name of the projections available 'lambert', 'polar', 'mercator', and 'lat-lon'   
    3131
    3232 ||   map_proj='lat-lon'
    33 * ref_x, ref_y --> Location of the latitude and longitude of reference for the domain   
     33* '''ref_x, ref_y:''' Location of the latitude and longitude of reference for the domain   
    3434
    3535 ||   ref_x=1, ref_y=1
    36 * ref_lat, ref_lon --> Reference coordinates of the domain.   
     36* '''ref_lat, ref_lon:''' Reference coordinates of the domain.   
    3737
    3838 ||   ref_lat=-8.85, ref_lon=24.1
    39 * pole_lat -->  For the latitude-longitude projection, it represents the latitude of the North Pole with respect to the computational latitude-longitude grid in which -90.0° latitude is at the bottom of a global domain and 90.0° latitude is at the top.
    40 * pole_lon --> For the latitude-longitude projection, it represents the longitude of the North Pole with respect to the computational latitude-longitude grid in which 180.0° longitude is at the center.
    41 * stand_lon --> A real value specifying the longitude that is parallel with the y-axis in the Lambert conformal and polar stereographic projections. For the regular latitude-longitude projection, this value gives the rotation about the earth's geographic poles.
    42 * geog_data_path --> Path to the directory where the geographical data directories may be found.   
     39* '''pole_lat:'''  For the latitude-longitude projection, it represents the latitude of the North Pole with respect to the computational latitude-longitude grid in which -90.0° latitude is at the bottom of a global domain and 90.0° latitude is at the top.
     40* '''pole_lon:''' For the latitude-longitude projection, it represents the longitude of the North Pole with respect to the computational latitude-longitude grid in which 180.0° longitude is at the center.
     41* '''stand_lon:''' A real value specifying the longitude that is parallel with the y-axis in the Lambert conformal and polar stereographic projections. For the regular latitude-longitude projection, this value gives the rotation about the earth's geographic poles.
     42* '''geog_data_path:''' Path to the directory where the geographical data directories may be found.   
    4343
    4444 ||   geog_data_path='$HOME/WRF/wps_topo/geog'
    4545
    4646Also, the GEOGRID.TBL file is needed to be present into a folder called geogrid, in the same place where geogrid is going to be executed. The final structure is the following:
    47 
    4847{{{
    49 #!sh
    50 [user@mycomputer~]$ tree
    51 .
    5248|-- geogrid
    5349|   `-- GEOGRID.TBL
     
    5551}}}
    5652
    57 
    58 Provided the namelist and the GEOGRID.TBL, the next step is to execute geogrid.exe. This will generate a netCDF file called geo_em_d01.nc, which contains all the fixed fields that WRF needs to run with that domain.
    59 
     53Provided the namelist and the `GEOGRID.TBL`, the next step is to execute `geogrid.exe`. This will generate a netCDF file called `geo_em_d01.nc`, which contains all the fixed fields that WRF needs to run with that domain.
    6054{{{
    6155#!sh