Talk:WRF-Fire/WRF-SFIRE history - Revision history

Jmandel: Jmandel moved page Talk:WRF-Fire history to Talk:WRF-Fire/WRF-SFIRE history

2026-07-20T22:08:36Z

Jmandel moved page Talk:WRF-Fire history to Talk:WRF-Fire/WRF-SFIRE history

← Older revision	Revision as of 22:08, 20 July 2026
(No difference)

Jmandel: Jmandel moved page Talk:WRF-Fire development notes to Talk:WRF-Fire history

2026-07-20T21:55:13Z

Jmandel moved page Talk:WRF-Fire development notes to Talk:WRF-Fire history

← Older revision	Revision as of 21:55, 20 July 2026
(No difference)

Jmandel: /* Moisture model */

2012-04-22T17:02:54Z

Moisture model

← Older revision		Revision as of 17:02, 22 April 2012
Line 152:		Line 152:
	Moisture model runs on the atmospheric grid, independently for one or more of fuel classes. Each class can have its own model or parameters of the model. Currently, a fine fuels model calibrated on the Canadian fire danger rating system is implemented similar to the above. The moisture contents in the fuel classes is combined in different proportions for different fuel categories, and interpolated to the fire grid. If the moisture model does not run, the interpolation takes the moisture contents in the fuel classes from wrfinput. [[User:Jmandel\|Jmandel]] 23:23, 28 February 2012 (UTC)		Moisture model runs on the atmospheric grid, independently for one or more of fuel classes. Each class can have its own model or parameters of the model. Currently, a fine fuels model calibrated on the Canadian fire danger rating system is implemented similar to the above. The moisture contents in the fuel classes is combined in different proportions for different fuel categories, and interpolated to the fire grid. If the moisture model does not run, the interpolation takes the moisture contents in the fuel classes from wrfinput. [[User:Jmandel\|Jmandel]] 23:23, 28 February 2012 (UTC)

	{{WRF-Fire-commit\|763044cd62eaaec5b92c14462f6e25bdddf4d643\|Done}}, the differential equations (though not the interpolation scheme nor the physical equations) are in Section 7 of the [http://~~ccm~~.~~ucdenver.edu~~/~~reports~~/~~rep309~~.~~pdf~~ ICCS 2012 paper]. [[User:Jmandel\|Jmandel]] 02:31, 11 March 2012 (UTC)		{{WRF-Fire-commit\|763044cd62eaaec5b92c14462f6e25bdddf4d643\|Done}}, the differential equations (though not the interpolation scheme nor the physical equations) are in Section 7 of the [http://arxiv.org/abs/1203.2230 ICCS 2012 paper]. [[User:Jmandel\|Jmandel]] 02:31, 11 March 2012 (UTC)

	== Restart from '''wrfout''' ==		== Restart from '''wrfout''' ==

Jmandel: /* Moisture model */

2012-03-11T02:31:49Z

Moisture model

← Older revision		Revision as of 02:31, 11 March 2012
Line 151:		Line 151:

	Moisture model runs on the atmospheric grid, independently for one or more of fuel classes. Each class can have its own model or parameters of the model. Currently, a fine fuels model calibrated on the Canadian fire danger rating system is implemented similar to the above. The moisture contents in the fuel classes is combined in different proportions for different fuel categories, and interpolated to the fire grid. If the moisture model does not run, the interpolation takes the moisture contents in the fuel classes from wrfinput. [[User:Jmandel\|Jmandel]] 23:23, 28 February 2012 (UTC)		Moisture model runs on the atmospheric grid, independently for one or more of fuel classes. Each class can have its own model or parameters of the model. Currently, a fine fuels model calibrated on the Canadian fire danger rating system is implemented similar to the above. The moisture contents in the fuel classes is combined in different proportions for different fuel categories, and interpolated to the fire grid. If the moisture model does not run, the interpolation takes the moisture contents in the fuel classes from wrfinput. [[User:Jmandel\|Jmandel]] 23:23, 28 February 2012 (UTC)

			{{WRF-Fire-commit\|763044cd62eaaec5b92c14462f6e25bdddf4d643\|Done}}, the differential equations (though not the interpolation scheme nor the physical equations) are in Section 7 of the [http://ccm.ucdenver.edu/reports/rep309.pdf ICCS 2012 paper]. [[User:Jmandel\|Jmandel]] 02:31, 11 March 2012 (UTC)

	== Restart from '''wrfout''' ==		== Restart from '''wrfout''' ==

Jmandel: /* Moisture model */

2012-02-28T23:24:06Z

Moisture model

← Older revision		Revision as of 23:24, 28 February 2012
Line 150:		Line 150:
	[[User:Jmandel\|Jmandel]] 02:51, 11 September 2011 (UTC)		[[User:Jmandel\|Jmandel]] 02:51, 11 September 2011 (UTC)

	Moisture model runs on the atmospheric grid, independently ~~in on~~ or more of fuel classes. Each class can have its own model. Currently, a fine fuels model calibrated on the Canadian fire danger rating system is implemented. The moisture contents in the fuel classes is combined ~~with~~ different proportions for different fuel categories, and interpolated to the fire grid. If the moisture model does not run, the interpolation takes the moisture contents in the fuel classes from wrfinput. [[User:Jmandel\|Jmandel]] 23:23, 28 February 2012 (UTC)		Moisture model runs on the atmospheric grid, independently for one or more of fuel classes. Each class can have its own model or parameters of the model. Currently, a fine fuels model calibrated on the Canadian fire danger rating system is implemented similar to the above. The moisture contents in the fuel classes is combined in different proportions for different fuel categories, and interpolated to the fire grid. If the moisture model does not run, the interpolation takes the moisture contents in the fuel classes from wrfinput. [[User:Jmandel\|Jmandel]] 23:23, 28 February 2012 (UTC)

	== Restart from '''wrfout''' ==		== Restart from '''wrfout''' ==

Jmandel: /* Moisture model */

2012-02-28T23:23:14Z

Moisture model

← Older revision		Revision as of 23:23, 28 February 2012
Line 149:		Line 149:
	# Fire can take moisture from direct coupling, or from an earlier run and interpolate in time. Perhaps add several moisture fields with different names to wrfinput/wrfout. Avoid fire mesh sized arrays with a 3rd dimension because of 32bit limits.		# Fire can take moisture from direct coupling, or from an earlier run and interpolate in time. Perhaps add several moisture fields with different names to wrfinput/wrfout. Avoid fire mesh sized arrays with a 3rd dimension because of 32bit limits.
	[[User:Jmandel\|Jmandel]] 02:51, 11 September 2011 (UTC)		[[User:Jmandel\|Jmandel]] 02:51, 11 September 2011 (UTC)

			Moisture model runs on the atmospheric grid, independently in on or more of fuel classes. Each class can have its own model. Currently, a fine fuels model calibrated on the Canadian fire danger rating system is implemented. The moisture contents in the fuel classes is combined with different proportions for different fuel categories, and interpolated to the fire grid. If the moisture model does not run, the interpolation takes the moisture contents in the fuel classes from wrfinput. [[User:Jmandel\|Jmandel]] 23:23, 28 February 2012 (UTC)

	== Restart from '''wrfout''' ==		== Restart from '''wrfout''' ==

Jmandel: /* Fire spin-up */ fix link

2012-01-04T04:56:39Z

Fire spin-up: fix link

← Older revision		Revision as of 04:56, 4 January 2012
Line 106:		Line 106:

	Implemented {{WRF-Fire-commit\|716cf59c2313e3bb483a57db02211d17b8d095f7\|March 24, 2011}}, for now in ideal run only. See		Implemented {{WRF-Fire-commit\|716cf59c2313e3bb483a57db02211d17b8d095f7\|March 24, 2011}}, for now in ideal run only. See
	{{ccm\|Jan_Mandel/Blog#March_24:_WRF-Fire:_Perimeter_ignition\|more info and pictures}}. [[User:Jmandel\|Jmandel]] 05:06, 25 March 2011 (UTC)		{{ccm\|Jan_Mandel/Blog/2011_Feb_Mar#March_24:_WRF-Fire:_Perimeter_ignition\|more info and pictures}}. [[User:Jmandel\|Jmandel]] 05:06, 25 March 2011 (UTC)

	== {{wp\|Google Earth}} ==		== {{wp\|Google Earth}} ==

Jmandel: /* Standalone driver */ update {{WRF-Fire-commit| links

2011-11-02T09:30:27Z

Standalone driver: update {{WRF-Fire-commit| links

← Older revision		Revision as of 09:30, 2 November 2011
Line 47:		Line 47:
	== Standalone driver ==		== Standalone driver ==

	This is how WRF-Fire was originally developed. The driver was phys/model_test_main.F until ~~[http://repo.or.cz/w/wrffire.git/~~commit/a3f839e50ebcf7e068c8aa0266401220bc09f2ec deleted] in November 2008. The last commit with the driver working might be ~~[http://repo.or.cz/w/wrffire.git/~~commit/135afed6783683d273b0eac9e0c1b959bd9e2351 this]. It should be resurrected now after the long argument lists are cleaned up. What would the driver do for inputs and outputs? NetCDF? [[User:Jmandel\|Jmandel]] 04:39, 30 May 2010 (UTC)		This is how WRF-Fire was originally developed. The driver was phys/model_test_main.F until {{WRF-Fire-commit\|a3f839e50ebcf7e068c8aa0266401220bc09f2ec\|deleted in November 2008}}. The last commit with the driver working might be {{WRF-Fire-commit\|135afed6783683d273b0eac9e0c1b959bd9e2351\|this}}. It should be resurrected now after the long argument lists are cleaned up. What would the driver do for inputs and outputs? NetCDF? [[User:Jmandel\|Jmandel]] 04:39, 30 May 2010 (UTC)

	:I think NetCDF would be best. In fact, I think we should maintain some sort of compatibility between these and WRF output files. This way, we can use existing visualization/data assimilation code. All this really requires is naming the variables and dimensions the same. [[User:Jbeezley\|Jbeezley]] 07:55, 30 May 2010 (UTC)		:I think NetCDF would be best. In fact, I think we should maintain some sort of compatibility between these and WRF output files. This way, we can use existing visualization/data assimilation code. All this really requires is naming the variables and dimensions the same. [[User:Jbeezley\|Jbeezley]] 07:55, 30 May 2010 (UTC)

Jmandel: /* Standalone driver */ typo

2011-11-02T09:26:02Z

Standalone driver: typo

← Older revision		Revision as of 09:26, 2 November 2011
Line 53:		Line 53:
	Re [http://www.openwfm.org/w/index.php5?title=WRF-Fire_development_notes&diff=prev&oldid=910 this edit]: Why would a standalone driver be for diagnostics only? Of course diagnostics would be the main purpose for us, but many models, such as [[FARSITE]], do not interface with atmosphere either. If we can run from the same data, it would be interesting to compare. I suppose this could be still called diagnostics, though. [[User:Jmandel\|Jmandel]] 16:37, 5 June 2010 (UTC)		Re [http://www.openwfm.org/w/index.php5?title=WRF-Fire_development_notes&diff=prev&oldid=910 this edit]: Why would a standalone driver be for diagnostics only? Of course diagnostics would be the main purpose for us, but many models, such as [[FARSITE]], do not interface with atmosphere either. If we can run from the same data, it would be interesting to compare. I suppose this could be still called diagnostics, though. [[User:Jmandel\|Jmandel]] 16:37, 5 June 2010 (UTC)

	The standalone model {{WRF-Fire-commit\|168fbfaa8a62061b51999001dc55162e2ac3a798\|now}} runs from WRF outputs, with additional fire mesh variables (wind interpolation, fuel data) added by preprocessing in the coupled fire model. For documentation, see [[How to run the standalone fire model in WRF-Fire]]. To do: another driver that would run only the preprocessing to take unmodified WRF output, add the fire variables, and create an input file to run the standalone code from. There is a hook in '''standalone/Makefile''' for '''atm.exe''' for this purpose already. Also, the utility '''init.exe''' to create to create a simple ideal ~~examples~~ without WRF at all should be revived. [[User:Jmandel\|Jmandel]] 20:01, 28 October 2011 (UTC)		The standalone model {{WRF-Fire-commit\|168fbfaa8a62061b51999001dc55162e2ac3a798\|now}} runs from WRF outputs, with additional fire mesh variables (wind interpolation, fuel data) added by preprocessing in the coupled fire model. For documentation, see [[How to run the standalone fire model in WRF-Fire]]. To do: another driver that would run only the preprocessing to take unmodified WRF output, add the fire variables, and create an input file to run the standalone code from. There is a hook in '''standalone/Makefile''' for '''atm.exe''' for this purpose already. Also, the utility '''init.exe''' to create to create a simple ideal example without WRF at all should be revived. [[User:Jmandel\|Jmandel]] 20:01, 28 October 2011 (UTC)

	== Gradual ignition ==		== Gradual ignition ==

Jmandel: /* Standalone driver */

2011-10-28T20:01:10Z

Standalone driver

← Older revision		Revision as of 20:01, 28 October 2011
Line 53:		Line 53:
	Re [http://www.openwfm.org/w/index.php5?title=WRF-Fire_development_notes&diff=prev&oldid=910 this edit]: Why would a standalone driver be for diagnostics only? Of course diagnostics would be the main purpose for us, but many models, such as [[FARSITE]], do not interface with atmosphere either. If we can run from the same data, it would be interesting to compare. I suppose this could be still called diagnostics, though. [[User:Jmandel\|Jmandel]] 16:37, 5 June 2010 (UTC)		Re [http://www.openwfm.org/w/index.php5?title=WRF-Fire_development_notes&diff=prev&oldid=910 this edit]: Why would a standalone driver be for diagnostics only? Of course diagnostics would be the main purpose for us, but many models, such as [[FARSITE]], do not interface with atmosphere either. If we can run from the same data, it would be interesting to compare. I suppose this could be still called diagnostics, though. [[User:Jmandel\|Jmandel]] 16:37, 5 June 2010 (UTC)

	The standalone model {{WRF-Fire-commit\|168fbfaa8a62061b51999001dc55162e2ac3a798\|now}} runs from WRF outputs, with additional fire mesh variables (wind interpolation, fuel data) added by preprocessing in the coupled fire model. For documentation, see [[How to run the standalone fire model in WRF-Fire]]. To do: another driver that would run only the preprocessing to take unmodified WRF output, add the fire variables, and create an input file to run the standalone code from. There is a hook in '''standalone/Makefile''' for '''atm.exe''' for this purpose already. [[User:Jmandel\|Jmandel]] 19:59, 28 October 2011 (UTC)		The standalone model {{WRF-Fire-commit\|168fbfaa8a62061b51999001dc55162e2ac3a798\|now}} runs from WRF outputs, with additional fire mesh variables (wind interpolation, fuel data) added by preprocessing in the coupled fire model. For documentation, see [[How to run the standalone fire model in WRF-Fire]]. To do: another driver that would run only the preprocessing to take unmodified WRF output, add the fire variables, and create an input file to run the standalone code from. There is a hook in '''standalone/Makefile''' for '''atm.exe''' for this purpose already. Also, the utility '''init.exe''' to create to create a simple ideal examples without WRF at all should be revived. [[User:Jmandel\|Jmandel]] 20:01, 28 October 2011 (UTC)

	== Gradual ignition ==		== Gradual ignition ==

← Older revision		Revision as of 04:56, 4 January 2012
Line 106:		Line 106:

	Implemented {{WRF-Fire-commit\|716cf59c2313e3bb483a57db02211d17b8d095f7\|March 24, 2011}}, for now in ideal run only. See		Implemented {{WRF-Fire-commit\|716cf59c2313e3bb483a57db02211d17b8d095f7\|March 24, 2011}}, for now in ideal run only. See
	{{ccm\|Jan_Mandel/Blog#March_24:_WRF-Fire:_Perimeter_ignition\|more info and pictures}}. [[User:Jmandel\|Jmandel]] 05:06, 25 March 2011 (UTC)		{{ccm\|Jan_Mandel/Blog/2011_Feb_Mar#March_24:_WRF-Fire:_Perimeter_ignition\|more info and pictures}}. [[User:Jmandel\|Jmandel]] 05:06, 25 March 2011 (UTC)

	== {{wp\|Google Earth}} ==		== {{wp\|Google Earth}} ==