The LDOS can be obtained at the same time using dos.ldos = true
. For example,
info.calculationType = 'dos'
info.savepath = 'results/c2_pdos'
dos.range = [-0.70,0.20]
dos.projL = [0,1]
dos.projM = [-1,0,1]
kpoint.gridn = [45,45,1]
kpoint.shift = [0,0,0]
kpoint.sampling = 'tetrahedron'
LCAO.status = 1
rho.in = 'results/c2_scf'
dos.ldos = true
Since pdos
is also activated by the keyword dos.projL
, the projected local DOS is also computed. The definitions for each PDOS is explained here. The LDOS and PLDOS are found in the HDF5 file which can be parsed as follows
h5disp('results/c2_pdos.h5')
You'll find them in /dos/pldosVal
.
The LDOS in RESCU is defined as in this equation. It's a field defined on a real space grid. Simply put, there is an infinitesimal real space charge at each energy. Some researchers are looking for how electronic charge looks at certain energies. If you sum over space, you get the DOS. If you sum over a certain energy range (mentioned in the link), you get the real space density. One can thus get the LDOS for a certain energy or energy interval.
Reading the VASP documentation on LORBIT, it appears that it is not computing the LDOS like we mean. LORBIT=11
computes the DOS and the site projected wave function character of each orbital. This information can be obtained computing the Mulliken population matrix as instructed here.
Thank you for your question.