Smoke and coupling with WRF-Chem - Revision history

Jmandel: spelling

2025-11-22T05:56:37Z

spelling

← Older revision		Revision as of 05:56, 22 November 2025
Line 2:		Line 2:


	[[File:Sfire smoke.png\|thumb\|~~SFire~~ smoke tracer in action. See [[File:Smoke small.avi\|animation]].]]		[[File:Sfire smoke.png\|thumb\|WRF-SFIRE smoke tracer in action. See [[File:Smoke small.avi\|animation]].]]

	Fire emissions can be modeled a passive smoke tracer advected by the wind field,		Fire emissions can be modeled a passive smoke tracer advected by the wind field,

Jmandel: /* Coupling with WRF-Chem */

2025-11-22T05:55:45Z

Coupling with WRF-Chem

← Older revision		Revision as of 05:55, 22 November 2025
Line 27:		Line 27:
	The selection of the tracers in WRF-Chem is controlled by namelist variable '''chem_opt''' in '''&chem''' section of '''namelist.input'''. If '''chem_opt=0''', no chemical tracers are created. The coupling supports subsets of RADM2 ('''chem_opt=2'''), MOZART ('''chem_opt=112''' or '''119'''), and GOCART ('''chem_opt=300''') variables.		The selection of the tracers in WRF-Chem is controlled by namelist variable '''chem_opt''' in '''&chem''' section of '''namelist.input'''. If '''chem_opt=0''', no chemical tracers are created. The coupling supports subsets of RADM2 ('''chem_opt=2'''), MOZART ('''chem_opt=112''' or '''119'''), and GOCART ('''chem_opt=300''') variables.

	It is also possible to use '''tracer_opt = 1''' ~~and~~ '''tracer_opt = 2''' in a code compiled with WRF-Chem~~, but the~~ resulting passive tracers ~~are~~ advected by WRF-Chem ~~and behave slightly differently~~.		It is also possible to use '''tracer_opt = 1''' or '''tracer_opt = 2''' with a code compiled with WRF-Chem. The resulting passive tracers may then be advected by code in WRF-Chem instead of WRF itself.

	==Running an idealized example==		==Running an idealized example==

Jmandel: /* Passive smoke tracers */

2025-11-22T05:53:19Z

Passive smoke tracers

← Older revision		Revision as of 05:53, 22 November 2025
Line 14:		Line 14:
	Emissions are computer proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions''' and added to the lowest layer of the active tracer variables.		Emissions are computer proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions''' and added to the lowest layer of the active tracer variables.

	There are small differences between the propagation of the different tracers, and also between the propagation when the code is build with or without WRF-~~CHEM~~.		There are small differences between the propagation of the different tracers, and also between the propagation when the code is build with or without WRF-Chem.

	==Coupling with WRF-Chem==		==Coupling with WRF-Chem==

Jmandel: /* Passive smoke tracers */

2025-11-22T05:52:44Z

Passive smoke tracers

← Older revision		Revision as of 05:52, 22 November 2025
Line 12:		Line 12:
	and the option '''tracer_opt = 2''', which creates passive tracers called '''tr17_1''' to '''tr17_8'''.		and the option '''tracer_opt = 2''', which creates passive tracers called '''tr17_1''' to '''tr17_8'''.

	Emissions are ~~inserted~~ proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions'''~~. The fire smoke emissions~~ added to the ~~tracers~~ are the ~~same. Propagation~~ of tracers ~~'''tr17_1''' to '''tr17_4''' is identical~~, ~~but~~ the ~~others slightly differ~~.		Emissions are computer proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions''' and added to the lowest layer of the active tracer variables.

			There are small differences between the propagation of the different tracers, and also between the propagation when the code is build with or without WRF-CHEM.

	==Coupling with WRF-Chem==		==Coupling with WRF-Chem==

Jmandel: /* Passive smoke tracers */ typo

2025-11-22T03:20:54Z

Passive smoke tracers: typo

← Older revision		Revision as of 03:20, 22 November 2025
Line 9:		Line 9:
	==Passive smoke tracers==		==Passive smoke tracers==

	The selection of the tracers in WRF is controlled by namelist variable '''tracer_opt''' in the '''&dynamics'''] section . ~~Yhe~~ coupling supports the option '''tracer_opt = 1''', which creates a single tracer called '''smoke''',		The selection of the tracers in WRF is controlled by namelist variable '''tracer_opt''' in the '''&dynamics'''] section . The coupling supports the option '''tracer_opt = 1''', which creates a single tracer called '''smoke''',
	and the option '''tracer_opt = 2''', which creates passive tracers called '''tr17_1''' to '''tr17_8'''.		and the option '''tracer_opt = 2''', which creates passive tracers called '''tr17_1''' to '''tr17_8'''.

