forked from lijiext/lammps
434 lines
23 KiB
HTML
434 lines
23 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_modify command — 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 & 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 & 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>
|
|
|
|
</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> »</li>
|
|
|
|
<li>pair_modify 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-modify-command">
|
|
<span id="index-0"></span><h1>pair_modify command</h1>
|
|
<div class="section" id="syntax">
|
|
<h2>Syntax</h2>
|
|
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">pair_modify</span> <span class="n">keyword</span> <span class="n">values</span> <span class="o">...</span>
|
|
</pre></div>
|
|
</div>
|
|
<ul class="simple">
|
|
<li>one or more keyword/value pairs may be listed</li>
|
|
<li>keyword = <em>pair</em> or <em>shift</em> or <em>mix</em> or <em>table</em> or <em>table/disp</em> or <em>tabinner</em> or <em>tabinner/disp</em> or <em>tail</em> or <em>compute</em></li>
|
|
</ul>
|
|
<pre class="literal-block">
|
|
<em>pair</em> values = sub-style N <em>special</em> which wt1 wt2 wt3
|
|
sub-style = sub-style of <a class="reference internal" href="pair_hybrid.html"><span class="doc">pair hybrid</span></a>
|
|
N = which instance of sub-style (only if sub-style is used multiple times)
|
|
<em>special</em> which wt1 wt2 wt3 = override <em>special_bonds</em> settings (optional)
|
|
which = <em>lj/coul</em> or <em>lj</em> or <em>coul</em>
|
|
w1,w2,w3 = 1-2, 1-3, and 1-4 weights from 0.0 to 1.0 inclusive
|
|
<em>mix</em> value = <em>geometric</em> or <em>arithmetic</em> or <em>sixthpower</em>
|
|
<em>shift</em> value = <em>yes</em> or <em>no</em>
|
|
<em>table</em> value = N
|
|
2^N = # of values in table
|
|
<em>table/disp</em> value = N
|
|
2^N = # of values in table
|
|
<em>tabinner</em> value = cutoff
|
|
cutoff = inner cutoff at which to begin table (distance units)
|
|
<em>tabinner/disp</em> value = cutoff
|
|
cutoff = inner cutoff at which to begin table (distance units)
|
|
<em>tail</em> value = <em>yes</em> or <em>no</em>
|
|
<em>compute</em> value = <em>yes</em> or <em>no</em>
|
|
</pre>
|
|
</div>
|
|
<div class="section" id="examples">
|
|
<h2>Examples</h2>
|
|
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">pair_modify</span> <span class="n">shift</span> <span class="n">yes</span> <span class="n">mix</span> <span class="n">geometric</span>
|
|
<span class="n">pair_modify</span> <span class="n">tail</span> <span class="n">yes</span>
|
|
<span class="n">pair_modify</span> <span class="n">table</span> <span class="mi">12</span>
|
|
<span class="n">pair_modify</span> <span class="n">pair</span> <span class="n">lj</span><span class="o">/</span><span class="n">cut</span> <span class="n">compute</span> <span class="n">no</span>
|
|
<span class="n">pair_modify</span> <span class="n">pair</span> <span class="n">lj</span><span class="o">/</span><span class="n">cut</span><span class="o">/</span><span class="n">coul</span><span class="o">/</span><span class="n">long</span> <span class="mi">1</span> <span class="n">special</span> <span class="n">lj</span><span class="o">/</span><span class="n">coul</span> <span class="mf">0.0</span> <span class="mf">0.0</span> <span class="mf">0.0</span>
|
|
</pre></div>
|
|
</div>
|
|
</div>
|
|
<div class="section" id="description">
|
|
<h2>Description</h2>
|
|
<p>Modify the parameters of the currently defined pair style. Not all
|
|
parameters are relevant to all pair styles.</p>
|
|
<p>If used, the <em>pair</em> keyword must appear first in the list of keywords.
|
|
It can only be used with the <a class="reference internal" href="pair_hybrid.html"><span class="doc">hybrid and hybrid/overlay</span></a> pair styles. It means that all the
|
|
following parameters will only be modified for the specified
|
|
sub-style. If the sub-style is defined multiple times, then an
|
|
additional numeric argument <em>N</em> must also be specified, which is a
|
|
number from 1 to M where M is the number of times the sub-style was
|
|
listed in the <a class="reference internal" href="pair_hybrid.html"><span class="doc">pair_style hybrid</span></a> command. The extra
|
|
number indicates which instance of the sub-style the remaining
|
|
keywords will be applied to. Note that if the <em>pair</em> keyword is not
|
|
used, and the pair style is <em>hybrid</em> or <em>hybrid/overlay</em>, then all the
|
|
specified keywords will be applied to all sub-styles.</p>
|
|
<p>The <em>special</em> keyword can only be used in conjunction with the <em>pair</em>
|
|
keyword and must directly follow it. It allows to override the
|
|
<a class="reference internal" href="special_bonds.html"><span class="doc">special_bonds</span></a> settings for the specified sub-style.
|
|
More details are given below.</p>
|
|
<p>The <em>mix</em> keyword affects pair coefficients for interactions between
|
|
atoms of type I and J, when I != J and the coefficients are not
|
|
explicitly set in the input script. Note that coefficients for I = J
|
|
must be set explicitly, either in the input script via the
|
|
“pair_coeff” command or in the “Pair Coeffs” section of the <a class="reference internal" href="read_data.html"><span class="doc">data file</span></a>. For some pair styles it is not necessary to
|
|
specify coefficients when I != J, since a “mixing” rule will create
|
|
them from the I,I and J,J settings. The pair_modify <em>mix</em> value
|
|
determines what formulas are used to compute the mixed coefficients.
|
|
In each case, the cutoff distance is mixed the same way as sigma.</p>
|
|
<p>Note that not all pair styles support mixing. Also, some mix options
|
|
are not available for certain pair styles. See the doc page for
|
|
individual pair styles for those restrictions. Note also that the
|
|
<a class="reference internal" href="pair_coeff.html"><span class="doc">pair_coeff</span></a> command also can be to directly set
|
|
coefficients for a specific I != J pairing, in which case no mixing is
|
|
performed.</p>
|
|
<p>mix <em>geometric</em></p>
|
|
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">epsilon_ij</span> <span class="o">=</span> <span class="n">sqrt</span><span class="p">(</span><span class="n">epsilon_i</span> <span class="o">*</span> <span class="n">epsilon_j</span><span class="p">)</span>
|
|
<span class="n">sigma_ij</span> <span class="o">=</span> <span class="n">sqrt</span><span class="p">(</span><span class="n">sigma_i</span> <span class="o">*</span> <span class="n">sigma_j</span><span class="p">)</span>
|
|
</pre></div>
|
|
</div>
|
|
<p>mix <em>arithmetic</em></p>
|
|
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">epsilon_ij</span> <span class="o">=</span> <span class="n">sqrt</span><span class="p">(</span><span class="n">epsilon_i</span> <span class="o">*</span> <span class="n">epsilon_j</span><span class="p">)</span>
|
|
<span class="n">sigma_ij</span> <span class="o">=</span> <span class="p">(</span><span class="n">sigma_i</span> <span class="o">+</span> <span class="n">sigma_j</span><span class="p">)</span> <span class="o">/</span> <span class="mi">2</span>
|
|
</pre></div>
|
|
</div>
|
|
<p>mix <em>sixthpower</em></p>
|
|
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">epsilon_ij</span> <span class="o">=</span> <span class="p">(</span><span class="mi">2</span> <span class="o">*</span> <span class="n">sqrt</span><span class="p">(</span><span class="n">epsilon_i</span><span class="o">*</span><span class="n">epsilon_j</span><span class="p">)</span> <span class="o">*</span> <span class="n">sigma_i</span><span class="o">^</span><span class="mi">3</span> <span class="o">*</span> <span class="n">sigma_j</span><span class="o">^</span><span class="mi">3</span><span class="p">)</span> <span class="o">/</span>
|
|
<span class="p">(</span><span class="n">sigma_i</span><span class="o">^</span><span class="mi">6</span> <span class="o">+</span> <span class="n">sigma_j</span><span class="o">^</span><span class="mi">6</span><span class="p">)</span>
|
|
<span class="n">sigma_ij</span> <span class="o">=</span> <span class="p">((</span><span class="n">sigma_i</span><span class="o">**</span><span class="mi">6</span> <span class="o">+</span> <span class="n">sigma_j</span><span class="o">**</span><span class="mi">6</span><span class="p">)</span> <span class="o">/</span> <span class="mi">2</span><span class="p">)</span> <span class="o">^</span> <span class="p">(</span><span class="mi">1</span><span class="o">/</span><span class="mi">6</span><span class="p">)</span>
|
|
</pre></div>
|
|
</div>
|
|
<p>The <em>shift</em> keyword determines whether a Lennard-Jones potential is
|
|
shifted at its cutoff to 0.0. If so, this adds an energy term to each
|
|
pairwise interaction which will be included in the thermodynamic
|
|
output, but does not affect pair forces or atom trajectories. See the
|
|
doc page for individual pair styles to see which ones support this
|
|
option.</p>
|
|
<p>The <em>table</em> and <em>table/disp</em> keywords apply to pair styles with a
|
|
long-range Coulombic term or long-range dispersion term respectively;
|
|
see the doc page for individual styles to see which potentials support
|
|
these options. If N is non-zero, a table of length 2^N is
|
|
pre-computed for forces and energies, which can shrink their
|
|
computational cost by up to a factor of 2. The table is indexed via a
|
|
bit-mapping technique <a class="reference internal" href="pair_table_rx.html#wolff"><span class="std std-ref">(Wolff)</span></a> and a linear interpolation is
|
|
performed between adjacent table values. In our experiments with
|
|
different table styles (lookup, linear, spline), this method typically
|
|
gave the best performance in terms of speed and accuracy.</p>
|
|
<p>The choice of table length is a tradeoff in accuracy versus speed. A
|
|
larger N yields more accurate force computations, but requires more
|
|
memory which can slow down the computation due to cache misses. A
|
|
reasonable value of N is between 8 and 16. The default value of 12
|
|
(table of length 4096) gives approximately the same accuracy as the
|
|
no-table (N = 0) option. For N = 0, forces and energies are computed
|
|
directly, using a polynomial fit for the needed erfc() function
|
|
evaluation, which is what earlier versions of LAMMPS did. Values
|
|
greater than 16 typically slow down the simulation and will not
|
|
improve accuracy; values from 1 to 8 give unreliable results.</p>
|
|
<p>The <em>tabinner</em> and <em>tabinner/disp</em> keywords set an inner cutoff above
|
|
which the pairwise computation is done by table lookup (if tables are
|
|
invoked), for the corresponding Coulombic and dispersion tables
|
|
discussed with the <em>table</em> and <em>table/disp</em> keywords. The smaller the
|
|
cutoff is set, the less accurate the table becomes (for a given number
|
|
of table values), which can require use of larger tables. The default
|
|
cutoff value is sqrt(2.0) distance units which means nearly all
|
|
pairwise interactions are computed via table lookup for simulations
|
|
with “real” units, but some close pairs may be computed directly
|
|
(non-table) for simulations with “lj” units.</p>
|
|
<p>When the <em>tail</em> keyword is set to <em>yes</em>, certain pair styles will add
|
|
a long-range VanderWaals tail “correction” to the energy and pressure.
|
|
These corrections are bookkeeping terms which do not affect dynamics,
|
|
unless a constant-pressure simulation is being performed. See the doc
|
|
page for individual styles to see which support this option. These
|
|
corrections are included in the calculation and printing of
|
|
thermodynamic quantities (see the <a class="reference internal" href="thermo_style.html"><span class="doc">thermo_style</span></a>
|
|
command). Their effect will also be included in constant NPT or NPH
|
|
simulations where the pressure influences the simulation box
|
|
dimensions (e.g. the <a class="reference internal" href="fix_nh.html"><span class="doc">fix npt</span></a> and <a class="reference internal" href="fix_nh.html"><span class="doc">fix nph</span></a>
|
|
commands). The formulas used for the long-range corrections come from
|
|
equation 5 of <a class="reference internal" href="#sun"><span class="std std-ref">(Sun)</span></a>.</p>
|
|
<div class="admonition note">
|
|
<p class="first admonition-title">Note</p>
|
|
<p class="last">The tail correction terms are computed at the beginning of each
|
|
run, using the current atom counts of each atom type. If atoms are
|
|
deleted (or lost) or created during a simulation, e.g. via the <a class="reference internal" href="fix_gcmc.html"><span class="doc">fix gcmc</span></a> command, the correction factors are not
|
|
re-computed. If you expect the counts to change dramatically, you can
|
|
break a run into a series of shorter runs so that the correction
|
|
factors are re-computed more frequently.</p>
|
|
</div>
|
|
<p>Several additional assumptions are inherent in using tail corrections,
|
|
including the following:</p>
|
|
<ul class="simple">
|
|
<li>The simulated system is a 3d bulk homogeneous liquid. This option
|
|
should not be used for systems that are non-liquid, 2d, have a slab
|
|
geometry (only 2d periodic), or inhomogeneous.</li>
|
|
<li>G(r), the radial distribution function (rdf), is unity beyond the
|
|
cutoff, so a fairly large cutoff should be used (i.e. 2.5 sigma for an
|
|
LJ fluid), and it is probably a good idea to verify this assumption by
|
|
checking the rdf. The rdf is not exactly unity beyond the cutoff for
|
|
each pair of interaction types, so the tail correction is necessarily
|
|
an approximation.</li>
|
|
</ul>
|
|
<p>The tail corrections are computed at the beginning of each simulation
|
|
run. If the number of atoms changes during the run, e.g. due to atoms
|
|
leaving the simulation domain, or use of the <a class="reference internal" href="fix_gcmc.html"><span class="doc">fix gcmc</span></a>
|
|
command, then the corrections are not updates to relect the changed
|
|
atom count. If this is a large effect in your simulation, you should
|
|
break the long run into several short runs, so that the correction
|
|
factors are re-computed multiple times.</p>
|
|
<ul class="simple">
|
|
<li>Thermophysical properties obtained from calculations with this option
|
|
enabled will not be thermodynamically consistent with the truncated
|
|
force-field that was used. In other words, atoms do not feel any LJ
|
|
pair interactions beyond the cutoff, but the energy and pressure
|
|
reported by the simulation include an estimated contribution from
|
|
those interactions.</li>
|
|
</ul>
|
|
<p>The <em>compute</em> keyword allows pairwise computations to be turned off,
|
|
even though a <a class="reference internal" href="pair_style.html"><span class="doc">pair_style</span></a> is defined. This is not
|
|
useful for running a real simulation, but can be useful for debugging
|
|
purposes or for performing a <a class="reference internal" href="rerun.html"><span class="doc">rerun</span></a> simulation, when you
|
|
only wish to compute partial forces that do not include the pairwise
|
|
contribution.</p>
|
|
<p>Two examples are as follows. First, this option allows you to perform
|
|
a simulation with <a class="reference internal" href="pair_hybrid.html"><span class="doc">pair_style hybrid</span></a> with only a
|
|
subset of the hybrid sub-styles enabled. Second, this option allows
|
|
you to perform a simulation with only long-range interactions but no
|
|
short-range pairwise interactions. Doing this by simply not defining
|
|
a pair style will not work, because the
|
|
<a class="reference internal" href="kspace_style.html"><span class="doc">kspace_style</span></a> command requires a Kspace-compatible
|
|
pair style be defined.</p>
|
|
<hr class="docutils" />
|
|
<div class="section" id="use-of-special-keyword">
|
|
<h3>Use of <em>special</em> keyword</h3>
|
|
<p>The <em>special</em> keyword allows to override the 1-2, 1-3, and 1-4
|
|
exclusion settings for individual sub-styles of a
|
|
<a class="reference internal" href="pair_hybrid.html"><span class="doc">hybrid pair style</span></a>. It requires 4 arguments similar
|
|
to the <a class="reference internal" href="special_bonds.html"><span class="doc">special_bonds</span></a> command, <em>which</em> and
|
|
wt1,wt2,wt3. The <em>which</em> argument can be <em>lj</em> to change the
|
|
Lennard-Jones settings, <em>coul</em> to change the Coulombic settings,
|
|
or <em>lj/coul</em> to change both to the same set of 3 values. The wt1,wt2,wt3
|
|
values are numeric weights from 0.0 to 1.0 inclusive, for the 1-2,
|
|
1-3, and 1-4 bond topology neighbors, respectively. The <em>special</em>
|
|
keyword can only be used in conjunction with the <em>pair</em> keyword
|
|
and has to directly follow it.</p>
|
|
<div class="admonition note">
|
|
<p class="first admonition-title">Note</p>
|
|
<p class="last">The global settings specified by the
|
|
<a class="reference internal" href="special_bonds.html"><span class="doc">special_bonds</span></a> command affect the construction of
|
|
neighbor lists. Weights of 0.0 (for 1-2, 1-3, or 1-4 neighbors)
|
|
exclude those pairs from the neighbor list entirely. Weights of 1.0
|
|
store the neighbor with no weighting applied. Thus only global values
|
|
different from exactly 0.0 or 1.0 can be overridden and an error is
|
|
generated if the requested setting is not compatible with the global
|
|
setting. Substituting 1.0e-10 for 0.0 and 0.9999999999 for 1.0 is
|
|
usually a sufficient workaround in this case without causing a
|
|
significant error.</p>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<hr class="docutils" />
|
|
<div class="section" id="restrictions">
|
|
<h2>Restrictions</h2>
|
|
<blockquote>
|
|
<div>none</div></blockquote>
|
|
<p>You cannot use <em>shift</em> yes with <em>tail</em> yes, since those are
|
|
conflicting options. You cannot use <em>tail</em> yes with 2d simulations.</p>
|
|
</div>
|
|
<div class="section" id="related-commands">
|
|
<h2>Related commands</h2>
|
|
<p><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>,
|
|
<a class="reference internal" href="thermo_style.html"><span class="doc">thermo_style</span></a></p>
|
|
</div>
|
|
<div class="section" id="default">
|
|
<h2>Default</h2>
|
|
<p>The option defaults are mix = geometric, shift = no, table = 12,
|
|
tabinner = sqrt(2.0), tail = no, and compute = yes.</p>
|
|
<p>Note that some pair styles perform mixing, but only a certain style of
|
|
mixing. See the doc pages for individual pair styles for details.</p>
|
|
<hr class="docutils" />
|
|
<p id="wolff"><strong>(Wolff)</strong> Wolff and Rudd, Comp Phys Comm, 120, 200-32 (1999).</p>
|
|
<p id="sun"><strong>(Sun)</strong> Sun, J Phys Chem B, 102, 7338-7364 (1998).</p>
|
|
</div>
|
|
</div>
|
|
|
|
|
|
</div>
|
|
</div>
|
|
<footer>
|
|
|
|
|
|
<hr/>
|
|
|
|
<div role="contentinfo">
|
|
<p>
|
|
© 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> |