Changes between Version 27 and Version 28 of WRF4G2.0/WRFAPP


Ignore:
Timestamp:
Dec 1, 2016 6:51:29 PM (5 years ago)
Author:
chus
Comment:

English polishing

Legend:

Unmodified
Added
Removed
Modified
  • WRF4G2.0/WRFAPP

    v27 v28  
    11= WRF configuration =
    22
    3 To use WRF model in WRF4G2, you have to configure the `app` variable in the [wiki:WRF4G2.0/Experiment experiment.wrf4g] file. By default, WRF4G2 provides a bundle with all you need to simulate an WRF experiment, configure as follows :
     3To use WRF through WRF4G2, you need to configure the `app` variable in the [wiki:WRF4G2.0/Experiment experiment.wrf4g] file. By default, WRF4G2 provides a bundle with all you need to simulate a WRF experiment, which is configured as follows :
    44
    55{{{
     
    77}}}
    88
    9 This bundle is able to be used for any x86_64 Linux system, and contains binaries, libraries and configuration files for WRF-3.4.1 build against gfortran-4.4.7, openmpi-1.4.3 and netcdf-4.1.3, which are include in the bundle too.
     9This bundle can be used on x86_64 Linux systems, and contains binaries, libraries and configuration files for WRF-3.4.1 build against gfortran-4.4.7, openmpi-1.4.3 and netcdf-4.1.3, which are included in the bundle too (hence, all in one).
    1010
    11 [[NoteBox(note, This configuration is quite usefully because you do not have to install WRF on any computing resources.)]]
     11[[NoteBox(note, This configuration is quite useful, because you do not need to ''install'' WRF on every computing resource.)]]
    1212
    13 But, if you want to use your own WRF installed on your machine or on a cluster, you have to update the `app` variable. There are several ways to configure this variable depending on your WRF configuration system. In order to clarify that, we are going to write some examples:     
     13However, if you'd like to use your own WRF, installed on your machine or on a cluster, you can do so by updating the `app` variable. There are several ways to configure this variable depending on your WRF configuration. Let's see some examples:     
    1414
    1515* Using [http://modules.sourceforge.net/ module] command:
     
    1818      wrf | command | module load wrf/4.5.1
    1919}}}
    20  
    21 [[NoteBox(note, We assume that each command is configuring other softwares such as openmpi\, netcdf and so on.)]]
    2220
    23 * Using `PATH` and `LD_LIBRARY_PATH` shell variables:
     21[[NoteBox(note, We assume that each command is configuring other pieces of software, such as openmpi\, netcdf and so on.)]]
     22
     23* Using `PATH` and `LD_LIBRARY_PATH` environment variables:
    2424{{{
    2525app = netcdf_bin | command | PATH=/home/user/netcdf-4.1.3/bin/:$PATH
    2626      netcdf_lib | command | LD_LIBRARY_PATH=/home/user/netcdf-4.1.3/lib/:$LD_LIBRARY_PATH
    2727      wrf_bin    | command | PATH=/home/user/WRF4.5.1/:$PATH
     28}}}
     29* If WRF is already configured and readily accessible (i.e. in the search path) on your system, you do not need to use the `app` variable.
    2830
    29 }}}
    30 * If WRF is already configured on your system, you do not have use `app` variable.
    31 
    32 [[NoteBox(warn, As you have probably noticed\, we did not mention anything about `WRF` and `WPS` configuration files (e.g. CAM_ABS_DATA\, CAM_AEROPT_DATA\, co2_trans\, etc). For that purpose\, it is highly recommendable to create a tree directory file configuration under [wiki:WRF4G2.0/WRF4GFiles wrf4g_files] directory per experiment.)]]
     31[[NoteBox(warn, As you might have probably noticed\, we didn't mention heavy input files required by some `WRF` configurations (e.g. CAM_ABS_DATA\, CAM_AEROPT_DATA\, co2_trans\, etc). In order to make them available for a specific WRF experiment, it is highly recommended to create a directory tree under the [wiki:WRF4G2.0/WRF4GFiles wrf4g_files] directory for that experiment.)]]