-
Notifications
You must be signed in to change notification settings - Fork 19
Forces
The Probe-Particle Model (the AFM part - ppafm) calculates all the forces that affect the probe particle (PP):
-
Forces caused by the interaction with (metallic) tip
- The lateral forces - x and y are holding the (PP) in its equilibrium position from its lateral sides. These forces are harmonic (spring) forces. For CO they are around 0.24 N/m. Note: For the Double Probe Particle model different forces are used, see its wiki.
- The radial force - R is holding the PP in the appropriate distance bellow the last metallic-tip atom. !!! Unlike in the original Fortran code and the paper this force is also harmonic (spring) !!! - This allows for better computational stability, than the original Lennard-Jones (L-J) model. L-J could in extreme cases lead to the loss of PP, which is physically right, but the exact constant is unknown and is extremely tip-dependent. Anyway, if the PP (standing for the flexible tip-apex) is lost in theory or experiment it causes loss of high resolution and the results are generally not usable. From our experience the usage of less precise potential is not causing any additional problems with the usage of spring constant around 20.0 or 30.0 N/m.
-
Forces caused by the interaction with the sample
- The interaction with the sample is explained in detail below in the section Force-field models
During the relaxation, all the forces are taking into account and once a new equilibrium is found the code calculates the forces acting on the metallic forces. These tip forces can be either plotted or used for computation of the frequency shift.
The force field governing the interaction between the PP and the sample atoms in ppafm is divided into three components:
The three components are the Pauli repulsion
- Pauli:
- Lennard-Jones
- Full-density based model
- vdW:
- Lennard-Jones
- DFT-D3
- ES:
- Point-charge
- Hartree
While in principle it is possible to combine these freely, there are a few combinations that make the most sense. In order of increasing physical accuracy:
- Lennard-Jones without electrostatics
- Lennard-Jones + point-charge electrostatics
- Lennard-Jones + Hartree electrostatics
- Full-density based model + DFT-D3 vdW + Hartree electrostatics
The different force-field models are explained in more detail in the following, with examples of how to use them in the ppafm CLI. For GPU-accelerated calculations, see the tutorial in the Python API documentation.
The Lennard-Jones (LJ) force field is a commonly used pair-wise force field that models the Pauli repulsion and van der Waals attraction interactions between atoms. It has the form
where
In ppafm the parameters values from the OPLS force field are used. You can copy and adjust this file in the local directory of calculations. The model will read it automatically.
The force is pre-calculated as a sum of forces originating from all the sample atoms, and stored in FFLJ_?.xsf or FFLJ.npz
files.
In the ppafm CLI, the Lennard-Jones force field can be computed using the ppafm-generate_ljff
command. Give the input geometry using the --input
/-i
option. For example, in the Graphene example we run
ppafm-generate-ljff -i Gr6x6N3hole.xyz
This outputs the LJ force field in three files FFLJ_{x,y,z}.xsf
for each of the spatial directions. Optionally one can choose to also output energy using the --energy
/-E
option. Also note the --ffModel
option which when set to vdW
only outputs the vdW contribution without the Pauli term.
ppafm supports two different ways of computing the electrostatics term, using either point charges or the Hartree potential. The point-charge model is the simpler one, where the electrostatic force is obtained from the Coulomb force between the PP and the sample atoms, which all have a point charge associated with them. The force is
where
The point-charge electrostatic force field can be obtained in the ppafm CLI by using the ppafm-generate-elff-point-charges
command. For example, in the Graphene example we use
ppafm-generate-elff-point-charges -i Gr6x6N3hole.xyz --tip s
This outputs the electrostatic force field in three files FFel_{x,y,z}.xsf
for each of the spatial directions. The point charges are contained in the input xyz file. Inspection of the Gr6x6N3hole.xyz file shows how the point charges are included as an additional fifth column in the xyz file. The Extended XYZ format of ASE is also supported.
The point-charge approximation works reasonably well in many places, but for a more physically accurate model we have to consider the full continuous charge density of the sample and the tip. Using the Hartree potential of the sample
The electrostatic force field from the Hartree potential can be generated in the ppafm CLI by using the ppafm-generate-elff
command. For example, in the PTCDA_HARTREE_dz2 example we run
ppafm-generate-elff -i LOCPOT.xsf --tip dz2 -f npy
using the Hartree potential in LOCPOT.xsf
generated with VASP.
Usage of multipoles is available for both of methods as well.
Generally speaking it is important to consider the charge and the multipole character of the PP.
The character of the charge distribution depends on what the functionalization of the tip is. Typically for a CO molecule we use the quadrupole charge distribution of the dz2 orbital, but for example for a Xe-tip the simpler monopole s-orbital is a better model. In the point-charge approximation the quadrupole is created by placing three point charges in a sigma
parameter.
The multipole moment is calculated by Q*sigma
for dipole or Q*sigma*sigma
for quadrupole.
The Pauli repulsion modelled by the
where
The Pauli force field from the FDBM can be calculated in the ppafm CLI by using the ppafm-conv-rho
command. For example, in the pyridineDensOverlap example we run
ppafm-conv-rho -s sample/CHGCAR.xsf -t tip/CHGCAR.xsf -B 1.0 -E
where we provide the sample electron density using the -s
option and the tip electron density using the -t
option. Both densities, sample/CHGCAR.xsf
and tip/CHGCAR.xsf
, must be defined for the same unit cell geometry. The value of the --Bpauli
/-B
option. The output force field is saved in the three files FFpauli_{x,y,z}.xsf
for each of the spatial directions. Also note that we have to subsequently call the ppafm-relaxed-scan
with the --noLJ
option to use the Pauli from the separate files as well as --Apauli
to set the value of the
In their implementation of the FDBM, Ellner et al. chose to use the DFT-D3 instead of Lennard-Jones vdW interaction to accompany the Pauli interaction. Following this choice, the DFT-D3 energy/force calculation is also implemented in ppafm, specifically in the Becke-Johnson damping form:
where the sum is over all of the atoms in the sample,
is a damping function,
is a cutoff radius, and the
The
The DFT-D3 vdW force field can be calculated in the ppafm CLI using the ppafm-generate-dftd3
command. For example, in the pyridineDensOverlap example we run
ppafm-generate-dftd3 -i sample/LOCPOT.xsf --df_name PBE
Here we choose to use the --df_params
option. The output force field is saved in the three files FFvdW_{x,y,z}.xsf
for each of the spatial directions. Also note that we have to subsequently call the ppafm-relaxed-scan
with the --noLJ
option to use the vdW from the separate files.
Total forces including van der Waals for 6 different model systems, 4 molecules (benzene, bromomethane, carbon monoxide, and water) and 2 atoms (He, Xe). The tip is always a CO molecule, with the oxygen atom pointing towards the sample. On the molecules, the tip is placed over the C (in benzene), Br (in bromomethane), and O (in CO and H2O) atoms, respectively. The benzene and H2O molecules are flat-lying, CH3Br points with the Br atom towards the tip, CO is in an upright position wit the O atom pointing towards the tip:
Van der Waals components only for comparison. This demonstrates that the D3 model of dispersion forces as implemented in PPAFM agrees reasonably well with the dispersion forces implemented in VASP:
Forces without the van der Waals component. This shows the discrepancy between FDBM of PPAFM and VASP while also demonstrating that the problem is not with the dispersion (vdW) forces but somewhere else: