HPC/Applications/vasp

Requesting Access

VASP versions 4, 5, and 6 are is available on Carbon, subject to confirmation for your group having a license for VASP major versions 4, 5, or 6.

To use VASP binaries on Carbon, send me (M. Sternberg), the following for the persons on your VASP license group who will be using VASP on Carbon:

• For each person:
  • Full name
  • Email address that the person registered with at vasp.at

Module considerations

• Review the available modules for each major version:
  • vasp, for VASP 4.x
  • vasp5, for VASP 5.x
  • vasp6, for VASP 6.x
• Choose and add one of the following lines to your ~/.bashrc file:

module load --auto vasp                # sets $VASP_HOME
module load --auto vasp5               # sets $VASP5_HOME
module load --auto vasp6               # sets $VASP6_HOME

Each module points to an installation directory using an environment variable corresponding to the module name. Do not hardcode the directory anywhere, as that location is determined by the module and may change in subsequent versions. There should not be a reason to do so, since $PATH will be managed appropriately.

• Each module provides several binaries (see next section).
• You do not need to specify a path for vasp for the mpirun statement in the PBS job script.
• The modules are mutually exclusive.
• Potentials are available in /opt/soft/vasp-pot.

To access Graeme Henkelman's script suite, load the vasp-vtstscripts module. It works with both the vasp and vasp5 modules above. In either case, choose one of the VTST-patched binaries from the table below. The unpatched vasp binaries will not interoperate with the script suite.

module load vasp-vtstscripts

Binaries

Some options for VASP cannot be configured at runtime (by input data) but must be chosen when compiling. Since no single set of compile-time choices is appropriate for all uses, a number of binaries are provided, distinguished by their name.

The modules from versions vasp/4.6.35-mkl-13 and vasp5/5.2.12a-mkl-4 onwards, respectively, contain several binaries built using different sets of preprocessor flags in the Makefile. Earlier modules only contain two binaries, vasp and vasp-gamma. Additional binaries are provided for useful preprocessor flag combinations after applying patches from the group of Graeme Henkelman (UT Austin) to the source code:

• Transition state tools for VASP, and
• DOS Projection in Bader Volumes.

To verify the binaries available for a module, run the appropriate command, once the module has been loaded:

ls $VASP_HOME/bin   # for VASP-4 (previous major version)
ls $VASP5_HOME/bin

Choose a binary appropriate for your task and pass its name to mpirun in the job script. There is no need for full path names. Copy a sample job script from:

$VASP_HOME/vasp.job   # for VASP-4 (previous major version)
$VASP5_HOME/vasp.job

Available binaries and their compile-time flags used

This table lists the names of the binaries compiled from

• combinations of preprocessor flags, and
• variants of the source code, primarily enhancing capabilities of ionic updates.

Versions and capabilities	Flags used	Binary names
		Official	Constrained Cell relaxation1	Patched for VTST2	Patched for Bader-projected DOS3
Conventional, Versions 4.x–5.3	(none)	vasp	vasp-cellz	vasp-vtst	vasp-baderdos
	-DNGZhalf	vasp-chargehalf	vasp-cellz-chargehalf	vasp-vtst-chargehalf	vasp-baderdos-chargehalf
	-DwNGZhalf	vasp-gamma	vasp-cellz-gamma	vasp-vtst-gamma	vasp-baderdos-gamma
	-DwNGZhalf -DNGZhalf	vasp-gamma-chargehalf	vasp-cellz-gamma-chargehalf	vasp-vtst-gamma-chargehalf	vasp-baderdos-gamma-chargehalf
Advanced MD techniques,4 Versions 5.2 and 5.3	-Dtbdyn	vasp-tbdyn	–	–	not useful
	-Dtbdyn -DNGZhalf	vasp-tbdyn-chargehalf
	-Dtbdyn -DwNGZhalf	vasp-tbdyn-gamma
	-Dtbdyn -DwNGZhalf -DNGZhalf	vasp-tbdyn-gamma-chargehalf
Version 5.44,5	-Dtbdyn	vasp_ncl	(–o–)5	vasp_vtst_ncl	TBD
	-Dtbdyn -DNGZhalf	vasp_std		vasp_vtst_std
	-Dtbdyn -DwNGZhalf -DNGZhalf	vasp_gam		vasp_vtst_gam
	(GPU6)	vasp_gpu_ncl		vasp_vtst_gpu_ncl
	(GPU6) -DNGZhalf	vasp_gpu		vasp_vtst_gpu
Version 6 (prelim.)		vasp_ncl	(–o–)5	vasp_vtst_ncl	TBD
		vasp_std		vasp_vtst_std
		vasp_gam		vasp_vtst_gam

¹) Stress tensor selectively zeroed in subroutine CONSTR_CELL_RELAX
²) http://theory.cm.utexas.edu/vtsttools/ . The dimer method was broken for vasp5/5.3.3 prior to 5.3.3p3-mkl-2.
³) http://theory.cm.utexas.edu/vtsttools/dos/ (now defunct)
⁴) http://cms.mpi.univie.ac.at/vasp/vasp/Advanced_MD_techniques.html
⁵) Axis-selective constrained cell relaxation, controlled via an optional input file CELL_RELAX, is compiled into all binaries.
⁶) http://cms.mpi.univie.ac.at/wiki/index.php/GPU_port_of_VASP

Explanation of flags

• File vasp.5.2/makefile.linux_pg in the souce code explains:

#-----------------------------------------------------------------------
# possible options for CPP:
# NGXhalf             charge density   reduced in X direction
# wNGXhalf            gamma point only reduced in X direction
# avoidalloc          avoid ALLOCATE if possible
# IFC                 work around some IFC bugs
# CACHE_SIZE          1000 for PII,PIII, 5000 for Athlon, 8000 P4
# RPROMU_DGEMV        use DGEMV instead of DGEMM in RPRO (usually  faster)
# RACCMU_DGEMV        use DGEMV instead of DGEMM in RACC (faster on P4)
#  **** definitely use -DRACCMU_DGEMV if you use the mkl library
#-----------------------------------------------------------------------
…
#-----------------------------------------------------------------------
# additional options for CPP in parallel version (see also above):
# NGZhalf               charge density   reduced in Z direction
# wNGZhalf              gamma point only reduced in Z direction
# scaLAPACK             use scaLAPACK (usually slower on 100 Mbit Net)
#-----------------------------------------------------------------------

• In the new build system (since version 5.4) the direct use of the -D*NG*half options has been replaced by predefined make(1) arguments VERSION={std,gam,ncl}.

Common flags

-DIFC -DRPROMU_DGEMV  -DRACCMU_DGEMV -DCACHE_SIZE=16000  -DMPI -DMPI_BLOCK=8000

General patches

The following modifications have been applied and are active in all binaries:

vdW-DF functional

The vdW-DF functional of Langreth and Lundqvist et al. is implemented in all the *-chargehalf binaries of the vasp5 module, and all versions above 5.4.

No specific preparations are needed other than setting the INCAR flags as documented. The binaries will find the required precalculated kernel file vdw_kernel.bindat by means of the environment variable $VASP5_HOME which is set by the module.

This is a Carbon-specific extension.

Solvation Model

All binaries above build 5.4.1.3-8-* contain the VASPsol solvation model of the Hennig group at Univ. of Florida..

Constrained Cell Relaxation

Likewise, in all binaries above build 5.4.1.3-8-* the relaxation of the unit cell may be constrained along one or more axes by creating a supplementary input file CELL_RELAX. The subroutine CONSTR_CELL_RELAX, having been a placeholder in the original source files, was extended to read (and re-read) this file in each call and apply the containts to the force components of each basis vector. The performance impact from the multiple reads is expected to be minimal.

This is a Carbon-specific extension.

File format

  cell relaxation     - fixed string, for validation only, leading spaces ignored.
  ix iy iz            - 3 integer flags, indicating which cartesian components of the
                        basis vectors are allowed to be changed; 0 means no (fixed),
                        non-zero means yes (can change).

Examples

• To relax the entire cell (identical to default behavior):

  cell relaxation
  1 1 1

• To relax along z only:

  cell relaxation
  0 0 1

Output indicator

To indicate if your chosen VASP binary (a) looked for and (b) did or did not find the CELL_RELAX file, the subroutine CONSTR_CELL_RELAX will output one of the following each time it has been called:

CELL_RELAX not present: performing unconstrained unit cell relaxation

or:

CELL_RELAX: performing constrained unit cell relaxation in cartesian directions  1  0  1
Unit cell forces:
      1.1111111111111112       0.0000000000000000       2.2222222222222223
      0.0000000000000000       0.0000000000000000       0.0000000000000000
      2.2222222222222223       0.0000000000000000       3.3333333333333330

(The force values shown here are contrived.)

Author

Michael Sternberg.

Usage under ASE

VASP calculations can be set up, run, and analyzed using the calculator interface of the ASE package, available on Carbon under both the ase3 and atk modules. ASE is told how to use VASP by means of environment variables which the modules define for you with sensible defaults:

VASP_PP_PATH
VASP_COMMAND

• The calculator will create and possibly overwrite VASP input files in the current directory, and then run VASP therein. To minimize clutter, consider setting up and changing into a run-specific directory before initializing the calculator.
• VASP_COMMAND normally uses the vasp binary (see above), and will run in parallel when called under a PBS job. That decision is based on the PBS_NODEFILE environment variable being present.
• You can supply another executable name or path in the variable VASP_BINARY.
• The ASE calculator supports an alternative calling interface, a python script named in VASP_SCRIPT. This variable is not set by default on Carbon. If you wish to define a personal VASP_SCRIPT, unset VASP_COMMAND in tandem.
  • VASP_COMMAND takes precendence over VASP_SCRIPT.
  • The stdout stream is redirected to a file under VASP_COMMAND, but will appear on ASE's stdout under VASP_SCRIPT.
  • Inspect the calculator source code for details; see function run(self).

Usage under ATK/VNL

The ATK package (module atk) supports two different ways to interface with VASP.

1. The ase calculator interface – see previous section.
2. The VASPScripter AddOn.
   • The scripter "merely" helps you to set up the VASP input files in VNL, the ATK GUI. It does not start or analyze a VASP run.
   • The directory for pseudopotentials is preconfigured to be the same as $VASP_PP_PATH for the ASE calculator.

See also

• Advanced node selection