Input file variables

Attention

Work in progress…

Yambo input variables

A typical Yambo input file looks like this:

[...]
rim_cut              # [R] Coulomb potential
gw0                  # [R] GW approximation
el_el_corr           # [R] Electron-Electron Correlation
HF_and_locXC         # [R] Hartree-Fock
em1d                 # [R][X] Dynamically Screened Interaction
NLogCPUs=0           # [PARALLEL] Live-timing CPU`s (0 for all)
RandQpts=1000000     # [RIM] Number of random q-points in the BZ
CUTGeo= "slab z"     # [CUT] Coulomb Cutoff geometry: box/cylinder/sphere/ws/slab X/Y/Z/XY..
RandGvec= 5  Ry      # [RIM] Coulomb interaction RS components
NGsBlkXm= 1  Ry      # [Xm] Response block size
[...]

Note that each comment begins with a marker, for example [R], [RIM], [CUT] and so on. These markers identify different classes of variables that refer to specific sections of either the calculation or the code itself. In the following, all the variables are grouped according to their reference marker(s).

You may also notice that for some variables it is possible to specify the units: you will find the available options in the variable description.


Marker(s): [R]

These variables are used by the driver to determine what needs to be computed. To each runlevel is connected a set of input variables.

rim_cut, gw0

Marker(s): [RIM], [CUT]

These variables control the random integration method and the cutoff geometry of the Coulomb interaction.

RandQpts, …


Runlevels

Here all the variables related to the marker [R].

rim_cut
Description

> top

gw0
Description

> top


RIM and Coulomb cutoff

Here all the variables related to the markers [RIM] and [CUT].

RandQpts
Type: INTEGER
Units: RL
Default: 100..?

Number of random q-points in the BZ to perform Monte Carlo Integration.
Values like \(10^6\) can be used to ensure convergence.
Needed for non 3D system to avoid divergences for small \(q\), and needed to build cutoff potential with box shape.

Added in version 4.0: Brief explanation…

> top