The updated constant potential plugin for LAMMPS
The USER-CONP2 package allows users to perform LAMMPS MD simulations with constant potential electrodes. It updates the original LAMMPS-CONP (https://github.com/zhenxingwang/lammps-conp) with the following improvements and optimizations:
- Overall electroneutrality enforced via projection matrix precomputation
- New PPPM KSpace styles and CONP interfaces, including with the Intel package
- Smart neighborlisting and
newton oncompatibility - Extensive vectorization speedups in the old Ewald KSpace code
This is version 1.1 of the code. Upgrade priorities for version 1.2 are listed throughout this document in boldface; I welcome all feature suggestions!
If you are reading this, you probably know that you need a custom compiled LAMMPS to use this plugin -- see below for instructions.
If you have used this plugin, please use one or both of the following citations as suitable:
- https://doi.org/10.48610/6b1122a The University of Queensland eSpace digital repository DOI for this source code
- https://aip.scitation.org/doi/10.1063/5.0086986 Our just accepted manuscript describing electroneutrality and fully periodic techniques (
ffield/noslab zneutr)
Fix conp used to crash without an error message if electrolyte particle IDs were non-contiguous (e.g. after a delete_atoms command).
I believe this has been fixed but have not personally verified this.
For now, any such crashes may be remedied by a suitable reset_atom_ids command.
The PPPM flag causes weird things to happen in Poiseuille-flow-type simulations. Omitting that flag works fine (albeit with much lower performance). Repairing this is a priority issue.
The fix command is considerably simpler than in the previous version:
fix [ID] [group1] conp [Nevery] [group2] [η] [DV] [Log] [optional keyword1] [optional value1] ...
fix [ID] [group1] conq [Nevery] [group2] [η] [QR] [Log] [optional keyword1] [optional value1] ...
ID = ID of FIX command
group1 = Group for 'left' electrode
Nevery = Update charge every this many steps
group2 = Group for 'right' electrode
η = Gaussian width parameter in angstrom-1. Usually this is 1.979 in earlier literature. Validating this is an active project.
DV: fix conp will set the charges such that group2 has a potential DV volts above group1.
QR: fix conq will set the charges such that group2 has total charge QR, group1 has total charge -QR, and energy is minimized. See [5] for more details. fully added in v1.1
Log = Name of log file recording time usage of different parts
pppm [no values]
Does what it says on the box!
To use pppm, the pppm/conp KSpace style must be used. This style is interchangeable with the LAMMPS pppm style in every other way but can interface with fix conp to enable PPPM calculations of the electrode-electrolyte interactions in KSpace. (Note that there is a pppm/conp/intel KSpace implementation, which works with package intel and will automatically be used when suffix intel is specified).
Fix conp will crash LAMMPS with an error message if the pppm flag is specified but fix conp cannot find the pppm/conp (or /intel) KSpace style. The eventual design goal is for the pppm flag to be removed and for fix conp to silently interface with pppm/conp when detected.
Note: Weird things happen with PPPM mode (with and without USER-INTEL) in NEMD simulations. Proceed with caution.
etypes [Ntypes] [type1] [type2] ... [typeN]
This tells fix conp that the electrode only contains the specified particle types, and the electrolyte does not contain the specified particle types. For example, "etypes 2 5 3" is a promise to fix conp that the electrode only contains types 3 and 5. This allows fix conp to request specialized neighbor lists from LAMMPS: in the construction of the electrode "A" matrix the neighbor list will contain only electrode-electrode interactions, and in the calculation of the electrolyte "b" vector the neighbor list will contain only electrode-electrolyte interactions. This will speed up your calculation by 10-20% if correctly specified, and will silently return incorrect results if the electrode and electrolyte particle types overlap in any way.
ffield [no values]
This tells fix conp to run in finite-field mode as per Dufils (2019) [1], where (1) slab corrections are disabled and (2) the electrode preset charge vector is calculated using the electrodes' z coordinates. Configurations can be switched seamlessly between slab and finite-field mode, as long as the usual changes to the script are made ("boundary p p p" instead of "boundary p p f" and no "kspace_modify slab").
However, you must add in the electric field separately: if fix conp is run in ffield mode, you must include lines like these in your script:
variable zfield equal -v_v/lz
fix efield all efield 0.0 0.0 v_zfield
where v_v is the potential difference supplied to fix conp. Note that using "v_"-style variables is required for matching up a dynamically-varying potential difference to a dynamically-varying electric field.
Note that fix efield already takes its argument in the correct units for units real (V/angstroms) so no unit conversion should usually be needed. Fix conp in ffield mode will silently return incorrect results without the electric field; upgrading this is an urgent feature addition priority.
*Note: In [1], electrode atoms are mentioned as being "set at 0V", but the effect of this is already automatically done inside the conp ffield code. You do not specify electrode voltages in any different way whatsoever in the input script when using ffield.
new in v1.1:
You can also run fix conq in finite-field mode by coupling a fix efield to its output (which is the potential difference required to achieve the prescribed charge):
fix charges elec1 conq 1 elec2 ...
variable v_zfield equal -f_charges/lz
fix efield all efield 0.0 0.0 v_zfield
noslab [no values]
This tells fix conp to run in no-slab-corrections mode, without further modifications. Run this with zneutr (see below) unless you know what you are doing.
zneutr [no values]
This tells fix conp to enforce an additional electroneutrality constraint: the total sum of electrode charges in the right half of the box (z > 0) will be zero. Thus, noslab zneutr enables fix conp to run a "doubled cell" simulation, in which two cells are positioned back-to-back with reversed polarities to create a zero dipole supercell -- see Raiteri (2020) [2] for a version of this simulation geometry, but with fixed charges.
matout [no values]
Causes fix conp to print out the A-matrix and the inverse A-matrix (if inv is used) to amatrix and inv_a_matrix respectively. The inverse matrix will already be projected into the space of electroneutral charge vectors (see [4], eq (21) for the expression, which they label as "S"). Note that the former conp would print out this matrix by default -- I have decided to make this capability opt-in because the A matrix reading code still has bugs lurking in it and the alternative of just computing the A matrix afresh is now very fast with the latest optimizations in v1.0.
inv [inv_matrix_file]
org [org_matrix_file]
This allows fix conp to read in a pre-existing electrode matrix for its calculations, either the A matrix ("org") or its inverse ("inv"). Option "org" will result in an electroneutral final matrix (since fix conp calculates the electroneutrality projection when inverting the A matrix), while option "inv" has no such guarantee. Use of these options are maintained for compatibility but is discouraged: there are still plenty of possible bugs lurking, and the code here does not use LAMMPS's latest file-reading functions, and optimization (notably calculating only half the A-matrix and then mirroring by symmetry) means that the A-matrix calculation is very short for all but the largest electrode configurations.
This package is only guaranteed to work for the 27May2021 patch of LAMMPS. Although it may work with other versions, they are not officially supported by the USER-CONP2 developers and may require extra work on the part of the user to compile.
The fix requires BLAS and LAPACK compatible linear algebra libraries, although it's not fussy about
which ones to use. CMake will automatically attempt to find compatible libraries during the
configuration stage and will build its own if it can't find any, although this will be slower than using
libraries optimised for the target machine. CMake is usually accurate when
finding libraries, but it may be necessary to modify the CMAKE_CXX_FLAGS variable to explicitly
specify the desired library location and link flags.
Git is required by the install_cmake.sh installation script.
Installation is managed via the install_cmake.sh script in the root directory. This script copies the
necessary files into a dedicated USER-CONP2 folder in the LAMMPS src directory and integrates with
LAMMPS' CMake build process. The installation steps are as follows:
- Set the
LAMMPS_PREFIXenvironment variable to the location of the base LAMMPS directory (note: this must be the root directory containing theREADMEfile, not thesrcdirectory). In bash, run the commandexport LAMMPS_PREFIX=/path/to/lammps. - In the root directory of this repository, run the install script via
bash ./install_cmake.sh - Compile LAMMPS using the usual CMake procedure, setting
-D PKG_USER-CONP2=yes. This package can be installed alongside theUSER-INTELaccelerator package by also setting-D PKG_USER-INTEL=yes, in which case you should use the Intel C++ compiler and link against Intel MKL for the best performance. - Alternatively, compile LAMMPS using the legacy Make procedure, including
make yes-user-conp2to set up this package for inclusion.
It is also possible to use the legacy make-based build system by copying all relevant .cpp and .h
files into the LAMMPS src directory and manually specifying the BLAS/LAPACK compile and link options.
There is a compute potential/atom which can be used to compute the electric potential at atoms' positions as a per-atom variable. This is still in development but almost ready for public use.
The dev-historical branch contains versions frozen in various stages of optimization -- including the original conp/v0, with only semantic changes to bring it in line with the latest LAMMPS code -- to prove correctness of optimizations.
[1] Dufils et al, PRL 123 (19): 195501 (2019) https://doi.org/10.1103/PhysRevLett.123.195501
[2] Raiteri et al, J Chem Phys 153: 164714 (2020) https://doi.org/10.1063/5.0027876
[3] Zhang et al, J Phys Energy 2: 032005 (2020) https://doi.org/10.1088/2515-7655/ab9d8c
[4] Scalfi et al, Phys Chem Chem Phys 22: 10480-10489 (2020) https://doi.org/10.1039/C9CP06285H
[5] Dufils et al, JPC Lett 12 (18): 4357-4361 (2021) https://doi.org/10.1021/acs.jpclett.1c01131
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent