# Changes between Version 76 and Version 77 of WRF4GTutorial2

Ignore:
Timestamp:
Oct 17, 2012 6:22:49 PM (10 years ago)
Comment:

--

### Legend:

Unmodified
 v76 As stated before, a step of the WRF Preprocessor System (WPS), called geogrid, is not included in the WRF4G workflow. Thus, the user must deal with it by hand, or using another tool, such as [http://www.wrfportal.org/ WRF portal]. Geogrid does the task of extracting the fixed fields (orography, land use data, etc.) that WRF needs to run at a given resolution and region. In the WRF4G framework, the output of geogrid is known as the "domain" of an experiment. Inside the original WRF4G tarball there are two example domains, Santander_50km and wrfuc, located in $WRF4G_LOCATION/repository/domains. Here we are going to see how a new one can be added. It's important to note that there exists an [http://www.mmm.ucar.edu/wrf/OnLineTutorial/index.htm excellent on-line tutorial] for running WPS and WRF by hand. Users of WRF4G are encouraged to work through this tutorial before start running with WRF4G itself. This framework is intended to make life much easier for WRF users, but knowledge about WRF itself is needed to deal with common errors and issues, and to carry on a correct interpretation of the results. First 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 (size, location, resolution, etc.) Also, 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. Provided the namelist and the GEOGRID.TBL, the next step in 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. First 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 (size, location, resolution, etc.) Also, 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: {{{ [markel@ui01]$ tree . |-- geogrid |   -- GEOGRID.TBL -- namelist.wps }}} Provided the namelist and the GEOGRID.TBL, the next step in 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. {{{ \${PATH_TO_GREOGRID}/geogrid.exe >& geogrid.log markel@ui01:~/ls geo_em.d01.nc  geogrid  namelist.wps  geogrid.log }}} The next and final step is to copy the geo_em and the namelist.wps files to a folder with the name chosen for the domain (e.g. Europe_15k). This folder must be located in the path specified by the variable WRF4G_DOMAINPATH in [wiki:WRF4Gresources_wrf4g resources.wrf4g]. After following these steps, the new domain is available for using it in any WRF4G experiment, just setting the variable domain equal to the name of the folder in [wiki:WRF4Gexperiment_wrf4g experiments.wrf4g] (the folder where we located geo_em_d01.nc and namelist.wps). == How to use wrf4g_kill command ==