Page 1 of 1
how to run internal test "make testin_1" etc
Posted: Sun May 12, 2013 9:11 am
by weitong
I am beginner with abinit.
Yestoday I just finished the installation with the help from this forums.
Today I continue to work on it following the installation notes from the web
Code: Select all
http://www.abinit.org/documentation/helpfiles/for-v7.2/install_notes/install.html
Come to the third part:
3. How to make the internal tests?Code: Select all
[weitong@localhost abinit-7.2.1]$ make testin_1
I serached the abinit folder, found some files named test "testin_v1.in" , "testin_v5.in", "testin_bigdft.in", etc, in ~ /abinit-7.2.1/tets/built-in/Input. But there is no "testin_1" or "test_in".
PS: my installation steps:
1.export LD_LIBRARY_PATH=/usr/lib64/openmpi/lib:$LD_LIBRARY_PATH
2. $ ./configure --enable-mpi --with-mpi-prefix=/usr/lib64/openmpi/ --with-tardir=/home/weitong/.abinit/tarballs/
3. make mj4
4. make install
5. export LD_LIBRARY_PATH=/usr/lib64/openmpi/lib:$LD_LIBRARY_PATH
Re: how to run internal test "make testin_1" etc [SOLVED]
Posted: Sun May 12, 2013 11:29 am
by gmatteo
serached the abinit folder, found some files named test "testin_v1.in" , "testin_v5.in", "testin_bigdft.in", etc, in ~ /abinit-7.2.1/tets/built-in/Input. But there is no "testin_1" or "test_in".
There's a typo in the documentation. Use
make testin_v1
make testin_v5
make testin_bigdft
...
BTW:
make without arguments will give the list of available options
Re: how to run internal test "make testin_1" etc
Posted: Sun May 12, 2013 11:46 am
by weitong
Got it.
Thanks!
Re: how to run internal test "make testin_1" etc
Posted: Thu Mar 09, 2017 10:02 pm
by dumindasamarakoon
I installed abinit-7.4.1, using the following set of commands in a linux server.
1. Download, gunzip and untar the latest version.
2. ./configure
3. make
4. make install
Then I run the command
.
I got the following error message,
Code: Select all
make: *** No rule to make target `testin_v1'. Stop.
But,
command output the following message,
Code: Select all
make basic_tests
make[1]: Entering directory `/root/Downloads/abinit-7.4.1'
cd ./tests && make tests_in
make[2]: Entering directory `/root/Downloads/abinit-7.4.1/tests'
make testin_fast testin_v1 testin_v5 testin_bigdft testin_etsf_io testin_libxc testin_wannier90
make[3]: Entering directory `/root/Downloads/abinit-7.4.1/tests'
echo "Running built-in test in_fast"
Running built-in test in_fast
timeout="0" perl ./Scripts/run-basic-tests.pl built-in in_fast /root/Downloads/abinit-7.4.1/tests
Status file, reporting on built-in test fast
==> The run finished cleanly.
Moreover, comparison of the total energy, and other (few) relevant quantities with reference values has been successful.
This does not mean that no problem is present, however.
Please run the complete set of ABINIT tests to gain a better confidence in your installation.
echo "Running built-in test in_v1"
Running built-in test in_v1
timeout="0" perl ./Scripts/run-basic-tests.pl built-in in_v1 /root/Downloads/abinit-7.4.1/tests
Status file, reporting on built-in test v1
==> The run finished cleanly.
Moreover, comparison of the total energy, and other (few) relevant quantities with reference values has been successful.
This does not mean that no problem is present, however.
Please run the complete set of ABINIT tests to gain a better confidence in your installation.
echo "Running built-in test in_v5"
Running built-in test in_v5
timeout="0" perl ./Scripts/run-basic-tests.pl built-in in_v5 /root/Downloads/abinit-7.4.1/tests
Status file, reporting on built-in test v5
==> The run finished cleanly.
Moreover, comparison of the total energy, and other (few) relevant quantities with reference values has been successful.
This does not mean that no problem is present, however.
Please run the complete set of ABINIT tests to gain a better confidence in your installation.
make[3]: Nothing to be done for `testin_bigdft'.
make[3]: Nothing to be done for `testin_etsf_io'.
make[3]: Nothing to be done for `testin_libxc'.
make[3]: Nothing to be done for `testin_wannier90'.
make[3]: Leaving directory `/root/Downloads/abinit-7.4.1/tests'
make[2]: Leaving directory `/root/Downloads/abinit-7.4.1/tests'
make[1]: Leaving directory `/root/Downloads/abinit-7.4.1'
What could be the issue with the testin_v1 ?
Re: how to run internal test "make testin_1" etc
Posted: Sun Mar 26, 2017 5:51 pm
by thelifeofapanca
gmatteo wrote: serached the abinit folder, found some files named test "testin_v1.in" , "testin_v5.in", "testin_bigdft.in", etc, in ~ /abinit-7.2.1/tets/built-in/Input. But there is no "testin_1" or "test_in".
There's a typo in the documentation. Use
make testin_v1
make testin_v5
make testin_bigdft
...
BTW:
make without arguments will give the list of available options
Great thx!