WRF-Fire merge testing - Revision history

Afarguell: /* GNU */

2019-02-18T17:47:21Z

GNU

← Older revision		Revision as of 17:47, 18 February 2019
Line 106:		Line 106:

	* Hybrid executions: develop-intel-hybrid and fuel-moisture-model-intel-hybrid. They are compiled using configure option: ifort compiler with icc dmpar (16), nesting 1. All the executions crash because of memory corruption.		* Hybrid executions: develop-intel-hybrid and fuel-moisture-model-intel-hybrid. They are compiled using configure option: ifort compiler with icc dmpar (16), nesting 1. All the executions crash because of memory corruption.

	~~====GNU====~~

	===WRF in fuel-moisture-model branch===		===WRF in fuel-moisture-model branch===

Afarguell: /* PGI */

2019-02-18T17:47:10Z

PGI

← Older revision		Revision as of 17:47, 18 February 2019
Line 106:		Line 106:

	* Hybrid executions: develop-intel-hybrid and fuel-moisture-model-intel-hybrid. They are compiled using configure option: ifort compiler with icc dmpar (16), nesting 1. All the executions crash because of memory corruption.		* Hybrid executions: develop-intel-hybrid and fuel-moisture-model-intel-hybrid. They are compiled using configure option: ifort compiler with icc dmpar (16), nesting 1. All the executions crash because of memory corruption.

	~~====PGI====~~


	====GNU====		====GNU====

Afarguell: /* Results */

2019-02-18T17:46:57Z

Results

← Older revision		Revision as of 17:46, 18 February 2019
Line 144:		Line 144:

	All these executions are run in order to compare the three different results.		All these executions are run in order to compare the three different results.

	~~====Results====~~

	==Adam's test results==		==Adam's test results==

Afarguell: /* Running WTF in Cheyenne */

2019-02-10T08:59:47Z

Running WTF in Cheyenne

← Older revision		Revision as of 08:59, 10 February 2019
Line 115:		Line 115:
	In order to test WRF in the new {{wrf-fire-merge-branch\|fuel-moisture-model}}, the WTF is used.		In order to test WRF in the new {{wrf-fire-merge-branch\|fuel-moisture-model}}, the WTF is used.
	====Running WTF in Cheyenne====		====Running WTF in Cheyenne====
	The new WTF code is ~~downloaded~~ using		The new WTF code is updated to work on Cheyenne and using run_from_github.py. New update is in:
	<pre>		<pre>
	~~wget http~~://~~www2~~.~~mmm.ucar.edu~~/~~wrf~~/~~src/wtf_v04.09_small.tar~~		git clone https://github.com/openwfm/WTF
	</pre>		</pre>
	After that, the ~~tar file is uncompressed~~ using		After that, one can change to the correct branch using
	<pre>		<pre>
	~~tar -xvf wtf_v04.09_small.tar~~		git checkout angelfc
	~~cd WTF_v04.09~~
	</pre>		</pre>
	~~Once~~ one ~~try to use ./~~run_from_github.py python execution~~, an error appear which says that Data folder is old. So, the new Data folder is downloaded using~~		Then one can just run run_from_github.py python execution doing:
	<pre>		<pre>
	cd ..		./run_from_github.py
	~~wget http:~~/~~/www2.mmm.ucar.edu/wrf/tmp/data_v04.08~~.~~tar~~
	</pre>		</pre>
	~~After that,~~ the ~~new data is uncompressed~~ and ~~replaced using~~		One needs to give also the github repository to test and the branch which are going to be:
	<pre>		<pre>
	~~tar~~ -~~xvf data_v04.08.tar~~		URL of the repository: https://github.com/openwfm/WRF-Fire-merge
	rm -~~fr WTF_v04.09/Data~~		branch: master
	~~mv Data WTF_v04.09~~
	</pre>		</pre>
	~~Then, the new version of the data is updated in line 42 of run_from_github.py file as~~		and
	<pre>		<pre>
	~~version="v04~~.~~08"~~		URL of the repository: https://github.com/openwfm/WRF-Fire-merge
	</~~pre>~~		branch: develop
	~~It is also needed to provide the account code to run the qsub in file qsub_this_to_run_all_compiler.csh. In our case, it should be~~
	~~<pre>~~
	~~#PBS -A UCUD0004~~
	</pre>		</pre>
	~~Finally, one can run the code doing~~		and
	~~<pre>~~
	~~./run_from_github.py~~
	~~</pre>~~
	~~One needs to give also the github repository to test~~ and ~~the branch which are going to be:~~
	<pre>		<pre>
	URL of the repository: https://github.com/openwfm/WRF-Fire-merge		URL of the repository: https://github.com/openwfm/WRF-Fire-merge
	branch: fuel-moisture-model		branch: fuel-moisture-model
	</pre>		</pre>

			All these executions are run in order to compare the three different results.

	====Results====		====Results====

Afarguell: /* Intel */

2019-02-10T08:46:49Z

Intel

← Older revision		Revision as of 08:46, 10 February 2019
Line 99:		Line 99:

	====Intel====		====Intel====
	* Serial executions: develop-intel-serial and fuel-moisture-model-intel-serial.		* Serial executions: develop-intel-serial and fuel-moisture-model-intel-serial. They are compiled using configure option: ifort compiler with icc serial (13), nesting 0. Both hill simple and two fires cases give exactly the same results.

	They are compiled using configure option: ifort compiler with icc ~~serial~~ (13), nesting 0.		* OpenMP executions: develop-intel-openmp and fuel-moisture-model-intel-openmp. They are compiled using configure option: ifort compiler with icc dmpar (14), nesting 0.

	~~Both~~ hill simple and two fires ~~cases give exactly the~~ same results.		* MPI executions: develop-intel-mpi and fuel-moisture-model-intel-mpi. They are compiled using configure option: ifort compiler with icc dmpar (15), nesting 1. In both ideal cases hill simple and two fires, same results in variables U, V, and TIGN_G from wrfouts. Using 1, 2, 4 and 8 MPI processes.

	* OpenMP executions: develop-intel-openmp and fuel-moisture-model-intel-openmp.		* Hybrid executions: develop-intel-hybrid and fuel-moisture-model-intel-hybrid. They are compiled using configure option: ifort compiler with icc dmpar (16), nesting 1. All the executions crash because of memory corruption.

	~~They are compiled using configure option: ifort compiler with icc dmpar (14), nesting 0.~~

	* MPI executions: develop-intel-mpi and fuel-moisture-model-intel-mpi.

	~~They are compiled using configure option: ifort compiler with icc dmpar (15), nesting 1.~~

	~~In both ideal cases hill simple and two fires, same results in variables U, V, and TIGN_G from wrfouts. Using 1, 2, 4 and 8 MPI processes.~~

	* Hybrid executions: develop-intel-hybrid and fuel-moisture-model-intel-hybrid.

	They are compiled using configure option: ifort compiler with icc dmpar (16), nesting 1.

	All the executions crash because of memory corruption.

	====PGI====		====PGI====

Afarguell: /* Branch develop vs. fuel-moisture-model without fuel moisture */

2019-02-10T08:46:09Z

Branch develop vs. fuel-moisture-model without fuel moisture

← Older revision		Revision as of 08:46, 10 February 2019
Line 103:		Line 103:
	They are compiled using configure option: ifort compiler with icc serial (13), nesting 0.		They are compiled using configure option: ifort compiler with icc serial (13), nesting 0.

	* ~~Parallel~~ executions: develop-intel-mpi and fuel-moisture-model-intel-mpi.		Both hill simple and two fires cases give exactly the same results.

			* OpenMP executions: develop-intel-openmp and fuel-moisture-model-intel-openmp.

			They are compiled using configure option: ifort compiler with icc dmpar (14), nesting 0.

			* MPI executions: develop-intel-mpi and fuel-moisture-model-intel-mpi.

	They are compiled using configure option: ifort compiler with icc dmpar (15), nesting 1.		They are compiled using configure option: ifort compiler with icc dmpar (15), nesting 1.

			In both ideal cases hill simple and two fires, same results in variables U, V, and TIGN_G from wrfouts. Using 1, 2, 4 and 8 MPI processes.

			* Hybrid executions: develop-intel-hybrid and fuel-moisture-model-intel-hybrid.

			They are compiled using configure option: ifort compiler with icc dmpar (16), nesting 1.

			All the executions crash because of memory corruption.

	====PGI====		====PGI====


	====GNU====		====GNU====


	===WRF in fuel-moisture-model branch===		===WRF in fuel-moisture-model branch===

Afarguell: /* WRF in fuel-moisture-model branch */

2019-02-07T20:22:25Z

WRF in fuel-moisture-model branch

← Older revision		Revision as of 20:22, 7 February 2019
Line 114:		Line 114:

	===WRF in fuel-moisture-model branch===		===WRF in fuel-moisture-model branch===
	In order to test WRF in the new {{wrf-fire-merge-branch\|fuel-moisture-model}}, the WTF is used. ~~Therefore, the~~ new WTF code is downloaded using		In order to test WRF in the new {{wrf-fire-merge-branch\|fuel-moisture-model}}, the WTF is used.
			====Running WTF in Cheyenne====
			The new WTF code is downloaded using
	<pre>		<pre>
	wget http://www2.mmm.ucar.edu/wrf/src/wtf_v04.09_small.tar		wget http://www2.mmm.ucar.edu/wrf/src/wtf_v04.09_small.tar
Line 151:		Line 153:
	branch: fuel-moisture-model		branch: fuel-moisture-model
	</pre>		</pre>
			====Results====

	==Adam's test results==		==Adam's test results==

Afarguell: /* Angel's test results */

2019-02-07T20:20:56Z

Angel's test results

@@ Line 50: / Line 50: @@
 ==Angel's test results==
-All kingspeak runs are in /uufs/chpc.utah.edu/common/home/kochanski-group3/farguella/merge and run on node kingspeak11 and kinspeak12. All the compilation are done using ifort serial (13), nesting 0.
+All kingspeak runs are in /uufs/chpc.utah.edu/common/home/kochanski-group3/farguella/merge.
 ===Branch develop vs. added-fmc_g===
 The {{wrf-fire-merge-branch|develop}} and {{wrf-fire-merge-branch|added-fmc_g}} are in kingspeak in folders WRF-Fire-merge-develop and WRF-Fire-merge-added-fmc_g respectively. They are tested in order to see the first new functionalities of adding variable FMC_G in WRF4 baseline. Tests are from list in https://www.openwfm.org/index.php?title=Porting_WRF-SFIRE_fuel_moisture_model_to_WRF4#Testing_to_be_done.
 ====fire_fmc_read not present in namelist.input====
@@ Line 87: / Line 90: @@
 * Slope FMC_G field: RF-Fire-merge-added-fmc_g/test/em_fire/hill_tests/fmc_slope.
 ==Adam's test results==

Jmandel at 16:58, 7 February 2019

2019-02-07T16:58:06Z

← Older revision		Revision as of 16:58, 7 February 2019
Line 3:		Line 3:
	''Please see [[Talk:WRF-Fire_merge_testing]] for permanent notes.''		''Please see [[Talk:WRF-Fire_merge_testing]] for permanent notes.''

			==The basics==

	The version to test is {{wrf-fire-merge-branch\|fuel-moisture-model}} currently at commit {{wrf-fire-merge-commit\|c1cedfc7eba28a2ed\|}}		The version to test is {{wrf-fire-merge-branch\|fuel-moisture-model}} currently at commit {{wrf-fire-merge-commit\|c1cedfc7eba28a2ed\|}}
Line 12:		Line 13:
	The namelist.input and namelist.fire with variables that turn the fuel moisture model and fire on are in test/em_fire_rain/rain. The description of the namelist variables is at [[Fuel_moisture_model#Configuration]]. Other features from WRF-SFIRE are not carried over - only the fuel moisture model.		The namelist.input and namelist.fire with variables that turn the fuel moisture model and fire on are in test/em_fire_rain/rain. The description of the namelist variables is at [[Fuel_moisture_model#Configuration]]. Other features from WRF-SFIRE are not carried over - only the fuel moisture model.

	Who is doing what:		==Who is doing what==

	* Angel - [[WTF]], parallel testing of both branches for identical results, all test cases in test/em_fire		* Angel - [[WTF]], parallel testing of both branches for identical results, all test cases in test/em_fire

Jmandel at 16:56, 7 February 2019

2019-02-07T16:56:43Z

← Older revision		Revision as of 16:56, 7 February 2019
Line 8:		Line 8:
	The baseline is WRF4 {{wrf-fire-merge-branch\|develop}} currently at commit {{wrf-fire-merge-commit\|0f296f9c0f674f9\|}}		The baseline is WRF4 {{wrf-fire-merge-branch\|develop}} currently at commit {{wrf-fire-merge-commit\|0f296f9c0f674f9\|}}

	When either branch advances we have to retest - after any fix in fuel-moisture-model ~~(I will let you know)~~, and, after we are done, we will have to forward branch develop to current WRF4 and merge it into fuel-moisture-model. For this reason (and to reduce confusion), I am trying to organize the tests in a way that they are really easy to rerun without modifying any files - separate clones for different compilation options and separate copies of test/em_fire directory for different test cases.		When either branch advances we have to retest - after any fix in fuel-moisture-model, and, after we are done, we will have to forward branch develop to current WRF4 and merge it into fuel-moisture-model. For this reason (and to reduce confusion), I am trying to organize the tests in a way that they are really easy to rerun without modifying any files - separate clones for different compilation options and separate copies of test/em_fire directory for different test cases.

	The namelist.input and namelist.fire with variables that turn the fuel moisture model and fire on are in test/em_fire_rain/rain. The description of the namelist variables is at [[Fuel_moisture_model#Configuration]]. Other features from WRF-SFIRE are not carried over - only the fuel moisture model.		The namelist.input and namelist.fire with variables that turn the fuel moisture model and fire on are in test/em_fire_rain/rain. The description of the namelist variables is at [[Fuel_moisture_model#Configuration]]. Other features from WRF-SFIRE are not carried over - only the fuel moisture model.