lammps/doc/html/pair_write.html

260 lines
10 KiB
HTML

<!DOCTYPE html>
<!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]-->
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>pair_write command &mdash; LAMMPS documentation</title>
<link rel="stylesheet" href="_static/css/theme.css" type="text/css" />
<link rel="stylesheet" href="_static/sphinxcontrib-images/LightBox2/lightbox2/css/lightbox.css" type="text/css" />
<link rel="top" title="LAMMPS documentation" href="index.html"/>
<script src="_static/js/modernizr.min.js"></script>
</head>
<body class="wy-body-for-nav" role="document">
<div class="wy-grid-for-nav">
<nav data-toggle="wy-nav-shift" class="wy-nav-side">
<div class="wy-side-nav-search">
<a href="Manual.html" class="icon icon-home"> LAMMPS
</a>
<div role="search">
<form id="rtd-search-form" class="wy-form" action="search.html" method="get">
<input type="text" name="q" placeholder="Search docs" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
</div>
<div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
<ul>
<li class="toctree-l1"><a class="reference internal" href="Section_intro.html">1. Introduction</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_start.html">2. Getting Started</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_commands.html">3. Commands</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_packages.html">4. Packages</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_accelerate.html">5. Accelerating LAMMPS performance</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_howto.html">6. How-to discussions</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_example.html">7. Example problems</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_perf.html">8. Performance &amp; scalability</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_tools.html">9. Additional tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_modify.html">10. Modifying &amp; extending LAMMPS</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_python.html">11. Python interface to LAMMPS</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_errors.html">12. Errors</a></li>
<li class="toctree-l1"><a class="reference internal" href="Section_history.html">13. Future and history</a></li>
</ul>
</div>
&nbsp;
</nav>
<section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
<nav class="wy-nav-top" role="navigation" aria-label="top navigation">
<i data-toggle="wy-nav-top" class="fa fa-bars"></i>
<a href="Manual.html">LAMMPS</a>
</nav>
<div class="wy-nav-content">
<div class="rst-content">
<div role="navigation" aria-label="breadcrumbs navigation">
<ul class="wy-breadcrumbs">
<li><a href="Manual.html">Docs</a> &raquo;</li>
<li>pair_write command</li>
<li class="wy-breadcrumbs-aside">
<a href="http://lammps.sandia.gov">Website</a>
<a href="Section_commands.html#comm">Commands</a>
</li>
</ul>
<hr/>
</div>
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<div itemprop="articleBody">
<div class="section" id="pair-write-command">
<span id="index-0"></span><h1>pair_write command</h1>
<div class="section" id="syntax">
<h2>Syntax</h2>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">pair_write</span> <span class="n">itype</span> <span class="n">jtype</span> <span class="n">N</span> <span class="n">style</span> <span class="n">inner</span> <span class="n">outer</span> <span class="n">file</span> <span class="n">keyword</span> <span class="n">Qi</span> <span class="n">Qj</span>
</pre></div>
</div>
<ul class="simple">
<li>itype,jtype = 2 atom types</li>
<li>N = # of values</li>
<li>style = <em>r</em> or <em>rsq</em> or <em>bitmap</em></li>
<li>inner,outer = inner and outer cutoff (distance units)</li>
<li>file = name of file to write values to</li>
<li>keyword = section name in file for this set of tabulated values</li>
<li>Qi,Qj = 2 atom charges (charge units) (optional)</li>
</ul>
</div>
<div class="section" id="examples">
<h2>Examples</h2>
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">pair_write</span> <span class="mi">1</span> <span class="mi">3</span> <span class="mi">500</span> <span class="n">r</span> <span class="mf">1.0</span> <span class="mf">10.0</span> <span class="n">table</span><span class="o">.</span><span class="n">txt</span> <span class="n">LJ</span>
<span class="n">pair_write</span> <span class="mi">1</span> <span class="mi">1</span> <span class="mi">1000</span> <span class="n">rsq</span> <span class="mf">2.0</span> <span class="mf">8.0</span> <span class="n">table</span><span class="o">.</span><span class="n">txt</span> <span class="n">Yukawa_1_1</span> <span class="o">-</span><span class="mf">0.5</span> <span class="mf">0.5</span>
</pre></div>
</div>
</div>
<div class="section" id="description">
<h2>Description</h2>
<p>Write energy and force values to a file as a function of distance for
the currently defined pair potential. This is useful for plotting the
potential function or otherwise debugging its values. If the file
already exists, the table of values is appended to the end of the file
to allow multiple tables of energy and force to be included in one
file.</p>
<p>The energy and force values are computed at distances from inner to
outer for 2 interacting atoms of type itype and jtype, using the
appropriate <a class="reference internal" href="pair_coeff.html"><span class="doc">pair_coeff</span></a> coefficients. If the style
is <em>r</em>, then N distances are used, evenly spaced in r; if the style is
<em>rsq</em>, N distances are used, evenly spaced in r^2.</p>
<p>For example, for N = 7, style = <em>r</em>, inner = 1.0, and outer = 4.0,
values are computed at r = 1.0, 1.5, 2.0, 2.5, 3.0, 3.5, 4.0.</p>
<p>If the style is <em>bitmap</em>, then 2^N values are written to the file in a
format and order consistent with how they are read in by the
<a class="reference internal" href="pair_coeff.html"><span class="doc">pair_coeff</span></a> command for pair style <em>table</em>. For
reasonable accuracy in a bitmapped table, choose N &gt;= 12, an <em>inner</em>
value that is smaller than the distance of closest approach of 2
atoms, and an <em>outer</em> value &lt;= cutoff of the potential.</p>
<p>If the pair potential is computed between charged atoms, the charges
of the pair of interacting atoms can optionally be specified. If not
specified, values of Qi = Qj = 1.0 are used.</p>
<p>The file is written in the format used as input for the
<a class="reference internal" href="pair_style.html"><span class="doc">pair_style</span></a> <em>table</em> option with <em>keyword</em> as the
section name. Each line written to the file lists an index number
(1-N), a distance (in distance units), an energy (in energy units),
and a force (in force units).</p>
</div>
<div class="section" id="restrictions">
<h2>Restrictions</h2>
<p>All force field coefficients for pair and other kinds of interactions
must be set before this command can be invoked.</p>
<p>Due to how the pairwise force is computed, an inner value &gt; 0.0 must
be specified even if the potential has a finite value at r = 0.0.</p>
<p>For EAM potentials, the pair_write command only tabulates the
pairwise portion of the potential, not the embedding portion.</p>
</div>
<div class="section" id="related-commands">
<h2>Related commands</h2>
<p><a class="reference internal" href="pair_table.html"><span class="doc">pair_style table</span></a>,
<a class="reference internal" href="pair_style.html"><span class="doc">pair_style</span></a>, <a class="reference internal" href="pair_coeff.html"><span class="doc">pair_coeff</span></a></p>
<p><strong>Default:</strong> none</p>
</div>
</div>
</div>
</div>
<footer>
<hr/>
<div role="contentinfo">
<p>
&copy; Copyright 2013 Sandia Corporation.
</p>
</div>
Built with <a href="http://sphinx-doc.org/">Sphinx</a> using a <a href="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <a href="https://readthedocs.org">Read the Docs</a>.
</footer>
</div>
</div>
</section>
</div>
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT:'./',
VERSION:'',
COLLAPSE_INDEX:false,
FILE_SUFFIX:'.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<script type="text/javascript" src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
<script type="text/javascript" src="_static/sphinxcontrib-images/LightBox2/lightbox2/js/jquery-1.11.0.min.js"></script>
<script type="text/javascript" src="_static/sphinxcontrib-images/LightBox2/lightbox2/js/lightbox.min.js"></script>
<script type="text/javascript" src="_static/sphinxcontrib-images/LightBox2/lightbox2-customize/jquery-noconflict.js"></script>
<script type="text/javascript" src="_static/js/theme.js"></script>
<script type="text/javascript">
jQuery(function () {
SphinxRtdTheme.StickyNav.enable();
});
</script>
</body>
</html>