IMAGES

From VASP Wiki
Revision as of 08:10, 20 October 2023 by Schlipf (talk | contribs)

IMAGES = [integer]
Default: IMAGES = 0 

Description: IMAGES defines the number of instances of VASP initiated. These instances carry out VASP calculations in separate directories (e.g., 01, 02, 03, etc.). This flag is instrumental in supporting various calculations including elastic band calculations, parallel tempering, and thermodynamic integration, where simultaneous execution of multiple VASP instances is necessary.


VASP supports different modes for performing simultaneous calculations using distinct INCAR, KPOINTS, POTCAR, or POSCAR files. These modes include the elastic band method for energy barrier calculations, thermodynamic coupling-constant integrations, and parallel tempering. Typically, the primary INCAR file should be located in the root directory. Other files such as KPOINTS, POTCAR, and POSCAR can be placed in subdirectories (e.g., 00, 01, 02...) or in the root directory. Files in subdirectories take precedence over those in the root directory.

File handling

When VASP starts, it reads the file INCAR in the root directory. Subsequently, VASP splits the MPI communicator into subgroups for each image. If an INCAR file is present in the subdirectories 01, 02, 03, ..., VASP will process those afterward. Otherwise, VASP continues reading from the root INCAR file. You can also provide image-specific data in the root INCAR file if the files are very similar

 # general INCAR tags
 IMAGES = 4
 TEBEG = 600
 
 # INCAR tags only on IMAGE 1
 IMAGE_1 {
   TEBEG = 400
 }
 
 # INCAR tags only on IMAGE 2
 IMAGE_2 {
   TEBEG = 500
 }

Here images 3 and 4 would use TEBEG=600 because the value is not specified for the image. The files KPOINTS and POTCAR will be read from the subdirectory if available and from the root directory otherwise. The POSCAR file and all other input files are always read from the subdirectories. All output files (including OUTCAR and OSZICAR) are always written to the subdirectories.

To summarize, to run a calculation with IMAGES, you provide:

  • an INCAR file in the root directory
  • optionally an overwriting INCAR file in the subdirectories
  • POSCAR files in the subdirectories
  • KPOINTS and POTCAR either in the root or in the subdirectories

Use cases

Nudged elastic bands
If IMAGES is set without any other tag, an elastic-band calculation is performed. This defaults to the recommended nudged-elastic-band method but other options are available by modifying the SPRING tag. Please consider the nudged-elastic-bands how-to and the SPRING tag for more information.
Thermodynamic coupling-constant integrations
When VCAIMAGES is set in the INCAR file, VASP computes a thermodynamic coupling-constant integration. This in turn sets IMAGES=2 running two VASP calculations in the subdirectories 01 and 02. Since this is a special case where the two calculations may have different computational costs, NCORE_IN_IMAGE1 can be set to force an unequal split of the processes across the two images. The tag VCAIMAGES describes in more detail how to set up these calculations.
Parallel tempering
If the tag LTEMPER=.TRUE. is set in the INCAR file, VASP will perform parallel tempering calculations. In this case, it is necessary to provide different POSCAR files in each subdirectory and modify the TEBEG either by separate INCAR files or nested IMAGE_X/TEBEG definitions in the root INCAR file. For further details, refer to the description of the LTEMPER tag.


Related tags and articles

SPRING, IBRION, NFREE, SMASS, VCAIMAGES, LTEMPER

Examples that use this tag