LIBXC1: Difference between revisions

From VASP Wiki
No edit summary
No edit summary
Line 27: Line 27:
  {{TAG|LIBXC2}} = MGGA_C_SCAN
  {{TAG|LIBXC2}} = MGGA_C_SCAN


<references>
<ref name="libxc">https://www.tddft.org/programs/libxc/]</ref>
</references>


== Related Tags and Sections ==
== Related Tags and Sections ==

Revision as of 09:42, 21 December 2021

LIBXC1 = [integer] or [string] 

Description: LIBXC1 and LIBXC2 specify the functionals from the library of exchange-correlation functionals [1][2] that one wants to use.


LIBXC1 and LIBXC2 can be either integers or strings. The available functionals are listed on the Libxc website[3] and are essentially of three types: exchange (_X_), correlation (_C_) or exchange-correlation (_XC_). The possibilities for LIBXC1 and LIBXC2 are the following:

  • Both LIBXC1  and LIBXC2  are specified and correspond to the exchange (_X_) and correlation (_C_) functionals, respectively, or the reverse.
  • Only LIBXC1  (or LIBXC2 ) is specified and corresponds to an exchange (_X_) or exchange-correlation (_XC_) functional. It can also be a correlation (_C_) functional, but such a calculation without exchange would not make sense. Examples of how to specify a Libxc functional in INCAR are given below for the PBE[4] and SCAN functionals[5].
  • PBE
GGA = LIBXC
LIBXC1 = 101
LIBXC2 = 130

or

GGA = LIBXC
LIBXC1 = GGA_X_PBE
LIBXC2 = GGA_C_PBE
  • SCAN
METAGGA = LIBXC
LIBXC1 = 101
LIBXC2 = 130

or

METAGGA = LIBXC
LIBXC1 = MGGA_X_SCAN
LIBXC2 = MGGA_C_SCAN

Related Tags and Sections

AGGAX, AGGAC, ALDAC, LHFCALC, hybrid functionals, settings for specific hybrid functionals

Examples that use this tag