WRF-SFIRE - Revision history

Jmandel: Jmandel moved page WRF-SFIRE-historical to WRF-SFIRE over a redirect without leaving a redirect: revert move

2026-08-28T23:35:09Z

Jmandel moved page WRF-SFIRE-historical to WRF-SFIRE over a redirect without leaving a redirect: revert move

← Older revision	Revision as of 23:35, 28 August 2026
(No difference)

Jmandel at 23:26, 28 August 2026

2026-08-28T23:26:06Z

← Older revision		Revision as of 23:26, 28 August 2026
Line 1:		Line 1:
	~~{{historical}}~~
	{{users guide}}		{{users guide}}
	[[Category:WRF-SFIRE]]		[[Category:WRF-SFIRE]]

Jmandel at 22:33, 28 August 2026

2026-08-28T22:33:26Z

← Older revision		Revision as of 22:33, 28 August 2026
Line 1:		Line 1:
			{{historical}}
	{{users guide}}		{{users guide}}
	[[Category:WRF-SFIRE]]		[[Category:WRF-SFIRE]]

Jmandel: Jmandel moved page WRF-SFIRE to WRF-SFIRE-historical

2026-08-28T22:32:42Z

Jmandel moved page WRF-SFIRE to WRF-SFIRE-historical

← Older revision	Revision as of 22:32, 28 August 2026
(No difference)

Jmandel: /* Web-based run system WRFX */

2026-01-03T10:44:03Z

Web-based run system WRFX

