How to add namelist variables - Revision history

Jmandel at 06:36, 17 May 2019

2019-05-17T06:36:13Z

← Older revision		Revision as of 06:36, 17 May 2019
Line 1:		Line 1:
	[[Category:~~wrf~~-~~fire~~]]		[[Category:WRF-Fire]]
	==[[namelist.input]]==		==[[namelist.input]]==
	# '''Edit Registry/registry.fire to add a config line.''' It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)		# '''Edit Registry/registry.fire to add a config line.''' It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)

Jmandel: /* namelist.fire */

2019-05-17T06:34:58Z

namelist.fire

← Older revision		Revision as of 06:34, 17 May 2019
Line 5:		Line 5:
	# Add a line to copy the value from config_flags into the variable in '''module_fr_sfire_driver.F''' subroutine '''set_flags'''		# Add a line to copy the value from config_flags into the variable in '''module_fr_sfire_driver.F''' subroutine '''set_flags'''
	==[[namelist.fire]]==		==[[namelist.fire]]==
			# Add a declaration of the variable at the beginning of '''module_fr_sfire_phys.F''', before the "contains" statement. That will make it accessible throughout that file.
			# The variable can be either scalar, or vary by category, then declare it with '''dimension(mfuelcats)'''
			# If you want to use the variable in other files, you need to make it PUBLIC a little bit below and import it in those other files through a USE statement. E.g. you can add it to
			<pre>
			use module_fr_sfire_phys, only: mfuelcats, nfuelcats
			</pre>
			in module_fr_sfire_atm.F (if your added code deals with atmosphere, it should go this file)
			# Add '''data''' statement after the declaration with your default values for the variable
			# In subroute '''init_fuel_cats''', add the variable to '''namelist /fuel_categories/'''. The order does note matter.
			# Add '''call wrf_dm_bcast_real''' or '''call wrf_dm_bcast_integer'''as appropriate to communicate the variable to other MPI processes; the file namelist.fire is read only by the master process.
			# The description above is for fuel categories. The code for fuel moisture classes is similar.

	==See also==		==See also==
	* [[namelist.input]]		* [[namelist.input]]
	* [[namelist.fire]]		* [[namelist.fire]]

Jmandel at 06:17, 17 May 2019

2019-05-17T06:17:18Z

← Older revision		Revision as of 06:17, 17 May 2019
Line 1:		Line 1:
	[[Category:wrf-fire]]		[[Category:wrf-fire]]
			==[[namelist.input]]==
	# '''Edit Registry/registry.fire to add a config line.''' It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)		# '''Edit Registry/registry.fire to add a config line.''' It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)
	# Add declaration of the variable and its default value to the list at the beginning of '''phys/module_fr_sfire_util.F'''. That will make the variable known anywhere in '''phys/module_fr_sfire_*.F'''. Please use the same name for this variable as in the registry, lest a confusion ensues.		# Add declaration of the variable and its default value to the list at the beginning of '''phys/module_fr_sfire_util.F'''. That will make the variable known anywhere in '''phys/module_fr_sfire_*.F'''. Please use the same name for this variable as in the registry, lest a confusion ensues.
	# Add a line to copy the value from config_flags into the variable in '''module_fr_sfire_driver.F''' subroutine '''set_flags'''		# Add a line to copy the value from config_flags into the variable in '''module_fr_sfire_driver.F''' subroutine '''set_flags'''
			==[[namelist.fire]]==

	==See also==		==See also==
	* [[namelist.input]]		* [[namelist.input]]
	* [[namelist.fire]]		* [[namelist.fire]]

Jmandel: /* See also */

2019-05-17T06:16:43Z

Jmandel: Jmandel moved page How to add variables to namelist.input to How to add namelist variables

2019-05-17T06:16:24Z

Jmandel moved page How to add variables to namelist.input to How to add namelist variables

← Older revision	Revision as of 06:16, 17 May 2019
(No difference)

Jmandel at 06:10, 17 May 2019

2019-05-17T06:10:25Z

← Older revision		Revision as of 06:10, 17 May 2019
Line 2:		Line 2:
	# '''Edit Registry/registry.fire to add a config line.''' It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)		# '''Edit Registry/registry.fire to add a config line.''' It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)
	# Add declaration of the variable and its default value to the list at the beginning of '''phys/module_fr_sfire_util.F'''. That will make the variable known anywhere in '''phys/module_fr_sfire_*.F'''. Please use the same name for this variable as in the registry, lest a confusion ensues.		# Add declaration of the variable and its default value to the list at the beginning of '''phys/module_fr_sfire_util.F'''. That will make the variable known anywhere in '''phys/module_fr_sfire_*.F'''. Please use the same name for this variable as in the registry, lest a confusion ensues.
	# Add a line to copy the value from config_flags into the variable in module_fr_sfire_driver.F subroutine set_flags		# Add a line to copy the value from config_flags into the variable in '''module_fr_sfire_driver.F''' subroutine '''set_flags'''


	==See also==		==See also==
	* [[namelist.input]]		* [[namelist.input]]

Jmandel at 06:09, 17 May 2019

2019-05-17T06:09:51Z

← Older revision		Revision as of 06:09, 17 May 2019
Line 1:		Line 1:
			[[Category:wrf-fire]]
	# '''Edit Registry/registry.fire to add a config line.''' It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)		# '''Edit Registry/registry.fire to add a config line.''' It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)
			# Add declaration of the variable and its default value to the list at the beginning of '''phys/module_fr_sfire_util.F'''. That will make the variable known anywhere in '''phys/module_fr_sfire_*.F'''. Please use the same name for this variable as in the registry, lest a confusion ensues.
			# Add a line to copy the value from config_flags into the variable in module_fr_sfire_driver.F subroutine set_flags


			==See also==
			* [[namelist.input]]

Jmandel at 06:02, 17 May 2019

2019-05-17T06:02:54Z

← Older revision		Revision as of 06:02, 17 May 2019
Line 1:		Line 1:
	# Edit Registry/registry.fire to add a line ~~of with fist column rconfig~~. It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)		# '''Edit Registry/registry.fire to add a config line.''' It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)

Jmandel at 06:02, 17 May 2019

2019-05-17T06:02:23Z

← Older revision		Revision as of 06:02, 17 May 2019
Line 1:		Line 1:
	# Edit Registry/registry.fire to add a line of with fist column rconfig. It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky. We really should have used 1 from the beginning always. Oh well.)		# Edit Registry/registry.fire to add a line of with fist column rconfig. It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky, many models are configured so that the finest domain is the last. We really should have used 1 from the beginning always. Oh well.)

Jmandel: Created page with "# Edit Registry/registry.fire to add a line of with fist column rconfig. It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable..."

2019-05-17T06:01:33Z

Created page with "# Edit Registry/registry.fire to add a line of with fist column rconfig. It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable..."

New page

# Edit Registry/registry.fire to add a line of with fist column rconfig. It should be clear from the lines already there how. Use NumTLev 1. Then you need to put the variable in namelist.input line only once. If you use MaxLevels, Otherwise you will need to guess how many levels there are and hit the correct one. (Ideally, the finest level where the fire model lives, should be the first, then it would not matter, but we are not so lucky. We really should have used 1 from the beginning always. Oh well.)

← Older revision		Revision as of 06:16, 17 May 2019
Line 7:		Line 7:
	==See also==		==See also==
	* [[namelist.input]]		* [[namelist.input]]
			* [[namelist.fire]]