The Vienna Ab initio Simulation Package (VASP) is a computer program for atomic scale materials modelling, for example electronic structure calculations and quantum-mechanical molecular dynamics, from first principles.
This guide serves as an introduction to running VASP at Pawsey.
Prerequisites/Before you begin
Proof of a licence is required before being granted access to VASP.
You should submit a helpdesk ticket requesting VASP access, including the user accounts and email addresses that require access.
The email addresses for the accounts must match the email addresses that are used on the VASP licensing portal.
Based on experience, checking the email that was used in the VASP license portal first can avoid confusion and help us progress the ticket faster.
The Pawsey helpdesk will then use the VASP licensing portal to confirm a valid licence, which is why it is important to have a matching email address to the one registered with VASP.
Upon confirmation from the VASP licensing portal we will grant access to the
vasp6 groups depending on the type of license, which will allow the accounts to load the corresponding VASP modules.
Generally, up to 6 users can be on a single licence. Note that licences are restricted to particular versions of VASP.
Example script to run VASP
ulimit command is required because VASP uses a large amount of stack memory in addition to heap memory. This does not unlock more physical memory.
In VASP versions 5.4.4, 6.2.1 and 6.3.0 there are three default binaries created:
Pawsey staff does not install any VASP customisations globally.
Install VASP with support for VASPsol
VASPsol is a popular customisation package for VASP, that enables calculations using an implicit solvation model.
Users with a valid VASP license can use Spack to install VASP with VASPsol support. Note how the Spack installation command needs to be run from a directory containing the VASP source archive for the requested version.
The example below shows the procedure to install VASP 6.3.0 with VASPsol using Spack:
Note that this procedure has currently been tested with the following versions and options:
- email@example.com +scalapack +vaspsol
- firstname.lastname@example.org +scalapack +vaspsol
- email@example.com +scalapack +vaspsol
Peter Larsson's work on optimising VASP performance may be useful:
These are particularly interesting for choosing the number of cores, cores per node, and VASP parameters such as NPAR, KPAR, NCORE and NSIM.