← Older revision		Revision as of 10:44, 3 January 2026
Line 33:		Line 33:
	* Build WRF-Fire with optimization and test on several platforms (at least gfortran).		* Build WRF-Fire with optimization and test on several platforms (at least gfortran).

	==Web-based run system ~~WRFX~~==		==Web-based run system WRFx==
	This system is available at http://github.com/openwfm. It consists of the following parts:		This system is available at http://github.com/openwfm. It consists of the following parts:
	* [http://github.com/openwfm/wrfxpy wrfxpy] - Initiate and manage WRF-SFIRE simulations on a cluster. Automates data download, queuing and monitoring jobs, and postprocessing outputs into geolocated images. (Python). Intended to run on a head node of the cluster. ~~Documentation is available at http://wrfxpy.readthedocs.io~~		* [http://github.com/openwfm/wrfxpy wrfxpy] - Initiate and manage WRF-SFIRE simulations on a cluster. Automates data download, queuing and monitoring jobs, and postprocessing outputs into geolocated images. (Python). Intended to run on a head node of the cluster.
	* [http://github.com/openwfm/wrfxctrl wrfxctrl] - Map-based web interface to wrfxpy (Python and Javascript). Intended to run on a head node of the cluster. Runs its own web server.		* [http://github.com/openwfm/wrfxctrl wrfxctrl] - Map-based web interface to wrfxpy (Python and Javascript). Intended to run on a head node of the cluster. Runs its own web server.
	* [http://github.com/openwfm/wrfxweb wrfxweb] - Map-based visualization server running on a remote server. The visualizations are also available as Google Earth KML files. (Browser-based Javascript, Python utilities) Designed to run on a small cloud machine.		* [http://github.com/openwfm/wrfxweb wrfxweb] - Map-based visualization server running on a remote server. The visualizations are also available as Google Earth KML files. (Browser-based Javascript, Python utilities) Designed to run on a small cloud machine.
			See [[Running WRF-SFIRE with real data in the WRFx system]].

	==Works with==		==Works with==

Jmandel: /* Required testing */ update

2025-10-22T15:06:01Z

Required testing: update

← Older revision		Revision as of 15:06, 22 October 2025
Line 28:		Line 28:
	==Required testing==		==Required testing==

	If you change anything in the files '''~~WRFV3/~~phys/module_fr_sfire_*.F''', you must test that the changes do not break WRF-Fire, otherwise your changes will not be maintainable.		If you change anything in the files '''phys/module_fr_sfire_*.F''', you must test that the changes do not break WRF-Fire, otherwise your changes will not be maintainable.

	* Build WRF-~~Fire~~ with SM+DM parallelism with debugging, and test all 4 versions (serial, SM, DM, SM+DM) with the examples provided in '''~~WRFV3/~~test/em_fire''' and various numbers of processors. The results (the numerical values in the arrays the '''wrfrst''' files, not the files themselves) ~~must~~ be bit-identical to each other and identical to what they were before your changes. You can compare the files using the '''diffwrf''' utility, which is built as a part of the WRF compilation process, or start Matlab in '''~~WRFV3/~~test/em_fire''' (to set the path) and use the command '''ncdiff''' in Matlab.		* Build WRF-SFIRE with SM+DM parallelism with debugging, and test all 4 versions (serial, SM, DM, SM+DM) with the examples provided in '''test/em_fire''' and various numbers of processors. The results (the numerical values in the arrays the '''wrfrst''' files, not the files themselves) should be bit-identical to each other and identical to what they were before your changes. You can compare the files using the '''diffwrf''' utility, which is built as a part of the WRF compilation process, or start Matlab in '''test/em_fire''' (to set the path) and use the command '''ncdiff''' in Matlab.
	* Build WRF-Fire with optimization and test on several platforms (at least gfortran ~~and PGI~~).		* Build WRF-Fire with optimization and test on several platforms (at least gfortran).

	==Web-based run system WRFX==		==Web-based run system WRFX==

Jmandel: /* Standalone code */ updated

2025-10-22T15:03:17Z

Standalone code: updated

← Older revision		Revision as of 15:03, 22 October 2025
Line 8:		Line 8:

	* See [[How to run the standalone fire model in WRF-Fire]].		* See [[How to run the standalone fire model in WRF-Fire]].
	* The build process in '''standalone''' uses the ~~SFIRE~~ source code from the WRF file tree, namely the files '''~~WRFV3/~~phys/module_fr_sfire_.F''' except '''~~WRFV3/~~phys/module_fr_sfire_driver_wrf.F'''. There is no code duplication. Instead of WRF, the fire code is linked with the '''.F''' files in the '''standalone''' directory, which provide I/O and substitute the required subset of WRF functionality.		* The build process in '''standalone''' uses the generated source code from the WRF file tree, namely the files '''phys/module_fr_sfire_.f90''' except '''phys/module_fr_sfire_driver_wrf.f90'''. There is no code duplication. Instead of WRF, the fire code is linked with the '''.F''' files in the '''standalone''' directory, which provide I/O and substitute the required subset of WRF functionality.

	==Interface between WRF and SFIRE==		==Interface between WRF and SFIRE==

Jmandel: Category:WRF-SFIRE

2021-08-02T15:20:06Z

Category:WRF-SFIRE

← Older revision		Revision as of 15:20, 2 August 2021
Line 1:		Line 1:
	{{users guide}}		{{users guide}}
			[[Category:WRF-SFIRE]]
	The fire code in WRF-SFIRE is called SFIRE (for Spread FIRE model). It is based on the [[wikipedia:Level set method\|level set method]]. Since June 2011, we call the fire code SFIRE because of [[changes in WRF-Fire 3.3 release]]. The coupled code is called [[WRF]]-[[SFIRE]], and we reserve the designation [[WRF-Fire]] for the code in the WRF release.		The fire code in WRF-SFIRE is called SFIRE (for Spread FIRE model). It is based on the [[wikipedia:Level set method\|level set method]]. Since June 2011, we call the fire code SFIRE because of [[changes in WRF-Fire 3.3 release]]. The coupled code is called [[WRF]]-[[SFIRE]], and we reserve the designation [[WRF-Fire]] for the code in the WRF release.

Jmandel: /* Works with */

2020-07-15T04:18:25Z

Works with

← Older revision		Revision as of 04:18, 15 July 2020
Line 40:		Line 40:
	==Works with==		==Works with==

	* {{WRF-~~Fire-~~branch~~\|jm2/driver_wrf}} {{WRF-Fire-commit\|8d8ef07dd3aec14bc298e5cfc55e051274e51e42\|Aug 2 2010}}~~		* WRF-SFIRE master branch

	[[Category:WRF-Fire]]		[[Category:WRF-Fire]]
	[[Category:Software]]		[[Category:Software]]

Afarguell at 21:26, 2 July 2020

2020-07-02T21:26:22Z

← Older revision		Revision as of 21:26, 2 July 2020
Line 1:		Line 1:
			{{users guide}}
	The fire code in WRF-SFIRE is called SFIRE (for Spread FIRE model). It is based on the [[wikipedia:Level set method\|level set method]]. Since June 2011, we call the fire code SFIRE because of [[changes in WRF-Fire 3.3 release]]. The coupled code is called [[WRF]]-[[SFIRE]], and we reserve the designation [[WRF-Fire]] for the code in the WRF release.		The fire code in WRF-SFIRE is called SFIRE (for Spread FIRE model). It is based on the [[wikipedia:Level set method\|level set method]]. Since June 2011, we call the fire code SFIRE because of [[changes in WRF-Fire 3.3 release]]. The coupled code is called [[WRF]]-[[SFIRE]], and we reserve the designation [[WRF-Fire]] for the code in the WRF release.