Changes between Version 95 and Version 96 of WRF4GTutorial2


Ignore:
Timestamp:
May 7, 2013 10:42:36 AM (9 years ago)
Author:
carlos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WRF4GTutorial2

    v95 v96  
    181181* SLURM
    182182 
    183 In order to add new resources, you need to edit `ComputingResources` section in the [wiki:WRF4Gframework4g_conf framework4g.conf] file which is located under `$WRF4G_LOCATION/etc` directory. The file has to contain one resource per line with the format:
     183In order to add new resources, you need to edit `ComputingResources` section in the [wiki:WRF4Gframework4g_conf framework4g.conf] file which is located under `$HOME/WRF4G/etc` directory. The file has to contain one resource per line with the format:
    184184
    185185{{{
     
    236236== How to add a new WRF geographical domain ==
    237237
    238 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.
     238As 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 `$HOME/WRF4G/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.
    239239
    240240First 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: