VASP
Overview
The Vienna Ab initio Simulation Package (VASP), is a package for performing ab initio quantum mechanical calculations using either Vanderbilt pseudopotentials, or the projector augmented wave method and a plane wave basis set.
VASP Homepage: Access to VASP News, Wiki, Support Forum and Portal
VASP Wiki: Menu
Please consult the VASP FAQ for more details regards licensing.
For Example: To whom are VASP licenses given?
VASP licenses are given to well-defined research groups only. They are not department-or institution-wide, also they are not personal licenses. All members of a VASP-group have to work in the same organizational unit (Department, Institute) at the same location.
VASP-licenses are not transferable from one research institution to another one. Any transfer of a license to another group at the same research institution has to be approved by the VASP Software GmbH explicitly.
Using
NOTE: VASP is NOT publicly available to users across the clusters. Instead, there are local installations per project with each project having its own license agreement. If ARCC comes across users abusing the licensing agreement we will have to act on it.
Multicore
Note: Although ARCC can assist in the functional setup and running of VASP on the cluster, we do leave the science up to the researchers.
With this in mind, there are a number of pages on the VASP Wiki that make suggestions on how best to configure simulation inputs with respect to nodes/cores, as well as memory considerations.
VASP Wiki:
NCORE: determines the number of compute cores that work on an individual orbital. Default:
NCORE = 1
NPAR determines the number of bands that are treated in parallel. Default: NPAR = number of cores
These are just a few, please look through the VASP Wiki for others. If you find further details, please pass them onto us and we can add them to this page.
ISTART: Related to starting a job and determines whether or not to read the WAVECAR file.
Others:
Yale: CRC: VASP
NSC: Selecting the Right Number of Cores for a VASP Calculation
Installation Guidelines
The basic process is to unpack the provided source tar file. Copy and update an appropriate arch/makefile.include.<version>
file, and then build.
Below is an example using a <version>
that ARCC believes is suitable. By all means select and try a different <version>
but you will need to select appropriate compilers and related libraries, as well as updating the makefile.include
.
With the example below, you will need to update <project-name>
appropriately.
MedicineBow: Version 6.3.2
You need to update the makefile.include
file. The following modifications have been made:
Commented out native compiling.
Have explicitly added the paths to
openblas
,scalapack
andfftw
.Building with, and thus adding paths to,
hdf5
andwannier90
.The
wannier90
library typically installs the actual library file in its parent folder, and not a sublib/
folder. This modifies themakefile.include
to:LLIBS += -L$(WANNIER90_ROOT)/ -lwannier
i.e thelib
folder is not included.
Compiling
fftlib
.
Note: If you wish to use a different make.include.your_choice
or try another process, then you’ll need to module load
potentially a different compiler, and build core libraries if not built for that chosen compiler.
Suggested Module File Creation
If you have installed under say: /project/<project-name>/software/vasp.6.3.2/
you could create the following:
Installation: Potential Issues
Bin Folder Executables: Permission Denied
If you get an error of the form:
Once built, the files in the bin
folder should be executable. Check they have the x
permission defined for the groups:
If you don’t then use chmod ugo+x <filename>
to update.