How to run WRF-SFIRE with real data

Running WRF-Fire with real data is a process very similar to running WRF with real data for weather simulations. The WRF users page has many documents and tutorials outlining this process. The purpose of this page is to provide a tutorial for using real data with WRF-Fire starting from scratch. We begin with a quick outline of the steps involved including links to the output of each step. The user can use these linked files to start from any step or to verify their own results. Due to platform and compiler differences your output might differ slightly from those provided.

Outline

1. Obtain WRF-Fire source code.
2. Compile target em_real.
3. Compile WPS.
4. Configure your domain.
5. Download geogrid datasets.
6. Convert fire data to geogrid format.
7. Run the geogrid executable.
8. Download atmospheric data.
9. Run the ungrib executable.
10. Run the metrid executable.
11. Run real.exe and wrf.exe.

Configuring the domain

The physical domain is configured in the geogrid section of namelist.wps in the WPS directory. In this section, you should define the geographic projection with map_proj, truelat1, truelat2, and stand_lon. Available projections include 'lambert', 'polar', 'mercator', and 'lat-lon'. The lower left corner of the domain is located at ref_lon longitude and ref_lat latitude. The computational grid is defined by e_we/e_sn, the number of (staggered) grid points in the west-east/south-north direction, and the grid resolution is defined by dx and dy in meters. We also specify a path to where we will put the static dataset that geogrid will read from, and we specify the highest resolution (30 arc minutes) that this data is released in.

&geogrid
 e_we              =  43,
 e_sn              =  43,
 geog_data_res     = '30s',
 dx = 60,
 dy = 60,
 map_proj  = 'lambert',
 ref_lat   =  39.70537,
 ref_lon   = -107.2907,
 truelat1  =  39.338,
 truelat2  =  39.338,
 stand_lon = -106.807,
 geog_data_path = '../../wrfdata/geog'
/

The share section of the WPS namelist defines the fire subgrid refinement in subgrid_ratio_x and subgrid_ratio_y. This means that the fire grid will be a 10 time refined grid at a resolution of 6 meters by 6 meters. The start_date and end_data parameters specify the time window that the simulation will be run in. Atmospheric data must be available at both temporal boundaries. The interval_seconds parameter tells WPS the number of seconds between each atmospheric dataset. For our example, we will be using the NARR dataset which is released daily every three hours or 10,800 seconds.

&share
 wrf_core = 'ARW',
 max_dom = 1,
 start_date = '2005-08-28_12:00:00',
 end_date   = '2005-08-28_15:00:00',
 interval_seconds = 10800,
 io_form_geogrid = 2,
 subgrid_ratio_x = 10,
 subgrid_ratio_y = 10,
/

Obtaining data for geogrid

First you must download and uncompress the standard geogrid input data. This is a 429 MB compressed tarball that uncompresses to around 11 GB. It contains all of the static data that geogrid needs for a standard weather simulation; however, for a WRF-Fire simulation we need to fill in two additional fields that are too big to release in a single download for the whole globe. We first need to determine the approximate latitude and longitude bounds for our domain.

We know the coordinates in the lower left corner from the ref_lon and ref_lat parameters of the namelist.