Plugins: Difference between revisions

From VASP Wiki
No edit summary
Line 3: Line 3:
This page describes the steps that you will need to write your first Python script and link it with VASP.
This page describes the steps that you will need to write your first Python script and link it with VASP.


==Install==
Create a new [https://conda.io/projects/conda/en/latest/user-guide/getting-started.html conda] environment. Alternative environment creation packages should work, but we have not tested them.
    conda create -n vasp_plugin python=3.10
Enter the create <code>vasp_plugin</code> conda environment
    conda activate vasp_plugin
Navigate to the <code>plugins</code> directory within VASP source code,
    cd </path/to/vasp/source/code>/src/plugins
Install the VASP Python package through [https://pip.pypa.io/en/stable/installation pip]
    pip install .
Add the following lines to your <code>makefile.include</code>
    CPP_OPTIONS+= -DPLUGINS
    LLIBS      += $(shell python3-config --ldflags --embed) -lstdc++
    CXX_FLAGS  = -Wall -Wextra  $(shell python3 -m pybind11 --includes) -std=c++11
Compile VASP using the [[Installing_VASP.5.X.X|guide to installing VASP.6.X.X]].
{{NB|mind|Make sure to be within the conda environment when you compile VASP.}}


==Run-time instructions==
==Run-time instructions==

Revision as of 13:52, 14 October 2024

Implementing features over VASP carries a significant overhead, both in term of code development and maintenance. An alternative approach is to use our Python plugin infrastructure. Simply write Python functions in a pre-defined format and VASP will recognize and execute your code while it is running. This page describes the steps that you will need to write your first Python script and link it with VASP.


Run-time instructions

When running VASP with the python interface you will need to add the lib directory of your python to LD_LIBRARY_PATH. You can do this somewhat easily with conda by running python3-config --ldflags, followed by

   export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<path-from-earlier-command>

Python scripting

Start by creating a file called vasp_plugin.py in the folder in which you are running a VASP calculation. An alternative route through entry-points is also possible (see below for further instructions). In vasp_plugin.py implement one or all of the following Python functions.

   def local_potential(constants, additions):
       """Defines the PLUGINS/LOCAL_POTENTIAL interface"""
   def force_and_stress(constants, additions):
       """Defines the PLUGINS/FORCE_AND_STRESS interface"""
   def structure(constants, additions):
       """Defines the PLUGINS/STRUCTURE interface"""
   def occupancies(constants, additions):
       """Defines the PLUGINS/OCCUPANCIES interface"""

As the names of the input variables suggest,

  1. constants provides a dataclass with quantities computed in VASP that must stay constant through the interface. Typically these include "metadata" such as the lattice vectors, number of grid points, etc. Some interfaces also pass in quantities such as the charge density as constants. Please check the relevant INCAR pages for more details on which quantities are available as constants. Alternatively, you may print the contents of constants.
  2. additions stores quantities that are allowed to change in the interface. You must use the syntax additions.<quantity-name> += ... in order to change additions. That is, quantities must be "added" (or subtracted) to additions instead of them being assigned a new value.

Each of the above interfaces may be called by VASP depending on the following INCAR tags

   PLUGINS/LOCAL_POTENTIAL = T         ! Modifies the local potential every SCF step
   PLUGINS/FORCE_AND_STRESS = T        ! Modifies the force and stress at the end of the SCF loop
   PLUGINS/STRUCTURE = T               ! Modifies the structure at the end of the SCF loop
   PLUGINS/OCCUPANCIES = T             ! Modifies NELECT, EFERMI, SIGMA, ISMEAR, EMIN, EMAX, NUPDOWN at the end of the SCF loop

Navigate to the relevant INCAR tag pages for further information.

Exposing interfaces through entry-points (advanced)

Consider using entry points in cases where you do not want to move vasp_plugin.py to each new VASP calculation directory. Within the group "vasp", add the following lines to your pyproject.toml file for each interface you would like to introduce new functions. For example, if you wanted to access the force_and_stress interface through an entry point, add the following lines to your pyproject.toml file,

   force_and_stress = "/path/to/python_function:force_and_stress"