Jmandel: /* Passive smoke tracers */

2025-11-22T03:20:27Z

Passive smoke tracers

← Older revision		Revision as of 03:20, 22 November 2025
Line 9:		Line 9:
	==Passive smoke tracers==		==Passive smoke tracers==

	The selection of the tracers in WRF is controlled by namelist variable '''tracer_opt''' in the '''&dynamics'''] section . ~~At the moment, the~~ coupling supports '''tracer_opt = 1''', which creates a single tracer called '''smoke'''.		The selection of the tracers in WRF is controlled by namelist variable '''tracer_opt''' in the '''&dynamics'''] section . Yhe coupling supports the option '''tracer_opt = 1''', which creates a single tracer called '''smoke''',
	~~The~~ option '''tracer_opt = 2''' creates passive tracers called '''tr17_1''' to '''tr17_8'''.		and the option '''tracer_opt = 2''', which creates passive tracers called '''tr17_1''' to '''tr17_8'''.

	Emissions are inserted proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions'''. ~~Properties~~ of ~~the~~ tracers '''tr17_1''' to '''tr17_4''' ~~are~~ identical, but the others slightly differ.		Emissions are inserted proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions'''. The fire smoke emissions added to the tracers are the same. Propagation of tracers '''tr17_1''' to '''tr17_4''' is identical, but the others slightly differ.

	==Coupling with WRF-Chem==		==Coupling with WRF-Chem==

Jmandel: /* Passive smoke tracers */

2025-11-22T03:16:37Z

Passive smoke tracers

← Older revision		Revision as of 03:16, 22 November 2025
Line 12:		Line 12:
	The option '''tracer_opt = 2''' creates passive tracers called '''tr17_1''' to '''tr17_8'''.		The option '''tracer_opt = 2''' creates passive tracers called '''tr17_1''' to '''tr17_8'''.

	Emissions \are inserted proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions'''. Properties of the tracers '''tr17_1''' to '''tr17_4''' are identical, but the others slightly differ.		Emissions are inserted proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions'''. Properties of the tracers '''tr17_1''' to '''tr17_4''' are identical, but the others slightly differ.

	==Coupling with WRF-Chem==		==Coupling with WRF-Chem==

Jmandel: /* Coupling with WRF-Chem */ typo

2025-11-22T00:23:56Z

Coupling with WRF-Chem: typo

← Older revision		Revision as of 00:23, 22 November 2025
Line 23:		Line 23:
	</pre>		</pre>

	The selection of the tracers in WRF-Chem is controlled by namelist variable '''chem_opt'''in '''&chem''' section of '''namelist.input'''. If '''chem_opt=0''', no chemical tracers are created. The coupling supports subsets of RADM2 ('''chem_opt=2'''), MOZART ('''chem_opt=112''' or '''119'''), and GOCART ('''chem_opt=300''') variables.		The selection of the tracers in WRF-Chem is controlled by namelist variable '''chem_opt''' in '''&chem''' section of '''namelist.input'''. If '''chem_opt=0''', no chemical tracers are created. The coupling supports subsets of RADM2 ('''chem_opt=2'''), MOZART ('''chem_opt=112''' or '''119'''), and GOCART ('''chem_opt=300''') variables.

	~~It is also possible to use '''tracer_opt = 1''' and '''tracer_opt = 2''' in a code compiled with WRF-Chem, but the resulting passive tracers are advected by WRF-Chem and behave slightly differently~~.

			It is also possible to use '''tracer_opt = 1''' and '''tracer_opt = 2''' in a code compiled with WRF-Chem, but the resulting passive tracers are advected by WRF-Chem and behave slightly differently.

	==Running an idealized example==		==Running an idealized example==

Jmandel: separated passive tracers and chem

2025-11-22T00:23:34Z

separated passive tracers and chem

