File: INPUT_HP.xml

package info (click to toggle)
espresso 6.7-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 311,068 kB
  • sloc: f90: 447,429; ansic: 52,566; sh: 40,631; xml: 37,561; tcl: 20,077; lisp: 5,923; makefile: 4,503; python: 4,379; perl: 1,219; cpp: 761; fortran: 618; java: 568; awk: 128
file content (315 lines) | stat: -rw-r--r-- 11,065 bytes parent folder | download | duplicates (3)
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
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="input_xx.xsl"?>
<!-- FILE AUTOMATICALLY CREATED: DO NOT EDIT, CHANGES WILL BE LOST -->
    
<input_description distribution="Quantum Espresso" package="PWscf" program="hp.x" >
   <toc>
   </toc>
   <intro>
<b>Input data format:</b> { } = optional, [ ] = it depends, # = comment

<b>Structure of the input data:</b>
===============================================================================

<b>&amp;INPUTHP</b>
   ...
<b>/</b>
   </intro>
   <namelist name="INPUTHP" >
      <var name="prefix" type="CHARACTER" >
         <default> &apos;pwscf&apos;
         </default>
         <info>
Prepended to input/output filenames; must be the same
used in the calculation of unperturbed system.
         </info>
      </var>
      <var name="outdir" type="CHARACTER" >
         <default>
value of the <tt>ESPRESSO_TMPDIR</tt> environment variable if set;
<br/> current directory (&apos;./&apos;) otherwise
         </default>
         <info>
Directory containing input, output, and scratch files;
must be the same as specified in the calculation of
the unperturbed system.
         </info>
      </var>
      <var name="iverbosity" type="INTEGER" >
         <default> 1
         </default>
         <info>
= 1 : minimal output
= 2 : as above + symmetry matrices, final response
      matrices chi0 and chi1 and their inverse matrices,
      full U matrix
= 3 : as above + various detailed info about the NSCF
      calculation at k and k+q
= 4 : as above + response occupation matrices at every
      iteration and for every q point in the star
         </info>
      </var>
      <var name="max_seconds" type="REAL" >
         <default> 1.d7
         </default>
         <info>
Maximum allowed run time before the job stops smoothly.
         </info>
      </var>
      <vargroup type="INTEGER" >
         <var name="nq1" >
         </var>
         <var name="nq2" >
         </var>
         <var name="nq3" >
         </var>
         <default> 1,1,1
         </default>
         <info>
Parameters of the Monkhorst-Pack grid (no offset).
Same meaning as for nk1, nk2, nk3 in the input of pw.x.
         </info>
      </vargroup>
      <var name="skip_equivalence_q" type="LOGICAL" >
         <default> .false.
         </default>
         <info>
If .true. then the HP code will skip the equivalence
analysis of q points, and thus the full grid of q points
will be used. Otherwise the symmetry is used to determine
equivalent q points (star of q), and then perform
calculations only for inequivalent q points.
         </info>
      </var>
      <var name="determine_num_pert_only" type="LOGICAL" >
         <default> .false.
         </default>
         <see> find_atpert
         </see>
         <info>
If .true. determines the number of perturbations
(i.e. which atoms will be perturbed) and exits smoothly
without performing any calculation. For DFT+U+V, it also
determines the indices of inter-site couples.
         </info>
      </var>
      <var name="find_atpert" type="INTEGER" >
         <default> 1
         </default>
         <info>
Method for searching of atoms which must be perturbed.
1 = Find how many inequivalent Hubbard atoms there are
    by analyzing unperturbed occupations.
2 = Find how many Hubbard atoms to perturb based on
    how many different Hubbard atomic types there are.
    Warning: atoms which have the same type but which
    are inequivalent by symmetry or which have different
    occupations will not be distinguished in this case
    (use option 1 or 3 instead).
3 = Find how many inequivalent Hubbard atoms
    there are using symmetry. Atoms which have the
    same type but are not equivalent by symmetry will
    be distinguished in this case.
         </info>
      </var>
      <var name="docc_thr" type="REAL" >
         <default> 5.D-5
         </default>
         <info>
Threshold for a comparison of unperturbed occupations
which is needed for the selection of atoms which must
be perturbed. Can be used only when <ref>find_atpert</ref> = 1.
         </info>
      </var>
      <dimension name="skip_type" start="1" end="ntyp" type="LOGICAL" >
         <default> skip_type(i) = .false.
         </default>
         <see> equiv_type
         </see>
         <info>
<ref>skip_type</ref>(i), where i runs over types of atoms.
If <ref>skip_type</ref>(i)=.true. then no linear-response
calculation will be performed for the i-th atomic type:
in this case <ref>equiv_type</ref>(i) must be specified, otherwise
the HP code will stop. This option is useful if the
system has atoms of the same type but opposite spin
pollarizations (anti-ferromagnetic case).
This keyword cannot be used when <ref>find_atpert</ref> = 1.
         </info>
      </dimension>
      <dimension name="equiv_type" start="1" end="ntyp" type="INTEGER" >
         <default> equiv_type(i) = 0
         </default>
         <see> skip_type
         </see>
         <info>
<ref>equiv_type</ref>(i), where i runs over types of atoms.
<ref>equiv_type</ref>(i)=j, will make type i equivalent to type j
(useful when nspin=2). Such a merging of types is done
only at the post-processing stage.
This keyword cannot be used when <ref>find_atpert</ref> = 1.
         </info>
      </dimension>
      <dimension name="perturb_only_atom" start="1" end="ntyp" type="LOGICAL" >
         <default> perturb_only_atom(i) = .false.
         </default>
         <see> compute_hp
         </see>
         <info>
If <ref>perturb_only_atom</ref>(i)=.true. then only the i-th
atom will be perturbed and considered in the run.
This variable is useful when one wants to split
the whole calculation on parts.

<b>Note:</b> this variable has a higher priority than <ref>skip_type</ref>.
         </info>
      </dimension>
      <var name="start_q" type="INTEGER" >
         <default> 1
         </default>
         <see> last_q, sum_pertq
         </see>
         <info>
Computes only the q points from <ref>start_q</ref> to <ref>last_q</ref>.

<b>IMPORTANT:</b> <ref>start_q</ref> must be smaller or equal to
the total number of q points found.
         </info>
      </var>
      <var name="last_q" type="INTEGER" >
         <default> number of q points
         </default>
         <see> start_q, sum_pertq
         </see>
         <info>
Computes only the q points from <ref>start_q</ref> to <ref>last_q</ref>.

<b>IMPORTANT:</b> <ref>last_q</ref> must be smaller or equal to
the total number of q points found.
         </info>
      </var>
      <var name="sum_pertq" type="LOGICAL" >
         <default> .false.
         </default>
         <see> start_q, last_q, perturb_only_atom
         </see>
         <info>
If it is set to .true. then the HP code will collect
pieces of the response occupation matrices for all
q points. This variable should be used only when
<ref>start_q</ref>, <ref>last_q</ref> and <ref>perturb_only_atom</ref> are used.
         </info>
      </var>
      <var name="compute_hp" type="LOGICAL" >
         <default> .false.
         </default>
         <see> perturb_only_atom
         </see>
         <info>
If it is set to .true. then the HP code will collect
pieces of the chi0 and chi matrices (which must have
been produced in previous runs) and then compute
Hubbard parameters. The HP code will look for files
tmp_dir/HP/prefix.chi.i.dat. Note that all files
prefix.chi.i.dat (where i runs over all perturbed
atoms) must be placed in one folder tmp_dir/HP/.
<ref>compute_hp</ref>=.true. must be used only when the
calculation was parallelized over perturbations.
         </info>
      </var>
      <var name="conv_thr_chi" type="REAL" >
         <default> 1.D-5
         </default>
         <info>
Convergence threshold for the response function chi,
which is defined as a trace of the response
occupation matrix.
         </info>
      </var>
      <var name="thresh_init" type="REAL" >
         <default> 1.D-14
         </default>
         <info>
Initial threshold for the solution of the linear
system (first iteration). Needed to converge the
bare (non-interacting) response function chi0.
The specified value will be multiplied by the
number of electrons in the system.
         </info>
      </var>
      <var name="ethr_nscf" type="REAL" >
         <default> 1.D-11
         </default>
         <info>
Threshold for the convergence of eigenvalues during
the iterative diagonalization of the Hamiltonian in
the non-self-consistent-field (NSCF) calculation at
k and k+q points. Note, this quantity is NOT extensive.
         </info>
      </var>
      <var name="niter_max" type="INTEGER" >
         <default> 100
         </default>
         <info>
Maximum number of iterations in the iterative
solution of the linear-response Kohn-Sham equations.
         </info>
      </var>
      <var name="alpha_mix(i)" type="REAL" >
         <default> alpha_mix(1)=0.3
         </default>
         <info>
Mixing parameter (for the i-th iteration) for updating
the response SCF potential using the modified Broyden
method. See: D.D. Johnson, <a href="https://journals.aps.org/prb/abstract/10.1103/PhysRevB.38.12807">PRB 38, 12807 (1988)</a>.
         </info>
      </var>
      <var name="nmix" type="INTEGER" >
         <default> 4
         </default>
         <info>
Number of iterations used in potential mixing
using the modified Broyden method. See:
D.D. Johnson, <a href="https://journals.aps.org/prb/abstract/10.1103/PhysRevB.38.12807">PRB 38, 12807 (1988)</a>.
         </info>
      </var>
      <var name="num_neigh" type="INTEGER" >
         <default> 6
         </default>
         <info>
Number of nearest neighbors of every Hubbard atom which
will be considered when writting Hubbard V parameters to
the file parameters.out, which can be used in the
subsequent DFT+U+V calculation. This keyword is used only
when lda_plus_u_kind = 2 (post-processing stage).
         </info>
      </var>
      <var name="lmin" type="INTEGER" >
         <default> 2
         </default>
         <info>
Minimum value of the orbital quantum number of the Hubbard
atoms starting from which (and up to the maximum l in the
system) Hubbard V will be written to the file parameters.out.
<ref>lmin</ref> refers to the orbital quantum number of the atom
corresponding to the first site-index in Hubbard_V(:,:,:).
This keyword is used only when lda_plus_u_kind = 2 and only
in the post-processing stage. Example: <ref>lmin</ref>=1 corresponds to
writing to file V between e.g. oxygen (with p states) and its
neighbors, and including V between transition metals (with d
states) and their neighbors. Instead, when <ref>lmin</ref>=2 only the
latter will be written to parameters.out.
         </info>
      </var>
      <var name="rmax" type="REAL" >
         <default> 100.D0
         </default>
         <info>
Maximum distance (in Bohr) between two atoms to search
neighbors (used only at the postprocessing step when
lda_plus_u_kind = 2). This keyword is useful when there
are e.g. defects in the system.
         </info>
      </var>
   </namelist>
</input_description>