Why a preprocessor?

Before the WRF Preprocessor System (WPS) runs, input data files need to be in a specific format, so ungrib.exe is able to parse them. Specifically, files in GRIB format are needed. Furthermore, to be able to run WRF, there are some mandatory fields that must be presented in the input files. Some of these are not always available in the driving model data we want to use, such as soil temperature and moisture content. In addition, it is needed these variables with the frequency that WRF is going to use to update its boundary data (usually 6 hours).

Thus, in many cases input data available in some online server need to be preprocessed. This process could be carried out offline, transforming the whole downloaded dataset before using it. However, integrating it in the WRF4G workflow enables the user to download and preprocess the input data locally in any of the grid nodes. In WRF4G the program or script that performs this process is called preprocessor.

preprocessors in WRF4G

As mentioned, the preprocessor is called before the WPS in each chunk. It must be an executable file that can be written in any language, and accepts 3 arguments. These are the initial date, the end date (as YYYY-mm-dd HH:MM:SS) and the path to the input data (extdata_path). After preprocessing, the preprocessor must copy the properly formatted input data to a folder called WPS/grbdata.

WRF4G provides some preprocessors as examples. These are located under $WRF4G_DIR/repository/apps/preprocessor directory. In order to create preprocessors, they have to be located in the wrf4g_files/bin directory of the specific experiment.

Last modified 7 years ago Last modified on Jun 25, 2015 10:22:32 AM