Difference between revisions of "WRF-Fire"

From openwfm
Jump to navigation Jump to search
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{users guide}}
+
{{historical|WRF-SFIRE user guide}}
 
{{software}}
 
{{software}}
:''We now call the fire code [[SFIRE]] because of [[changes in WRF-Fire 3.3 release]], and the coupled code is called [[WRF]] and [[SFIRE]]. We reserve the designation [[WRF-Fire]] for the code in the WRF release.''
+
: ''The code under continued development in our repository and mirrors [http://repo.or.cz/git-browser/by-commit.html?r=wrffire.git] [https://github.com/jbeezley/wrf-fire/] is called '''[[SFIRE]]''', and the coupled code is called [[WRF]] and [[SFIRE]]. We reserve the designation [[WRF-Fire]] for the [[fire code in WRF release|version released with WRF]].''
  
 
'''WRF-Fire''' combines the Weather Research and Forecasting model ([[WRF]]) with a fire code implementing a surface fire behavior model, called [[SFIRE]], based on semi-empirical formulas calculate the rate of spread of the fire line (the interface between burning and unignited fuel) based on fuel properties, wind velocities from WRF, and terrain slope.  The fire spread is implemented by the [[wikipedia:Level set method|level set method]]. The heat release from the fire line as well as post-frontal heat release feeds back into WRF dynamics, affecting the simulated weather in the vicinity of the fire.  The fire code is written in [[wikipedia:Fortran|Fortran 90]] following [http://www.mmm.ucar.edu/wrf/WG2/WRF_conventions.html WRF coding conventions]. It is integrated as a physics option, called from WRF as a subroutine. It calls WRF libraries for utilities such as I/O and communication between [[MPI]] processes. The fire code executes on a part of the domain, called a tile (in WRF nomenclature). All communication between the tiles is in the caller; thus, one time step requires multiple calls to WRF-Fire.  
 
'''WRF-Fire''' combines the Weather Research and Forecasting model ([[WRF]]) with a fire code implementing a surface fire behavior model, called [[SFIRE]], based on semi-empirical formulas calculate the rate of spread of the fire line (the interface between burning and unignited fuel) based on fuel properties, wind velocities from WRF, and terrain slope.  The fire spread is implemented by the [[wikipedia:Level set method|level set method]]. The heat release from the fire line as well as post-frontal heat release feeds back into WRF dynamics, affecting the simulated weather in the vicinity of the fire.  The fire code is written in [[wikipedia:Fortran|Fortran 90]] following [http://www.mmm.ucar.edu/wrf/WG2/WRF_conventions.html WRF coding conventions]. It is integrated as a physics option, called from WRF as a subroutine. It calls WRF libraries for utilities such as I/O and communication between [[MPI]] processes. The fire code executes on a part of the domain, called a tile (in WRF nomenclature). All communication between the tiles is in the caller; thus, one time step requires multiple calls to WRF-Fire.  
  
WRF-Fire is essentially a reimplementation of [[CAWFE]] with the weather model replaced by WRF and with the fire spread implemented by the level set method in SFIRE. The subroutines for the computation of the rate of spread and for the insertion of the heat flux to the atmosphere are taken from [[CAWFE]]. Click on the following poster for the origins and a summary of current capabilities of WRF-Fire:
+
WRF-Fire is essentially a reimplementation of [[CAWFE]] with the weather model replaced by WRF and with the fire spread implemented by the level set method in SFIRE. The subroutines for the computation of the rate of spread and for the insertion of the heat flux to the atmosphere are taken from [[CAWFE]]. Click on the following images for the origins and a summary of current capabilities of WRF-Fire:
  
[[Image:Agu-poster-8mp.gif|400px]]
+
[[Image:Agu-poster-8mp.gif|400px]] [[Image:Coupled-wrf-fire-moisture-chem.png|400px]]
  
 
==Distribution==
 
==Distribution==
Line 13: Line 13:
 
WRF-Fire is public domain software, [http://github.com/jbeezley/wrf-fire/blob/master/license.txt released] under the [http://www.mmm.ucar.edu/wrf/users/public.html WRF public domain notice and disclaimer].
 
WRF-Fire is public domain software, [http://github.com/jbeezley/wrf-fire/blob/master/license.txt released] under the [http://www.mmm.ucar.edu/wrf/users/public.html WRF public domain notice and disclaimer].
  
===Development version===
+
The development version is called [[SFIRE]]; further information and links to downloads are in the [[Coupled WRF and SFIRE model user's guide|Users' Guide]]. We'll be happy to consider [[WRF-Fire development notes#Wish list|additional features]]. A restricted version is [[Fire_code_in_WRF_release|available in WRF releases]].
 
 
See [[How to get WRF-Fire]] and [[How to run WRF-Fire]] for installation instructions for the development version, which contains the latest features and bug fixes. The development version is called [[SFIRE]]. It is submitted for WRF release from time to time.  We'll be happy to consider [[WRF-Fire development notes#Wish list|additional features]] but '''you need to get the development version if you want any changes sooner than in a year or two or support directly from us'''. We are making the development version publicly available in hope that it will be useful; the code has been changing quite rapidly, with important features and an occasional bug fix added between WRF releases. The [http://github.com/jbeezley/wrf-fire/tree/master head of the master branch] should contain tested stable code at any time. The development version and [http://openwfm.org this site] also contain a number of additional tools and guides for visualization, diagnostics, and running the software; see the [[list of WRF-Fire pages]].
 
 
 
===WRF release version===
 
 
 
WRF-Fire is included in WRF since version 3.2, released on April 2, 2010, maintained and supported by by NCAR as a part of WRF. It is available at the [http://www.mmm.ucar.edu/wrf/users/download/get_source.html WRF download page]. See the [http://www.mmm.ucar.edu/wrf/users/fire/wrf-fire.html NCAR WRF-Fire page] for further information.
 
 
 
The WRF-Fire module code in WRF version 3.3, released in April 2011, contains a subset of the features of SFIRE. It is based the development version as of November 2010, with some [[Changes in WRF-Fire 3.3 release|further changes made at NCAR]].
 
  
 
==Contact==
 
==Contact==
Line 53: Line 45:
 
Questions and suggestions can be sent to the maling list at http://mailman.ucar.edu/mailman/listinfo/wrf-fire. Please subscribe to this list for further support, announcements, questions, and discussions.
 
Questions and suggestions can be sent to the maling list at http://mailman.ucar.edu/mailman/listinfo/wrf-fire. Please subscribe to this list for further support, announcements, questions, and discussions.
  
===Email support for the development version===
+
===Email support for SFIRE===
  
Questions regarding the development version (from the git repository) can be sent the the list above, or email the [[WRF-Fire#Contact|developers]] directly. When you write us, please:
+
When you write us, please:
  
* Make sure you test the issue first on the code exactly as you have received it from the git repository as described in [[How to get WRF-Fire]]
+
* Make sure you test the issue first on the code exactly as you have received it from the repository as described in [[How to get WRF-Fire]]
** <code>git diff</code> should return no output
+
** <code>git diff</code> should return no output, meaning that you have not modified any files
** please verify that you are on the latest commit on the master branch from the repository
+
** Send us the output of the command <code>git log | head -3 </code> to identify the version
 +
** Verify that you are on the latest commit on the master branch from the repository
 
* Recompile the code from scratch after typing <code>clean -a</code> first
 
* Recompile the code from scratch after typing <code>clean -a</code> first
* Send us the first line of the output of the command <code>git log</code> to identify the version
+
* Send us sufficient information to identify and reproduce the problem if needed (output of wrf compilation, namelist.input, output from the run, wrfinput file for a small test problem)
* Send us sufficient information to identify and reproduce the problem if needed (output of wrf compilation, namelist.input, output from the run)
 
  
===Email support for code in WRF release===
+
===Email support for [[Fire code in WRF release|code in WRF release]]===
  
 
The version of WRF-Fire in the WRF download is supported by NCAR. Please contact wrfhelp@ucar.edu with any questions regarding the version of WRF-Fire in the [http://wrf-model.org WRF release].
 
The version of WRF-Fire in the WRF download is supported by NCAR. Please contact wrfhelp@ucar.edu with any questions regarding the version of WRF-Fire in the [http://wrf-model.org WRF release].

Latest revision as of 06:53, 17 July 2020

This is an archived historical WRF-Fire/WRF-SFIRE page. Please go to WRF-SFIRE user guide for the current software version.
This is a page with basic information about a software. Please see Template for creating software pages for what should be here.
The code under continued development in our repository and mirrors [1] [2] is called SFIRE, and the coupled code is called WRF and SFIRE. We reserve the designation WRF-Fire for the version released with WRF.

WRF-Fire combines the Weather Research and Forecasting model (WRF) with a fire code implementing a surface fire behavior model, called SFIRE, based on semi-empirical formulas calculate the rate of spread of the fire line (the interface between burning and unignited fuel) based on fuel properties, wind velocities from WRF, and terrain slope. The fire spread is implemented by the level set method. The heat release from the fire line as well as post-frontal heat release feeds back into WRF dynamics, affecting the simulated weather in the vicinity of the fire. The fire code is written in Fortran 90 following WRF coding conventions. It is integrated as a physics option, called from WRF as a subroutine. It calls WRF libraries for utilities such as I/O and communication between MPI processes. The fire code executes on a part of the domain, called a tile (in WRF nomenclature). All communication between the tiles is in the caller; thus, one time step requires multiple calls to WRF-Fire.

WRF-Fire is essentially a reimplementation of CAWFE with the weather model replaced by WRF and with the fire spread implemented by the level set method in SFIRE. The subroutines for the computation of the rate of spread and for the insertion of the heat flux to the atmosphere are taken from CAWFE. Click on the following images for the origins and a summary of current capabilities of WRF-Fire:

Agu-poster-8mp.gif Coupled-wrf-fire-moisture-chem.png

Distribution

WRF-Fire is public domain software, released under the WRF public domain notice and disclaimer.

The development version is called SFIRE; further information and links to downloads are in the Users' Guide. We'll be happy to consider additional features. A restricted version is available in WRF releases.

Contact

  • Janice Coen (WRF release version), Jonathan Beezley or Jan Mandel (development version)

File format

All input, output, and restart files (with the complete model state) are in NetCDF format.

Programming language and environments

Fortran 90 with CPP preprocessor. Part of the WRF code is generated by C programs from a description in the registry.

Documentation

Technical description

User's guides

Support

Mailing list

Questions and suggestions can be sent to the maling list at http://mailman.ucar.edu/mailman/listinfo/wrf-fire. Please subscribe to this list for further support, announcements, questions, and discussions.

Email support for SFIRE

When you write us, please:

  • Make sure you test the issue first on the code exactly as you have received it from the repository as described in How to get WRF-Fire
    • git diff should return no output, meaning that you have not modified any files
    • Send us the output of the command git log | head -3 to identify the version
    • Verify that you are on the latest commit on the master branch from the repository
  • Recompile the code from scratch after typing clean -a first
  • Send us sufficient information to identify and reproduce the problem if needed (output of wrf compilation, namelist.input, output from the run, wrfinput file for a small test problem)

Email support for code in WRF release

The version of WRF-Fire in the WRF download is supported by NCAR. Please contact wrfhelp@ucar.edu with any questions regarding the version of WRF-Fire in the WRF release.

Wiki

We welcome contributions and discussion on the pages of this wiki. Please see the Main Page for How to get an account.

Publications

See WRF-Fire publications.

Contributors

  • Janice Coen (NCAR) developed the physics components of the fire model in CAWFE (Coen (2005) and Clark et al. (2004)), in particular the fire spread rate and the heat flux insertion modules, which were adopted into WRF-Fire with no substantial changes, and has been refining the fuel and spread rate models.
  • Ned Patton (NCAR) ported the fire code from (Clark et al., 2004) and interfaced it with WRF (Patton and Coen, 2004).
  • Minjeong Kim and Jan Mandel (University of Colorado Denver) have identified a version of the level set metod suitable for fire spread, and developed a prototype Matlab code.
  • Jan Mandel (University of Colorado Denver) has been developing the level set code and the overall fire module software structure.
  • John Michalakes (formerly NCAR, now NREL) modified WRF to support refined grids (submesh) for the fire code.
  • Jonathan Beezley (University of Colorado Denver) has further modified WRF to support the fire software, provided the software engineering infrastructure, has set up and maintains the git repository, maintains synchronization with WRF changes, and has been developing the modified version of WPS for WRF with the fire model to enable the use of real data.
  • Volodymyr Kondratenko (University of Colorado Denver) has improved memory handing in the computation of remaining fuel.
  • Adam Kochanski (University of Utah) has contributed variable atmospheric bubble initialization and suggested the walking line ignition. He is currently leading the validation effort.
  • Kara Yedinak (Washington State University) has improved in fire initialization. See discussion

See also

External links