← Older revision		Revision as of 00:23, 22 November 2025
Line 9:		Line 9:
	==Passive smoke tracers==		==Passive smoke tracers==

	==~~Compiling~~ with ~~chem support~~==		The selection of the tracers in WRF is controlled by namelist variable '''tracer_opt''' in the '''&dynamics'''] section . At the moment, the coupling supports '''tracer_opt = 1''', which creates a single tracer called '''smoke'''.
			The option '''tracer_opt = 2''' creates passive tracers called '''tr17_1''' to '''tr17_8'''.

			Emissions \are inserted proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions'''. Properties of the tracers '''tr17_1''' to '''tr17_4''' are identical, but the others slightly differ.

			==Coupling with WRF-Chem==
	Compiling the code with support for WRF-Chem is similar to the [[How to compile WRF-Fire\|standard procedure]].		Compiling the code with support for WRF-Chem is similar to the [[How to compile WRF-Fire\|standard procedure]].
	You must set an environment variable '''WRF_CHEM''' and configure with the argument '''chem''' as follows.		You must set an environment variable '''WRF_CHEM''' and configure with the argument '''chem''' as follows.
Line 17:		Line 22:
	./compile em_fire		./compile em_fire
	</pre>		</pre>

			The selection of the tracers in WRF-Chem is controlled by namelist variable '''chem_opt'''in '''&chem''' section of '''namelist.input'''. If '''chem_opt=0''', no chemical tracers are created. The coupling supports subsets of RADM2 ('''chem_opt=2'''), MOZART ('''chem_opt=112''' or '''119'''), and GOCART ('''chem_opt=300''') variables.

			It is also possible to use '''tracer_opt = 1''' and '''tracer_opt = 2''' in a code compiled with WRF-Chem, but the resulting passive tracers are advected by WRF-Chem and behave slightly differently.


	==Running an idealized example==		==Running an idealized example==
Line 24:		Line 34:

	==Configuration==		==Configuration==
	The selection of the model in WRF-Chem is controlled by namelist variables '''tracer_opt''' in the [https://github.com/jbeezley/wrf-fire/blob/4c0851085eeb25d9143bd5b07e736fe949700497/wrfv2_fire/test/em_fire/chem/namelist.input#L78 '''&dynamics'''] section and '''chem_opt''' in the [https://github.com/jbeezley/wrf-fire/blob/4c0851085eeb25d9143bd5b07e736fe949700497/wrfv2_fire/test/em_fire/chem/namelist.input#L203 '''&chemistry'''] section of '''namelist.input'''. At the moment, the coupling supports '''tracer_opt = 1''', which creates a single tracer called '''smoke''', and a subset of RADM2 ('''chem_opt=2'''), MOZART ('''chem_opt=112''' or '''119'''), and GOCART ('''chem_opt=300''') variables.

	The option '''tracer_opt = 2''' does not require WRF-Chem, and it creates passive tracers called '''tr17_1''' to '''tr17_8'''. Emissions \are inserted proportionally to the fuel burned according to the emission factors in file '''namelist.fire_emissions'''. Properties of the tracers '''tr17_1''' to '''tr17_4''' are identical, but the others slightly differ.

	To use the passive tracers in the code built with WRF-Chem, specify '''tracer_opt=2''' and '''chem_opt=0''' in '''namelist.input'''. The tracers work slightly differently in code built with and without WRF-Chem, as described in file '''chem/module_input_tracer.F'''. A sample emission factors table for this usage is available as '''test/em_fire/chem/namelist.fire_emissions.tracers'''. It can be used in ideal as well as real runs. Different rows in the table can be used to track separate species, e.g., pm10 and pm25, with different emission factors.		To use the passive tracers in the code built with WRF-Chem, specify '''tracer_opt=2''' and '''chem_opt=0''' in '''namelist.input'''. The tracers work slightly differently in code built with and without WRF-Chem, as described in file '''chem/module_input_tracer.F'''. A sample emission factors table for this usage is available as '''test/em_fire/chem/namelist.fire_emissions.tracers'''. It can be used in ideal as well as real runs. Different rows in the table can be used to track separate species, e.g., pm10 and pm25, with different emission factors.

Jmandel: redo lead

2025-11-22T00:09:36Z

redo lead

← Older revision		Revision as of 00:09, 22 November 2025
Line 1:		Line 1:
	{{users guide}}		{{users guide}}

	~~As of WRF 4, WRF-Chem is now included in the WRF repository. Fire emissions can now input into WRF-Chem as chemical species or a simple smoke tracer.~~ [[File:Sfire smoke.png\|thumb\|SFire smoke tracer in action. See [[File:Smoke small.avi\|animation]].]]
			[[File:Sfire smoke.png\|thumb\|SFire smoke tracer in action. See [[File:Smoke small.avi\|animation]].]]

			Fire emissions can be modeled a passive smoke tracer advected by the wind field,
			or as chemical species tracers, which also undergo chemical reactions by WRF-Chem. WRF-Chem is included in the WRF repository. Tracer variables are 3d fields of concentrations on the atmospheric grid. The variables are present in the wrfout files when activated.

			==Passive smoke tracers==

	==Compiling with chem support==		==Compiling with chem support==