Jump to content

Requests for technical support from the VASP team should be posted in the VASP Forum.

LWAVE: Difference between revisions

From VASP Wiki
No edit summary
No edit summary
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{TAGDEF|LWAVE|[logical]|.TRUE.}}
{{TAGDEF|LWAVE|[logical]|.TRUE.}}


Description: {{TAG|LWAVE}} determines whether the wavefunctions are written to the {{TAG|WAVECAR}} file at the end of a run.
Description: Determines whether the wavefunctions are written at the end of a run.
----


== Related Tags and Sections ==
The wavefunctions are written to the {{FILE|WAVECAR}} file by default. If {{TAG|LH5|T}}, the wavefunctions are written to the {{FILE|vaspwave.h5}} instead.
{{TAG|LCHARG}}
 
== Related tags and articles ==
{{FILE|WAVECAR}}, {{TAG|LH5}}, {{FILE|vaspwave.h5}}, {{TAG|LCHARG}}
 
 
{{sc|LWAVE|HowTo|Workflows that use this tag}}


{{sc|LWAVE|Examples|Examples that use this tag}}
----
[[The_VASP_Manual|Contents]]


[[Category:INCAR]]
[[Category:INCAR tag]][[Category:Electronic minimization]][[Category:Projector-augmented-wave method]]

Latest revision as of 07:53, 11 March 2026

LWAVE = [logical]
Default: LWAVE = .TRUE. 

Description: Determines whether the wavefunctions are written at the end of a run.


The wavefunctions are written to the WAVECAR file by default. If LH5 = T, the wavefunctions are written to the vaspwave.h5 instead.

Related tags and articles

WAVECAR, LH5, vaspwave.h5, LCHARG


Workflows that use this tag