VASP (Vienna Ab initio Simulation Package) is a computer program for atomic scale materials modelling, e.g. electronic structure calculations and quantum-mechanical molecular dynamics, from first principles.
VASP is licensed software, requiring the licensee to keep the vasp team updated with a list of user names. Thus, in order to use VASP arrange with the “vaspmaster” for your group to be put on the vasp licensed user list. Afterwards, contact your local triton admin who will take care of the IT gymnastics, and CC the vaspmaster so that he is aware of who gets added to the list.
For the PHYS department, the vaspmaster is Janne Blomqvist.
For each VASP version, there are 3 binaries compiled. All versions are MPI versions.
- vasp_std: The “standard” vasp, compiled with NGZhalf
- vasp_gam: Gamma point only. Faster if you use only a single k-point.
- vasp_ncl: For non-collinear spin calculations
The binaries are compiled with the Intel compiler suite and the MKL
library, the used toolchain module is
#!/bin/bash -l #SBATCH -n 8 #SBATCH -t 0-6 #SBATCH --mem-per-cpu=1500 ml vasp/5.4.4 srun vasp_std
Currently the binaries are compiled with GFortran instead of Intel Fortran (the Intel Fortran binaries crashed, don’t know why yet). Example batch script
#!/bin/bash -l #SBATCH -n 8 #SBATCH -p batch #SBATCH -t 0-6 #SBATCH --mem-per-cpu=1500 module load vasp/5.4.1-gmvolf-triton-2016a srun vasp_std
Potentials are stored at
VASP on old triton (obsolete, for reference only!)¶
For each VASP version, there are two binaries compiled with slightly different options:
Both are MPI versions. The first one is what you should normally use; it is compiled with the NGZhalf option which reduces charge density in the Z direction, leading to less memory usage and faster computation. The second version is needed for non-collinear spin calculations. The binaries can be found in the directory /share/apps/vasp/$VERSION/ . For those of you who need to compile your own version of VASP, the makefiles used for these builds can be used as a starting point, and are found in the directory /share/apps/vasp/makefiles .
The binaries are optimized for the Xeon Ivy Bridge nodes, although they will also work fine on the older Xeon Westmere and Opteron nodes. Note that for the moment only the NGZhalf version has been built. If you need the non-NGZhalf version for non-collinear spin calculations please contact triton support. Example job script below:
#!/bin/sh #SBATCH -p batch #SBATCH -N 1 #SBATCH -t 0-5 # 5 hours #SBATCH -n 12 #SBATCH --mem-per-cpu=2500 #SBATCH --constraint=[xeonib|xeon|opteron] module load vasp/5.3.5 srun vasp.mpi.NGZhalf
The relative time to run the vasptest v2 testsuite on 12 cores (so a full node for Xeon Westmere and Opteron nodes, and 12/20 cores on a Xeon Ivy Bridge node) is for Xeon IB/Xeon Westmere/Opteron 1.0/2.0/2.8. So one sees that the Xeon Ivy Bridge nodes are quite a lot faster per core than the older nodes (with the caveat that the timings may vary depending on other jobs that may have been running on the Xeon IB node during the benchmark).
The binaries are optimized for the Xeon nodes, although they also work on the Opteron nodes. Some simple benchmarks suggest that the Opteron nodes are a factor of 1.5 slower than the Xeon nodes, although it is recommended to write the batch script such that Opteron nodes can also be used, as the Opteron queue is often shorter. An example script below:
#!/bin/sh #SBATCH -p batch #SBATCH -N 1 #SBATCH -t 0-5 # 5 hours #SBATCH -n 12 #SBATCH --mem-per-cpu=2500 #SBATCH --constraint=[xeon|opteron] module load vasp/5.3.3 srun vasp.mpi.NGZhalf
VASP 5.3.2 and older¶
The binaries are optimized for the Intel Xeon architecture nodes, and are not expected to work on the Opteron nodes. An example job script is below (Note that it is different from the script for version 5.3.3 and newer above!):
#!/bin/sh #SBATCH -p batch #SBATCH -N 1 #SBATCH -t 1-0 # 1 day #SBATCH -n 12 #SBATCH --mem-per-cpu=3500 #SBATCH --constraint=xeon module load vasp/5.3.2 srun vasp.mpi.NGZhalf
PAW potentials for VASP can be found in the directory /share/apps/vasp/pot. The recommended potentials are the ones in the Apr2012.52 subdirectory. For reference, an older set of potentials dating back to 2003 can be found in the “2003” subdirectory.
The vasp.mpi.NGZhalf builds have been verified to pass all the tests in the vasptest suite.
Here is a number of Makefiles copy-pasted from old Rocks installation. Can be useful in general, though may require adaptation to new installation. Please, send us a fully working copy if you have one.
See old wiki: https://wiki.aalto.fi/display/Triton/Applications
Rename vasp.x.y.makefile => vasp.x.y/makefile