WRF-Fire development notes
Jump to navigation
Jump to search
This page tracks activity in the WRF-Fire and related software development. All members of the fildfires communicty are welcome to get an account and edit.
Wish list
- Add your suggestions or plans here. If you want to comment on any of the items, please start a new section of the talk page and link to it here.
- Take the winds from a given distance behind the fireline, and set the distance in the namelist.
- Gradual ignition from a point or a line without limitation on the initial radius. See discussion.
- Ignition of an observed fire perimeter, with atmosphere and fuel consumption spin-up. See discussion.
- Real test problem with real fire data at both fine and coarse resolution.
- Add a canopy fire model for both passive (colocated) and running (not colocated with surface fire) canopy fire.
- Output of emissions products into WRF for visualization of smoke transport and dispersion.
- Connection of emissions products with WRF-Chem for online simulation of the evolution of smoke.
- Add fuel models & fuel modeling schemes, esp. Scott-Burgan categories.
- Support for in input data.
- Fix ignition time computation in case of adaptive time steps. See discussion.
- Convert ignition namelist variables into arrays for multiple ignitions.
- Generate input data for WFDS.
- Generate KML files for visualization in Google Earth.
In progress
- When you start on an item from the wish list, please move the item here and add a link to the branch where you work on it.
- Take the winds from a given height, and set the height in the namelist. branch jm2/wind2
- Better quadrature for fuel left
- The quadrature is done separately on 4 smaller cells per fire cell. The interpolation of time from ignition to the smaller cells should take into consideration the case when some of the nodes interpolated from are ignited and some are not. branch jm2/fuel branch vk/test
- The current scheme is second order accurate when all 4 corners of a fire mesh cell are on fire, and exact when all 4 corners are not on fire. In the case when only some of the 4 corners are on fire, the only requirements are that the transition when nodes ignite is continuous and monotonous. In that case, the scheme may not be very accurate. A better scheme would be accurate in more cases and have natural invariance properties. branch jm2/mkim last commit branch vk/test
- This affects the amount of heat output from the cell in the timesteps when the fireline crosses the cell.
- Read the topography from a file in an ideal run. branch fireflux Done, needs documentation.
- Fix/extend surface initialization in ideal cases to allow for defining surface properties like roughness, ground temperature, albedo etc., required by soil models and radiation codes. See discussion. branch adamko/sfc_init Done, needs documentation.
- Support hyperbolic vertical mesh grading in ideal run not only exponential. branch adamko/sfc_init Done, needs documentation.
- Set up fireflux test case branch jc branch fireflux
- Paper on the fire model in WRF-Fire.
- Paper on numerical methods in WRF-Fire
- Data assimilation
Done
- Move the item here when done and add a link to the contributor's last commit before the merge into master. Links to major milestone events can be also added to the timeline.
2004
- Ned Patton and Janice Coen propose WRF-Fire in a workshop paper and formulate the fundamental principles of how to combine WRF with the fire spread model from CAWFE.
2005
- Standalone fire model from CAWFE rewritten in F90 by Ned Patton received Mar 31 2005
2006
- John Michalakes writes specs for support of fire grids in WRF Feb 6 2006
2007
- Alternative implementation of fire grid in nested domains in WRF by Jon Beezley Feb 29 2007
- Jon started git repository from initial WRF+tracers code from Ned Patton Jun 6 2007
- Matlab prototype of level set method working Aug 30, 2007
- Imported a modular rewrite with a new standalone level set code, called SFIRE Sep 5 2007
- WRF+spread by level set coupled code working Nov 2 2007
- Paper with description of WRF-Fire and data assimilation posted on arXiv Dec 24 2007
- Ignition controlled from namelist Dec 24 2007
2008
- Change nodes on the fire mesh from corners to centers Feb 10 2008
- WPS support 3 Aug 2008
- MPI support Oct 23 2008
- Cleanup, delete standalone driver and the tracer code from CAWFE Nov 18 2008
- Landfire data conversion Dec 15 2008
2009
- Distributed memory (halos) Jan 7 2009
- Approved by UCD and NCAR for public release Mar 17 2009
- Set up nested ideal case May 4 2009
- WPS support for fire grid and nesting 7 May 2009
- Paper with a description of the WRF-Fire and data assimilation published in June 2009
- Add namelist.fire to define fuel categories 20 Sep 2009
- Interpolate in the computation of fuel_left locally to save stack memory Oct 10 2009
- 3D visualization in Matlab Nov 3 2009
- Visualization in VisTrails and Supercomputing 2009 Demo, Nov 15 2009
2010
- Support for WRF restart 16 Jan 2010
- Control in namelist the initial atmosphere perturbation (bubble) in ideal run, off by default. 27 Feb 2010 See discussion.
- Version 19 Feb 2010 released with WRF 3.2 Apr 2 2010
- Fetch high-resolution geogrid data automatically Apr 27 2010
- Walking line ignition (as the fireman walks igniting the fire) 23 May 2010
- Basic visualization in VAPOR. May 26 2010
- Merge git repository with WRF and WPS 3.2 Jun 12 2010 announcement
- Interpolate the terrain gradient to the fire mesh instead of differencing an interpolated terrain height. Jun 14 2010 See discussion.
- Replace includes for fire parameter arrays by a derived type. Jun 14 2010. See discussion.
- Resurrected a standalone driver for the fire code that is independent of WRF for diagnostics. 20 Jun 2010 See discussion.
- A standalone driver that is independent of WRF with I/O as WRF-compatible NetCDF files. branch jm2/driver_wrf See How to run the standalone fire model in WRF-Fire.
- Vertical interpolation of wind from log profile to 20ft 28 Aug 2010, wind reduction to midflame height 16 Sep 2010, rate of spread diagnostics 16 Sep 2010.
Back burner
- Items from the wish list that are around for a long time or may never be done should be moved here.