potfit wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
~~NOTOC~~
====== Configurations ======
----

The atomic configurations used for fitting are read from the configuration file which is specified in the parameter file. The format of the configuration is very simple and explained below.

There is a [[utilities:vasp2force|command line tool]] to generate configuration files from 
[[https://www.vasp.at/|VASP]] output.

====  Configuration Files  ====

A //potfit// configuration file is a plain text file, consisting of a [[#Header|header]] and a [[#Body|body]], both of which are described below.

=====  Header  =====

The header consists of at least six lines starting with the number sign # and has the following format:

<code potfit>
 #N natoms useforce
 #C type_0 type_1 type_2 ...
 #X boxx.x boxx.y boxx.z
 #Y boxy.x boxy.y boxy.z
 #Z boxz.x boxz.y boxz.z
 #B_S x y z r
 #B_O x y z
 #B_A x y z
 #B_B x y z
 #B_C x y z
 #W weight
 #E coh_eng
 #S stress_xx stress_yy stress_zz stress_xy stress_yz stress_xz
 #F 
</code>

The lines starting with ''#N'', ''#X'', ''#Y'', ''#Z'', ''#E'' and ''#F'' are mandatory, while the lines starting with ''#C'', ''#W'', ''#B'' and ''#S'' are optional. All other lines are ignored. ''#N'' must head the first line specifying the number of atoms in the configuration and an integer flag to control whether to use or to ignore force and stress information in this configuration. ''#F'' signifies the last header line. All parameters except the //type_i// are numbers and have the following meaning:

**natoms**\\
<html>&nbsp;&nbsp;&nbsp;</html>number of atoms in configuration

**useforce**\\
<html>&nbsp;&nbsp;&nbsp;</html>if 0, forces from this configuration are ignored

**boxi.j**\\
<html>&nbsp;&nbsp;&nbsp;</html>component j of box vector i

**weight**\\
<html>&nbsp;&nbsp;&nbsp;</html>all contributions to the error sum from this configuration will be multiplied with this weight

**coh_eng**\\
<html>&nbsp;&nbsp;&nbsp;</html>cohesive energy per atom

**stress_ij**\\
<html>&nbsp;&nbsp;&nbsp;</html>components of stress tensor

Lines beginning with ''#B'' describe the [[bocp|Box of Contributing Particles]] and are optional.

The ''#C'' line contains information about the chemical elements and the corresponding atom types contained in this configuration. The elements are assigned to the corresponding atom types and have to be consistent throughout the configuration file.

**Please note:**

In all directions the sample should have a size of at least the potential cutoff distance. This distance is measured perpendicular to the corresponding face. If this is not the case, additional periodic copies of the configuration will be used for the simulation.

===  Deprecated header format  ===

This "old" format is still read by //potfit//. Here, the header consists of six lines and has the following format:

<code>
 natoms
 boxx.x boxx.y boxx.z
 boxy.x boxy.y boxy.z
 boxz.x boxz.y boxz.z
 coh_eng
 stress_xx stress_yy stress_zz stress_yz stress_zx stress_xy
</code>

The parameters have the same meaning as in the new header. The parameter useforce is assumed to be 1, i.e. the forces are used as reference data.

=====  Body  =====

Following the header, there is one line for each atom. The format of each line looks like this:

<code>type x y z f_x f_y f_z</code>

These items stand for:

**type**\\
<html>&nbsp;&nbsp;&nbsp;</html>type of the atom; must be in the range [0,...,ntypes-1]

**x, y, z**\\
<html>&nbsp;&nbsp;&nbsp;</html>absolute coordinates of the atom

**f_x, f_y, f_z**\\
<html>&nbsp;&nbsp;&nbsp;</html>net force components on the atom

Please note that the forces **cannot** be omitted, even when they are ignored.

===  Boundary Conditions  ===

//potfit// uses **periodic boundary conditions**. If a particle coordinate is not within the simulation box, it is mapped back into the simulation box.

=====  Multiple Configurations  =====

Multiple configuration files can just be concatenated. //potfit// continues reading from a reference file until it reaches the end of file. Should this not coincide with the end of a single configuration, an error will result.