Test-suite - Revision history

Fulvio: /* Web-Interface */

2023-12-11T09:21:40Z

Web-Interface

← Older revision		Revision as of 09:21, 11 December 2023
Line 3:		Line 3:
	The updated list of test-suite runs can be found on the old Yambo web-page.		The updated list of test-suite runs can be found on the old Yambo web-page.

	Tests' list is splitted in [http://~~www~~.yambo-code.~~org~~/robots/index.php branches].		Tests' list is splitted in [http://media.yambo-code.eu/robots/index.php branches].
	For each branch many robots are shown.		For each branch many robots are shown.
	Check the [http://~~www~~.yambo-code.~~org~~/robots/bug-fixes/polluce.php bug-fixes] branch as an example.		Check the [http://media.yambo-code.eu/robots/bug-fixes/polluce.php bug-fixes] branch as an example.

	This list is automatically updated by the test-suite driver.pl when the -report option is used.		This list is automatically updated by the test-suite driver.pl when the -report option is used.

Davide: /* Projects & Keys */

2023-04-12T08:57:59Z

Projects & Keys

← Older revision		Revision as of 08:57, 12 April 2023
Line 290:		Line 290:
	So in order to run '''all''' tests belonging to the '''sc''' project just type		So in order to run '''all''' tests belonging to the '''sc''' project just type

	%./driver.pl -tests all -keys sc		$./driver.pl -tests all -keys sc

	Actually the -keys option is more powerful as, in the future, should also select all inputs with specific observables (like gw, optics and so on).		Actually the -keys option is more powerful as, in the future, should also select all inputs with specific observables (like gw, optics and so on).
Line 296:		Line 296:
	The list of project are accessed by simply the first column in the list obtained by using the -l option. In the following are in bold.		The list of project are accessed by simply the first column in the list obtained by using the -l option. In the following are in bold.

	%%./driver.pl -l		$./driver.pl -l
	%Available test materials/systems:		Available test materials/systems:
	%[YAMBO] Al111		[YAMBO] Al111
	% C6H3Cl3		C6H3Cl3
	% PA_chain[H]		PA_chain[H]
	% SiH4		SiH4
	% Al_bulk/GW-OPTICS		Al_bulk/GW-OPTICS
	% H2/OPTICS		H2/OPTICS
	% H_chain/2.05		H_chain/2.05
	% H_chain/2.5		H_chain/2.5
	% hBN/GW-OPTICS		hBN/GW-OPTICS
	% LiF/GW-OPTICS		LiF/GW-OPTICS
	% Si_bulk/GW-OPTICS		Si_bulk/GW-OPTICS
	% Si_surface/OPTICS		Si_surface/OPTICS
	% Si_wire/OPTICS		Si_wire/OPTICS
	% MoS2/pwscf/OPTICS		MoS2/pwscf/OPTICS
	% MoS2/abinit/OPTICS/With-SOC		MoS2/abinit/OPTICS/With-SOC
	% MoS2/abinit/OPTICS/Without-SOC-sp1		MoS2/abinit/OPTICS/Without-SOC-sp1
	% MoS2/abinit/OPTICS/Without-SOC-sp2		MoS2/abinit/OPTICS/Without-SOC-sp2
	%['''QED'''] Si_bulk/QED		['''QED'''] Si_bulk/QED
	%['''NL'''] hBN/NL		['''NL'''] hBN/NL
	%['''RT'''] AlAs[H]		['''RT'''] AlAs[H]
	% H2/RT		H2/RT
	% hBN/RT		hBN/RT
	% Si_bulk/RT		Si_bulk/RT
	% WSe2/RT[H]		WSe2/RT[H]
	% MoS2/pwscf/RT		MoS2/pwscf/RT
	%['''SC'''] H2/SC		['''SC'''] H2/SC
	% hBN/SC		hBN/SC
	% Si_bulk/SC		Si_bulk/SC
	%['''MAGNETIC'''] Si_bulk/MAGNETIC		['''MAGNETIC'''] Si_bulk/MAGNETIC
	%['''ELPH'''] Diamond/ELPH1[H]		['''ELPH'''] Diamond/ELPH1[H]
	% Si_bulk/ELPH/BSE		Si_bulk/ELPH/BSE
	% Si_bulk/ELPH/ELPH_base		Si_bulk/ELPH/ELPH_base
	% Si_bulk/ELPH/ELPH_for_BSE		Si_bulk/ELPH/ELPH_for_BSE
	% Si_bulk/ELPH/QP_CTL		Si_bulk/ELPH/QP_CTL
	%['''KERR'''] Cobalt		['''KERR'''] Cobalt
	% Nickel		Nickel
	% Iron/pwscf		Iron/pwscf
	% Iron/abinit/With-SOC		Iron/abinit/With-SOC
	% Iron/abinit/Without-SOC		Iron/abinit/Without-SOC
	%[BROKEN] Dummy		[BROKEN] Dummy
	% GaAs001-c4x4/YAMBO		GaAs001-c4x4/YAMBO
	% hBN/PL[PL]		hBN/PL[PL]
	% Si001-c4x2/YAMBO		Si001-c4x2/YAMBO
	% WS2/PL[PL]		WS2/PL[PL]

	Note that to access any of these projects you must use the lowercase option. For example		Note that to access any of these projects you must use the lowercase option. For example

Davide: /* Parallel Options */

2023-04-12T08:56:54Z

Parallel Options

Davide: /* For the impatiens: quick cron run and final reporting */

2023-04-12T08:56:11Z

For the impatiens: quick cron run and final reporting

← Older revision		Revision as of 08:56, 12 April 2023
Line 120:		Line 120:
	$cat bin/scripts/yambo_validation.tcsh		$cat bin/scripts/yambo_validation.tcsh
	#!/usr/bin/tcsh		#!/usr/bin/tcsh
	$cd /home/marini/Yambo/sources/svn/yambo-tests/test-suite		cd /home/marini/Yambo/sources/svn/yambo-tests/test-suite
	$./driver.pl -flow $argv[1] -report		./driver.pl -flow $argv[1] -report

	That's all you need.		That's all you need.

Davide: Style improved

2023-04-12T08:55:46Z

Style improved

Show changes

Davide: /* Installation */ few improvements

2023-04-12T08:53:27Z

Installation: few improvements

← Older revision		Revision as of 08:53, 12 April 2023
Line 13:		Line 13:

	$git clone https://github.com/yambo-code/yambo-tests.git yambo-tests		$git clone https://github.com/yambo-code/yambo-tests.git yambo-tests

			you may need to provide your GitHub username and password.

			Then init and update the ROBOTS submodule

	$cd yambo-tests		$cd yambo-tests
	$git submodule init		$git submodule init
Line 20:		Line 25:
	$cd ..		$cd ..

	~~you may need to provide your GitHub username and password.~~		After the first thing to do is the configuration

	After ~~the checkout~~ the first thing to do is the configuration

	~~%cd test-suite~~		$./configure --with-yambo=/home/marini/Yambo/yambo/master/
	%./configure --with-yambo=/home/marini/Yambo/yambo/master/

	If the configuration works you should see something similar to the following message:		If the configuration works you should see something similar to the following message:

	%./configure --with-yambo=/home/marini/Yambo/yambo/master/		$./configure --with-yambo=/home/marini/Yambo/yambo/master/
	%checking build system type... x86_64-unknown-linux-gnu		checking build system type... x86_64-unknown-linux-gnu
	%checking host system type... x86_64-unknown-linux-gnu		checking host system type... x86_64-unknown-linux-gnu
	%checking the anomaly.mlib.ism.cnr.it ROBOT... created		checking the anomaly.mlib.ism.cnr.it ROBOT... created
	~~%checking~~ for nccopy... no		hecking for nccopy... no
	%checking for ncftp... ncftp		checking for ncftp... ncftp
	%checking for ncftpls... ncftpls		checking for ncftpls... ncftpls
	%checking for ncftpput... ncftpput		checking for ncftpput... ncftpput
	%checking for awk... awk		checking for awk... awk
	%checking for txt2html... txt2html		checking for txt2html... txt2html
	%checking the Yambo source... /home/marini/Yambo/yambo/master/		checking the Yambo source... /home/marini/Yambo/yambo/master/
	%configure: creating ./config.status		configure: creating ./config.status
	%config.status: creating config/MODULES.pl		config.status: creating config/MODULES.pl
	%config.status: creating config/TOOLS.pl		config.status: creating config/TOOLS.pl

	=== Robot informations ===		=== Robot informations ===
Line 48:		Line 50:
	By typing		By typing

	%./driver.pl -i		$./driver.pl -i

	you will see some basic info about your machine. This command is useful to see the available flows, configurations and so on. An example is		you will see some basic info about your machine. This command is useful to see the available flows, configurations and so on. An example is

Davide: /* Installation */ Added info for ROBOTS submodule init and update

2023-04-12T08:51:54Z

Installation: Added info for ROBOTS submodule init and update

← Older revision		Revision as of 08:51, 12 April 2023
Line 12:		Line 12:
	The test suite is available on GitHub via git		The test suite is available on GitHub via git

	%git clone https://github.com/yambo-code/yambo-tests.git yambo-tests		$git clone https://github.com/yambo-code/yambo-tests.git yambo-tests
			$cd yambo-tests
			$git submodule init
			$git submodule update
			$cd ROBOTS
			$git checkout master
			$cd ..

	you may need to provide your GitHub username and password.		you may need to provide your GitHub username and password.

Claudio at 10:27, 4 December 2020

2020-12-04T10:27:30Z

← Older revision		Revision as of 10:27, 4 December 2020
Line 502:		Line 502:

	It's now enough that you push and the new test will be ready!		It's now enough that you push and the new test will be ready!


	~~== Troubleshooting ==~~


	* If you link external libraries please be sure to copy ''ncdump'' and ''nccopy'' in the Yambo bin folder

	* do not forget to create the BRANCHES file in ROBOTS/hostname/usernames/BRANCHES with the folder and the name of your branch like
	~~/home/attacc/SOFTWARE/yambo-bugfixes bugfixes~~

	* In order to make test-suite works properly you need to add ssh-key in GitHub and clone the code using SSH and not HTTPS

	* Be sure that the following packages are installed on your pc: ncftp, ncftpls, ncftput, wget, git, awk, txt2html, rsync

	* If you want to test a branch and then upload the result on the web, it is important to use -branch branch_name when you perform the test otherwise the script will put the results of all branches in the same report and the upload will not work properly

	* If you use a script in the crontab do not forget to add the path of all libraries in the script and to load the MKL variables.

Attacc: /* Troubleshooting */

2020-11-10T08:06:35Z

Troubleshooting

← Older revision		Revision as of 08:06, 10 November 2020
Line 517:		Line 517:

	* If you want to test a branch and then upload the result on the web, it is important to use -branch branch_name when you perform the test otherwise the script will put the results of all branches in the same report and the upload will not work properly		* If you want to test a branch and then upload the result on the web, it is important to use -branch branch_name when you perform the test otherwise the script will put the results of all branches in the same report and the upload will not work properly

			* If you use a script in the crontab do not forget to add the path of all libraries in the script and to load the MKL variables.

Attacc: /* Troubleshooting */

2020-11-09T09:38:50Z

Troubleshooting

← Older revision		Revision as of 09:38, 9 November 2020
Line 516:		Line 516:
	* Be sure that the following packages are installed on your pc: ncftp, ncftpls, ncftput, wget, git, awk, txt2html, rsync		* Be sure that the following packages are installed on your pc: ncftp, ncftpls, ncftput, wget, git, awk, txt2html, rsync

	* If you want to test a branch and then upload the result on the web, it is important to use -branch branch_name when you perform the test		* If you want to test a branch and then upload the result on the web, it is important to use -branch branch_name when you perform the test otherwise the script will put the results of all branches in the same report and the upload will not work properly
	otherwise the script will put the results of all branches in the same report and the upload will not work properly

← Older revision		Revision as of 08:56, 12 April 2023
Line 213:		Line 213:

	=== Parallel Options ===		=== Parallel Options ===
	% (parallel options)		(parallel options)
	% -np <N> Fixed number of CPU used		-np <N> Fixed number of CPU used
	% -np_min <N> Minimum number of CPU used		-np_min <N> Minimum number of CPU used
	% -np_max <N> Maximum number of CPU used		-np_max <N> Maximum number of CPU used
	% -nt <T> # of OMP threads		-nt <T> # of OMP threads
	% -nl <L> # of CPU used for linear algebra		-nl <L> # of CPU used for linear algebra
	% -def_par Use the default parallelization scheme		-def_par Use the default parallelization scheme
	% -rand_par Use randomly generated parallel structures		-rand_par Use randomly generated parallel structures

	Examples:		Examples:

	%./driver.pl -tests Dummy -force -np 2		$./driver.pl -tests Dummy -force -np 2

	produces all possible combinations of 2 cpu's for the Dummy tests. Each run is labelled in such a way to be unique. The Dummy folder will look like		produces all possible combinations of 2 cpu's for the Dummy tests. Each run is labelled in such a way to be unique. The Dummy folder will look like

	~~%%l~~ tests/Dummy/		$ls tests/Dummy/
	%01_init-Nmpi2-1-master/ 02_hf-Nmpi2-3-master/ 03_optics-Nmpi2-3-master/ 04_em1s-Nmpi2-3-master/ INPUTS/ yambo.in		01_init-Nmpi2-1-master/ 02_hf-Nmpi2-3-master/ 03_optics-Nmpi2-3-master/ 04_em1s-Nmpi2-3-master/ INPUTS/ yambo.in
	%02_hf 03_optics 04_em1s 04_em1s-Nmpi2-4-master/ LOG/		02_hf 03_optics 04_em1s 04_em1s-Nmpi2-4-master/ LOG/
	%02_hf-Nmpi2-1-master/ 03_optics-Nmpi2-1-master/ 04_em1s-Nmpi2-1-master/ BROKEN REFERENCE/		02_hf-Nmpi2-1-master/ 03_optics-Nmpi2-1-master/ 04_em1s-Nmpi2-1-master/ BROKEN REFERENCE/
	%02_hf-Nmpi2-2-master/ 03_optics-Nmpi2-2-master/ 04_em1s-Nmpi2-2-master/ Dummy.tar.gz SAVE/		02_hf-Nmpi2-2-master/ 03_optics-Nmpi2-2-master/ 04_em1s-Nmpi2-2-master/ Dummy.tar.gz SAVE/

	Note that each run is labelled by the number of MPI cpus ('''Nmpi2''') and by the increasing counter of potential combinations of the two cpu's ('''-1-master,-2-master,...''').		Note that each run is labelled by the number of MPI cpus ('''Nmpi2''') and by the increasing counter of potential combinations of the two cpu's ('''-1-master,-2-master,...''').
Line 240:		Line 240:
	* MPI, default parallelization (no cycle)		* MPI, default parallelization (no cycle)

	%./driver.pl -tests Dummy -force -np 2 -def_par		$./driver.pl -tests Dummy -force -np 2 -def_par

	* MPI, random parallelization (no cycle, good for testing)		* MPI, random parallelization (no cycle, good for testing)

	%./driver.pl -tests Dummy -force -np 2 -rand_par		$./driver.pl -tests Dummy -force -np 2 -rand_par

	* MPI, using 2 and 4 cpu's, no cycle on combinations, using random parallelization		* MPI, using 2 and 4 cpu's, no cycle on combinations, using random parallelization

	%./driver.pl -tests Dummy -force -np_min 2 -np_max 4 -rand_par		$./driver.pl -tests Dummy -force -np_min 2 -np_max 4 -rand_par

	* OpenMP (if compiled with OpenMP)		* OpenMP (if compiled with OpenMP)

	%./driver.pl -tests Dummy -force -nt 2		$./driver.pl -tests Dummy -force -nt 2

	* MPI+SLK		* MPI+SLK

	%./driver.pl -tests Dummy -force -np 4 -nl 4 -def_par		$./driver.pl -tests Dummy -force -np 4 -nl 4 -def_par

	== Tests selection ==		== Tests selection ==