VASP is the Vienna Ab-initio Simulation Package for performing ab initio quantum mechanical molecular dynamics. VASP has strict licensing requirements and is installed on MASSIVE on behalf of the owner of the license. Generally we install VASP in association with a project that is lead by the license owner. Only members of the project can access the license and the project lead has complete control over who is a member of the project.

Some tips for running VASP

When running the CPU only version of VASP we prefer jobs to be run with 10 cores per node (ppn=10). This frees up 2 cores on the nodes to run GPU jobs on the 2 GPUs. 

VASP uses OpenMP and this can cause problems if OpenMP tries to spawn as many threads as detected node cores, when at the same time each process is also running on each core. To force VASP to use only one thread per core add the following option to your batch scripts:


Here is what a typical SLURM script looks like

#SBATCH --account=<project id>

#SBATCH --ntasks=16
#SBATCH --ntasks-per-node=16
#SBATCH --mem=48000

#SBATCH --mail-user=<you email address>
#SBATCH --mail-type=FAIL
#SBATCH --mail-type=END

#SBATCH --time=50:00:00

module load  vasp_<project id>/5.2.12-intel
# not required under SLURM
mpiexec vasp


Here is what a typical (deprecated) PBS looks like :

# Length job will run
#PBS -l walltime=24:00:00

# Run 80 cores, spread over 8 nodes, using 4000MB of memory per core
#PBS -l nodes=8:ppn=10,pmem=4000MB

# Go to the directory where the job was launched

# Set up the VASP environment
module load vasp_$ROJECTNAME/5.3.3-intel

# Make sure each process only uses one thread

# Run VASP and safe the output
mpiexec vasp > output

Copyright © 2016 MASSIVE. All Rights Reserved.