ENCUTGW: Difference between revisions
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
{ \epsilon_{n'{\mathbf{k}}+{\mathbf{q}}}-\epsilon_{n{\mathbf{k}}} - \omega - i \eta }- </math> | { \epsilon_{n'{\mathbf{k}}+{\mathbf{q}}}-\epsilon_{n{\mathbf{k}}} - \omega - i \eta }- </math> | ||
The {{TAG|ENCUTGW}} controls how many | The {{TAG|ENCUTGW}} controls how many <math>\mathbf{G}</math> vectors are included in the | ||
the response function | the response function <math>\chi_{{\mathbf{q}}}^0 ({\mathbf{G}}, {\mathbf{G}}', \omega)</math>. | ||
Tests have shown that choosing {\tt ENCUTGW}={\tt ENCUT} yields | Tests have shown that choosing {\tt ENCUTGW}={\tt ENCUT} yields |
Revision as of 14:32, 14 January 2017
ENCUTGW = [real] (energy cutoff for response function
Default: ENCUTGW = ENCUT
The parameter ENCUTGW controls the basis set for the response functions in exactly the same manner as ENCUT does for the orbitals. In the GW case, updates of the response function dominate the computational work load:
The ENCUTGW controls how many vectors are included in the the response function .
Tests have shown that choosing {\tt ENCUTGW}={\tt ENCUT} yields essentially exact results. In principle, however, the response function contains contributions up to twice the plane wave cutoff $G_{\rm cut}$ (see Sec. \ref{algo-wrap}). Since the diagonal of the dielectric matrix converges rapidly to one, such a large cutoff is never actually required (the present release has only been tested for {\tt ENCUTGW} $\le$ {\tt ENCUT}, and might crash if {\tt ENCUTGW} $\ge$ {\tt ENCUT}). Furthermore, in most cases, it is even possible to set {\tt ENCUTGW} to a value between 150 to 200 eV, and even 100 eV gives usually QP shifts that are accurate to within a few hundreds of an eV (0.01-0.02 eV). This can help to speed up the calculations significantly and reduces the memory requirements substantially.
\index{INCAR!P!PRECFOCK|textit}
The flag {\tt PRECFOCK} (Sec.~\ref{incar-precfock}),
determines the FFT grid in all GW (and Hartree-Fock) related routines.
For small systems (which are often dominated by FFT operations),
it can have a significant impact on the compute time for
QP calculations. For large systems, the FFT's usually do not
dominating the computational work load and savings are expected to be small for {\tt PRECFOCK = fast }.
QP shifts are usually not very sensitive to the setting of {\tt PRECFOCK}
(and it therefore does not harm to set {\tt PRECFOCK = fast }), whereas for
RPA calculations we recommend to set {\tt PRECFOCK= normal} to avoid numerical errors.