Choosing ENCUT, according to VASP Guide

Queries about input and output files, running specific calculations, etc.


Moderators: Global Moderator, Moderator

Post Reply
Message
Author
lahaye
Jr. Member
Jr. Member
Posts: 98
Joined: Fri Apr 14, 2006 5:08 am
Location: Suwon - Korea

Choosing ENCUT, according to VASP Guide

#1 Post by lahaye » Thu Sep 21, 2006 8:02 am

Hi all,

The VASP Guide says in
http://cms.mpi.univie.ac.at/vasp/vasp/node205.html
the following:

Code: Select all

There are some rules of thumb, which you should check
whenever making a calculation: For bulk materials the
number of plane waves per atom should be between 50-100.
A smaller basis set might result in serious errors. A larger basis
set is rarely necessary, and is a hint for a badly optimized
pseudopotential. If a large vacuum is included the number of
plane waves will be larger (i.e. 50% of your supercell
vacuum -> number of plane waves increases by a factor of 2).
I have a system of 11 atoms and the vacuum around is about
80 percent (using RWIGS in POTCAR to calculate volume occupied
by the atoms). The default settings for ENCUT is 400, which gives
a number of plane waves of around 244 (I averaged over the k-points).
This means 244/11 is approximately 22 plane waves/atom.
According to the above 'rule of thumb' this is far from accurate.
Is that the right conclusion?
And what is the factor when vacuum is 80 percent?


Furthermore, I have calculated the total energy of this system as
function of ENCUT, assuming that a larger ENCUT will use a larger
number of plane waves, which then should result in a more accurate
total energy. However, I get the following data:
http://surfion.snu.ac.kr/~lahaye/vasp/encut.jpg
The upper panel shows how the total energy varies with ENCUT,
and the lower panel shows the average number of plane waves
as function of ENCUT.
I expected that the total energy would gradually converge as
ENCUT is larger. However, it has a maximum first around
ENCUT=500 before convergence starts. I find this very strange!!!

By the way, when not giving ENCUT input explicity in INCAR, the
default is 400 (from POTCAR), which is exactly the ENCUT that is
equal to the converged total energy (at ENCUT > 800) before going
to the maximum. Is this where the VASP pseudo potential has made
a magical and very clever choice?

I hope somebody can help me understand better what is happening
here.

Thank you,
Rob.
Last edited by lahaye on Thu Sep 21, 2006 8:02 am, edited 1 time in total.

hra
Newbie
Newbie
Posts: 14
Joined: Wed Jun 15, 2005 11:23 am
Location: Yokohama, Japan

Choosing ENCUT, according to VASP Guide

#2 Post by hra » Thu Sep 21, 2006 3:04 pm

Instead of looking at total energy convergence, look how the energy difference of some reasonable configurations converges.
Last edited by hra on Thu Sep 21, 2006 3:04 pm, edited 1 time in total.

sondon
Newbie
Newbie
Posts: 8
Joined: Wed Nov 30, 2005 2:43 am
Location: USA

Choosing ENCUT, according to VASP Guide

#3 Post by sondon » Sun Sep 24, 2006 2:11 am

I have been heard that 10 meV/atom is one of rules of thumb for testing convergence in ENCUT tests.
<span class='smallblacktext'>[ Edited Sun Sep 24 2006, 04:15AM ]</span>
Last edited by sondon on Sun Sep 24, 2006 2:11 am, edited 1 time in total.

tjf
Full Member
Full Member
Posts: 107
Joined: Wed Aug 10, 2005 1:30 pm
Location: Leiden, Netherlands

Choosing ENCUT, according to VASP Guide

#4 Post by tjf » Sun Sep 24, 2006 12:36 pm

It depends on what you want to do the calculations for. For my applications 10 meV/atom is woefully insufficent and I converge stuff to around 1 meV per conventional unit cell (typically 18-96 atoms for my crystals).

However, achieving this level for many metals, for example, may be far too strenuous. As always, it's simply a case of being aware of the limitations of your calculations and thinking about what is sufficient/necessary for your purposes. Sometimes you need to take into consideration estimates of all the other (non convergence related) errors, other times the exact result for your "model" (DFT, PAW, etc.) is what you want.


<span class='smallblacktext'>[ Edited Mon Sep 25 2006, 11:03AM ]</span>
Last edited by tjf on Sun Sep 24, 2006 12:36 pm, edited 1 time in total.

Post Reply