potfit wiki

open source force-matching

User Tools

Site Tools

utilities

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
Next revisionBoth sides next revision
utilities [2013/02/28 13:31] – created danielutilities [2013/03/01 09:53] – daniel
Line 1: Line 1:
-{{TOC_right}} +~~NOTOC~~ 
-The potfit/util directory contains a number of utility programs for the preparation of ''potfit'' input files and the postprocessing of ''potfit'' output files.+====== Utilities ====== 
 +---- 
 +The potfit/util directory contains a number of utility programs for the preparation of //potfit// input files and the postprocessing of //potfit// output files.
  
-;[[#force2poscar|force2poscar]] +[[#force2poscar|force2poscar]]\\ 
-:Converts force files (IMD output) to vasp POSCAR files. + Converts force files (IMD output) to vasp POSCAR files.
-;[[#vasp2force|vasp2force]] +
-:Converts vasp output (POSCAR, OUTCAR) to reference configuration data. +
-;[[#pottrans|pottrans]] +
-:Converts various IMD and ''potfit'' potential formats. +
-;[[#list_config|list_config]] +
-:List all configurations in a configuration file. +
-;[[#potfit_setup|potfit_setup]] +
-:Creates a parameter file for ''potfit'' from scratch. +
-;[[Utilities/Awk_scripts|awk scripts]] +
-:A series of awk scripts to handle various tasks with potential files, like combining, appending, creating from analytical functions, generating from scratch, plotting,... +
-;[[#potscale|potscale]] +
-:Performs gauge transformations of ''potfit'' EAM potentials.+
  
-=== force2poscar ===+[[#vasp2force|vasp2force]]\\ 
 +Converts vasp output (POSCAR, OUTCAR) to reference configuration data.
  
-Converts force files produced by [http://imd.itap.physik.uni-stuttgart.de/ IMD] and used by ''potfit'' to [http://cms.mpi.univie.ac.at/vasp/ VASP] input file POSCAR.+[[#pottrans|pottrans]]\\ 
 +Converts various IMD and //potfit// potential formats.
  
-Compilation: <tt>make force2poscar [-DSTRESS]</tt>+[[#list_config|list_config]]\\ 
 +List all configurations in a configuration file. 
 + 
 +[[#potfit_setup|potfit_setup]]\\ 
 +Creates a parameter file for //potfit// from scratch. 
 + 
 +[[Utilities/Awk_scripts|awk scripts]]\\ 
 +A series of awk scripts to handle various tasks with potential files, like combining, appending, creating from analytical functions, generating from scratch, plotting,... 
 + 
 +[[#potscale|potscale]]\\ 
 +Performs gauge transformations of //potfit// EAM potentials. 
 + 
 +---- 
 + 
 +====  force2poscar  ==== 
 + 
 +Converts force files produced by [[http://imd.itap.physik.uni-stuttgart.de/|IMD]] and used by //potfit// to [[http://cms.mpi.univie.ac.at/vasp/|VASP]] input file POSCAR. 
 + 
 +Compilation: ''make force2poscar [-DSTRESS]''
  
 Usage:  Usage: 
- force2poscar input.force+  force2poscar input.force
  
-The information is always written to a file called POSCAR residing in the local directory. Use compile option -DSTRESS if your force file includes stress tensor information.+The information is always written to a file called POSCAR residing in the local directory. Use compile option ''-DSTRESS'' if your force file includes stress tensor information.
  
-=== vasp2force ===+====  vasp2force  ====
  
-Converts [http://cms.mpi.univie.ac.at/vasp/ VASP] output to force files.+Converts [[http://cms.mpi.univie.ac.at/vasp/|VASP]] output to force files.
  
-Compilation: <tt>make vasp2force</tt>+Compilation: ''make vasp2force''
  
 Usage:  Usage: 
- vasp2force [-c list] [-e file] [-f] [-l] [-r] [-s list] <OUTCAR files>+  vasp2force [-c list] [-e file] [-f] [-l] [-r] [-s list] <OUTCAR files>
  
 Reads information from all OUTCAR files in the current directory. <OUTCAR files> is an optional list of files, if not given all files matching OUTCAR* will be scanned (it is possible to read gzipped files ending with .gz). Reads information from all OUTCAR files in the current directory. <OUTCAR files> is an optional list of files, if not given all files matching OUTCAR* will be scanned (it is possible to read gzipped files ending with .gz).
-An optional file can be specified, containing the energy of a single free atom calculated by [http://cms.mpi.univie.ac.at/vasp/ VASP] in a single line in the same order as in the OUTCAR file, e.g.:+An optional file can be specified, containing the energy of a single free atom calculated by [[http://cms.mpi.univie.ac.at/vasp/|VASP]] in a single line in the same order as in the OUTCAR file, e.g.:
  
- # Al      Co        Ni +<code> 
- -0.000219 -0.993872 -0.855835+# Al      Co        Ni 
 +-0.000219 -0.993872 -0.855835 
 +</code>
  
-Writes a force file to be used as a ''potfit'' reference configuration to standard output. If no options are given, force data is generated from each ionic step.+Writes a force file to be used as a //potfit// reference configuration to standard output. If no options are given, force data is generated from each ionic step.
  
 Options: Options:
  
-<tt>-c <list></tt> +<code> 
-:list of chemical species to use (e.g. "vasp2force -c Al=0,Mn=1,Pd=2"). This will force all atom types in all configurations to be consistent. + -c <list>              list of chemical species to use 
-<tt>-e <file></tt> +                        (eg. "vasp2force.sh -c Al=0,Mn=1,Pd=2") 
-:Specify file to read single atom energies from; if not found, "0" will be used for every atom type. + -e <file>              specify file to read single atom energies from 
-<tt>-f</tt> +                        if not found, "0" will be used for every atom type 
-:Uses only final configuration of multiple ionic steps. + -f                     only use the final configuration from OUTCAR 
-<tt>-l</tt> + -l                     list all chemical species found in OUTCAR and exit 
-:List all chemical species found in OUTCAR and exit. + -r                     scan recursively for OUTCAR files 
-<tt>-r</tt> + -s <list>              comma separated list of configurations to use 
-:Scan recursively for OUTCAR files in every subdirectory. + -w <weight>            change weight for all configurations to <weight> 
-<tt>-s list</tt> +</code>
-:List is a comma separated list of ionic steps to use, e.g. "1,4,7,9". The sequence of the force data is always the same as in the OUTCAR file, independent of the sequence given in the list. Every configuration mentioned appears exactly once. +
-<tt>-w weight</tt> +
-:Assign this weight to all configurations.+
  
-=== pottrans ===+====  pottrans  ====
  
 Converts betweeen various potential models. Converts betweeen various potential models.
  
-Compilation:  <tt>make pottrans</tt>+Compilation:  ''make pottrans''
  
 Usage: Usage:
- pottrans <paramfile>+  pottrans <paramfile>
  
 required parameters in paramfile (here with example values) required parameters in paramfile (here with example values)
  
-<code><pre>+<code>
 ntypes     2           # number of atom types ntypes     2           # number of atom types
 ncols      3           # number of output potentials ncols      3           # number of output potentials
Line 83: Line 92:
 core_potential_file    phi.pot   # pair potential for EAM potentials core_potential_file    phi.pot   # pair potential for EAM potentials
  
-#optional parameters+# optional parameters
  
 reorder     0 1        # permutes order of potentials in final file, reorder     0 1        # permutes order of potentials in final file,
                        # ntypes parameters necessary                        # ntypes parameters necessary
 r_start   1.8 1.8 1.8  # minimal r for each column in output potential r_start   1.8 1.8 1.8  # minimal r for each column in output potential
-</pre></code>+</code>
  
-in.pot is converted to out.pot. in.pot can be of IMD potential format 1 or 2, out.pot is of ''potfit'' potential format. For EAM potentials, specify the appropriate number of columns in ncols and the required IMD format potential files. The order of the different atom types can be changed with the reorder parameter by specifying the desired sequence.+in.pot is converted to out.pot. in.pot can be of IMD potential format 1 or 2, out.pot is of //potfit// potential format. For EAM potentials, specify the appropriate number of columns in ncols and the required IMD format potential files. The order of the different atom types can be changed with the reorder parameter by specifying the desired sequence.
  
-To convert from ''potfit'' to IMD use ''potfit'' with opt 0 in parameter file.+To convert from //potfit// to IMD use //potfit// with ''opt 0'' in the parameter file.
  
-=== list_config ===+====  list_config  ====
  
 Lists all configurations in a config file. Lists all configurations in a config file.
  
-Compilation:  <tt>make list_config</tt>+Compilation:  ''make list_config''
  
 Usage: Usage:
- list_config <config_file>+  list_config <config_file>
  
-Scans a ''potfit'' configuration file and lists all configurations found. This includes the origin (if comment is found), the starting line, number of atoms and weight of the configuration.+Scans a //potfit// configuration file and lists all configurations found. This includes the origin (if comment is found), the starting line, number of atoms and weight of the configuration.
  
-=== potfit_setup ===+====  potfit_setup  ====
  
-This utility generates a simple parameter file for ''potfit''.+This utility generates a simple parameter file for //potfit//.
  
 Usage: Usage:
- potfit_setup [-c config file] [-p potential file] [-s prefix]+  potfit_setup [-c config file] [-p potential file] [-s prefix] 
 + 
 +<code> 
 + -c <config file>       name of the configuration file 
 + -p <potential file>    name of the potential file 
 +                        for analytic potentials this can easily be created with 
 +                        the makeapot script from the awkscripts 
 + -s <prefix>            prefix for all files, overrides -c and -p 
 +                        the following files will be checked: 
 +                        <prefix>.pot and <prefix>.config 
 +                        if they are not found, -c and -p will be read 
 +</code>
  
-<tt>-c <config file></tt> +====  awk scripts  ====
-:name of the configuration file +
-<tt>-p <potential file></tt> +
-:name of the potential file (for analytic potentials this can easily be created with the <tt>makeapot</tt> script from the awkscripts) +
-<tt>-s <prefix></tt> +
-:prefix for all files, overrides -c and -p  +
-:the following files will be checked: <tt><prefix>.pot</tt> and <tt><prefix>.config</tt> if they are not found, -c and -p will be read+
  
-=== awk scripts ===+The awk scripts are listed on a [[utilities/Awk_scripts|separate page]].
  
-The awk scripts are listed on a [[Utilities/Awk_scripts|separate page]].+====  potscale  ====
  
-=== potscale === +<html><span style="color:red;font-size:150%;">Not maintained anymore !</span></html>
-'''<div style="color:red">Not maintained anymore !</div>'''+
  
 potscale performs gauge transformations on EAM potentials. potscale performs gauge transformations on EAM potentials.
  
-Compilation: <tt>make potscale</tt>+Compilation: ''make potscale''
  
 Usage: Usage:
- potscale <paramfile>+  potscale <paramfile>
  
 Required parameters in paramfile: Required parameters in paramfile:
  
-<code><pre> +<code> 
-ntypes # number of atom types (types vary in [0..ntypes-1]) +ntypes # number of atom types (types vary in [[0..ntypes-1]]) 
 startpot # file name for starting potential (*) startpot # file name for starting potential (*)
 endpot # file name for final potential (*) endpot # file name for final potential (*)
Line 147: Line 160:
 dummy_r # Distance, where dummy_rho and dummy_phi are used (ignored) dummy_r # Distance, where dummy_rho and dummy_phi are used (ignored)
  
-#optional options+# optional options
 dummy_rho # dummy value of rho at dummy_r dummy_rho # dummy value of rho at dummy_r
 dummy_phi # vector (length ntypes) dummy values of phi_ii at dummy_r dummy_phi # vector (length ntypes) dummy values of phi_ii at dummy_r
-</pre></code>+</code>
  
-Prints the values of <math>\rho_0\,</math>(dummy_r) and <math>\Phi_{ii}\,</math>(dummy_r). +Prints the values of $\rho_0$(dummy_r) and $\Phi_{ii}$(dummy_r). 
  
-If dummy_phi is given, the potential is transformed so that <math>\rho_0</math>(dummy_r)=dummy_rho and <math>\Phi_{ii}</math>(dummy_r)=dummy_phi_ii. +If dummy_phi is given, the potential is transformed so that $\rho_0$(dummy_r)=dummy_rho and $\Phi_{ii}$(dummy_r)=dummy_phi_ii. 
  
 IMD potentials and potential plot files are also written. IMD potentials and potential plot files are also written.