LWANNIER90 RUN: Difference between revisions
No edit summary |
|||
| Line 15: | Line 15: | ||
{{TAG|LWANNIER90}}, | {{TAG|LWANNIER90}}, | ||
{{TAG|LWRITE_MMN_AMN}}, | {{TAG|LWRITE_MMN_AMN}}, | ||
{{TAG|LWRITE_UNK}} | {{TAG|LWRITE_UNK}}, | ||
{{TAG|NUM_WANN}} | |||
{{sc|LWANNIER90_RUN|Examples|Examples that use this tag}} | {{sc|LWANNIER90_RUN|Examples|Examples that use this tag}} | ||
Revision as of 06:09, 5 November 2021
LWANNIER90_RUN = .TRUE. | .FALSE.
Default: LWANNIER90_RUN = .FALSE.
Description: LWANNIER90_RUN executes wannier_setup (see LWANNIER90=.TRUE.) and subsequently runs WANNIER90 in library mode (wannier_run).
For details on the execution of wannier_setup in VASP, see the description of the LWANNIER90-tag. For information on the many tags one may set in the wannier90.win file to control the execution of WANNIER90 (be it standalone or in library mode) we refer to the WANNIER90 manual.
Mind: when running WANNIER90 in library mode, the wannier90.mmn and wannier90.amn files are not written. The information these files normally contain is passed on to wannier_run internally. If you want these files to be written anyway, for instance to be able to run WANNIER90 standalone later on, one should add
LWRITE_MMN_AMN=.TRUE.
to the INCAR file.
Related Tags and Sections
LWANNIER90, LWRITE_MMN_AMN, LWRITE_UNK, NUM_WANN