1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--Converted with LaTeX2HTML 2019.2 (Released June 5, 2019) -->
<HTML lang="EN">
<HEAD>
<TITLE>2.7 Running tests and examples</TITLE>
<META NAME="description" CONTENT="2.7 Running tests and examples">
<META NAME="keywords" CONTENT="user_guide">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="viewport" CONTENT="width=device-width, initial-scale=1.0">
<META NAME="Generator" CONTENT="LaTeX2HTML v2019.2">
<LINK REL="STYLESHEET" HREF="user_guide.css">
<LINK REL="next" HREF="node15.html">
<LINK REL="previous" HREF="node13.html">
<LINK REL="next" HREF="node15.html">
</HEAD>
<BODY >
<!--Navigation Panel-->
<A
HREF="node15.html">
<IMG WIDTH="37" HEIGHT="24" ALT="next" SRC="next.png"></A>
<A
HREF="node7.html">
<IMG WIDTH="26" HEIGHT="24" ALT="up" SRC="up.png"></A>
<A
HREF="node13.html">
<IMG WIDTH="63" HEIGHT="24" ALT="previous" SRC="prev.png"></A>
<A ID="tex2html188"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALT="contents" SRC="contents.png"></A>
<BR>
<B> Next:</B> <A
HREF="node15.html">2.8 Installation tricks and</A>
<B> Up:</B> <A
HREF="node7.html">2 Installation</A>
<B> Previous:</B> <A
HREF="node13.html">2.6 Compilation</A>
<B> <A ID="tex2html189"
HREF="node1.html">Contents</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A ID="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL>
<LI><A ID="tex2html190"
HREF="node14.html#SECTION00037100000000000000">2.7.1 Test-suite</A>
<LI><A ID="tex2html191"
HREF="node14.html#SECTION00037200000000000000">2.7.2 Examples</A>
</UL>
<!--End of Table of Child-Links-->
<HR>
<H2><A ID="SECTION00037000000000000000"></A>
<A ID="SubSec:Examples"></A>
<BR>
2.7 Running tests and examples
</H2>
<P>
As a final check that compilation was successful, you may want to run some or
all of the tests and examples.
Notice that most tests and examples are devised to be run serially
or on a small number of processors; do not use tests and examples
to benchmark parallelism, do not try to run on too many processors.
<P>
<H3><A ID="SECTION00037100000000000000">
2.7.1 Test-suite</A>
</H3>
Automated tests give a "pass/fail" answer. All tests run quickly
(less than a minute at most), but they are not meant to be realistic,
just to test a specific case. Many features are tested but only for
the following codes: <TT>pw.x</TT>, <TT>cp.x</TT>, <TT>ph.x</TT>, <TT>epw.x</TT>.
Instructions for the impatient:
<PRE>
cd test-suite
make run-tests
</PRE>
Instructions for all others: go to the <TT>test-suite/</TT> directory,
read the <TT>README</TT> file, or at least, type <TT>make</TT>. You may need
to edit the <TT>run-XX.sh</TT> shells, defining variables
<TT>PARA_PREFIX</TT> and <TT>PARA_POSTFIX</TT> (see below for their
meaning).
<P>
<H3><A ID="SECTION00037200000000000000">
2.7.2 Examples</A>
</H3>
There are many examples and reference data for almost every piece of Q<SMALL>UANTUM </SMALL>ESPRESSO,
but you have to manually inspect the results.
<P>
In order to use examples, you should edit file <TT>environment_variables</TT>,
setting the following variables as needed.
<BLOCKQUOTE>
BIN_DIR: directory where executables reside
<BR>
PSEUDO_DIR: directory where pseudopotential files reside
<BR>
TMP_DIR: directory to be used as temporary storage area
</BLOCKQUOTE>
The default values of BIN_DIR and PSEUDO_DIR should be fine,
unless you have installed things in nonstandard places. TMP_DIR
must be a directory where you have read and write access to, with
enough available space to host the temporary files produced by the
example runs, and possibly offering high I/O performance (i.e., don't
use an NFS-mounted directory). NOTA BENE: do not use a
directory containing other data: the examples will clean it!
<P>
If you have compiled the parallel version of Q<SMALL>UANTUM </SMALL>ESPRESSO (this
is the default if parallel libraries are detected), you will usually
have to specify a launcher program (such as <TT>mpirun</TT> or
<TT>mpiexec</TT>) and the number of processors: see Sec.<A HREF="node17.html#Sec:para">3</A> for
details. In order to do that, edit again the <TT>environment_variables</TT>
file and set the <TT>PARA_PREFIX</TT> and <TT>PARA_POSTFIX</TT> variables
as needed. Parallel executables will be run by a command like this:
<PRE>
$PARA_PREFIX pw.x $PARA_POSTFIX -i file.in > file.out
</PRE>
For example, if the command line is like this (as for an IBM SP):
<PRE>
poe pw.x -procs 4 -i file.in > file.out
</PRE>
you should set <TT>PARA_PREFIX="poe"</TT>, <TT>PARA_POSTFIX="-procs 4"</TT>.
Furthermore, if your machine does not support interactive use, you
must run the commands specified above through the batch queuing
system installed on that machine. Ask your system administrator for
instructions. For execution using OpenMP on N threads,
use <TT>PARA_PREFIX="env OMP_NUM_THREADS=N ... "</TT>.
<P>
To run an example, go to the corresponding directory (e.g.
<TT>PW/examples/example01</TT>) and execute:
<PRE>
./run_example
</PRE>
This will create a subdirectory <TT>results/</TT>, containing the input and
output files generated by the calculation. Some examples take only a
few seconds to run, while others may require up to several minutes.
<P>
In each example's directory, the <TT>reference/</TT> subdirectory contains
verified output files, that you can check your results against. They
were generated on a Linux PC using the Intel compiler. On different
architectures the precise numbers could be slightly different, in
particular if different FFT dimensions are automatically selected. For
this reason, a plain diff of your results against the reference data
doesn't work, or at least, it requires human inspection of the results.
<P>
The example scripts stop if an error is detected. You should look <EM>inside</EM>
the last written output file to understand why.
<P>
<HR>
<!--Navigation Panel-->
<A
HREF="node15.html">
<IMG WIDTH="37" HEIGHT="24" ALT="next" SRC="next.png"></A>
<A
HREF="node7.html">
<IMG WIDTH="26" HEIGHT="24" ALT="up" SRC="up.png"></A>
<A
HREF="node13.html">
<IMG WIDTH="63" HEIGHT="24" ALT="previous" SRC="prev.png"></A>
<A ID="tex2html188"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALT="contents" SRC="contents.png"></A>
<BR>
<B> Next:</B> <A
HREF="node15.html">2.8 Installation tricks and</A>
<B> Up:</B> <A
HREF="node7.html">2 Installation</A>
<B> Previous:</B> <A
HREF="node13.html">2.6 Compilation</A>
<B> <A ID="tex2html189"
HREF="node1.html">Contents</A></B>
<!--End of Navigation Panel-->
</BODY>
</HTML>
|
