forked from lijiext/lammps
449 lines
24 KiB
HTML
449 lines
24 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>fix deposit 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>fix deposit 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="fix-deposit-command">
|
|
<span id="index-0"></span><h1>fix deposit command</h1>
|
|
<div class="section" id="syntax">
|
|
<h2>Syntax</h2>
|
|
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">fix</span> <span class="n">ID</span> <span class="n">group</span><span class="o">-</span><span class="n">ID</span> <span class="n">deposit</span> <span class="n">N</span> <span class="nb">type</span> <span class="n">M</span> <span class="n">seed</span> <span class="n">keyword</span> <span class="n">values</span> <span class="o">...</span>
|
|
</pre></div>
|
|
</div>
|
|
<ul class="simple">
|
|
<li>ID, group-ID are documented in <a class="reference internal" href="fix.html"><span class="doc">fix</span></a> command</li>
|
|
<li>deposit = style name of this fix command</li>
|
|
<li>N = # of atoms or molecules to insert</li>
|
|
<li>type = atom type to assign to inserted atoms (offset for moleclue insertion)</li>
|
|
<li>M = insert a single atom or molecule every M steps</li>
|
|
<li>seed = random # seed (positive integer)</li>
|
|
<li>one or more keyword/value pairs may be appended to args</li>
|
|
<li>keyword = <em>region</em> or <em>id</em> or <em>global</em> or <em>local</em> or <em>near</em> or <em>attempt</em> or <em>rate</em> or <em>vx</em> or <em>vy</em> or <em>vz</em> or <em>mol</em> or <em>rigid</em> or <em>shake</em> or <em>units</em></li>
|
|
</ul>
|
|
<pre class="literal-block">
|
|
<em>region</em> value = region-ID
|
|
region-ID = ID of region to use as insertion volume
|
|
<em>id</em> value = <em>max</em> or <em>next</em>
|
|
max = atom ID for new atom(s) is max ID of all current atoms plus one
|
|
next = atom ID for new atom(s) increments by one for every deposition
|
|
<em>global</em> values = lo hi
|
|
lo,hi = put new atom/molecule a distance lo-hi above all other atoms (distance units)
|
|
<em>local</em> values = lo hi delta
|
|
lo,hi = put new atom/molecule a distance lo-hi above any nearby atom beneath it (distance units)
|
|
delta = lateral distance within which a neighbor is considered "nearby" (distance units)
|
|
<em>near</em> value = R
|
|
R = only insert atom/molecule if further than R from existing particles (distance units)
|
|
<em>attempt</em> value = Q
|
|
Q = attempt a single insertion up to Q times
|
|
<em>rate</em> value = V
|
|
V = z velocity (y in 2d) at which insertion volume moves (velocity units)
|
|
<em>vx</em> values = vxlo vxhi
|
|
vxlo,vxhi = range of x velocities for inserted atom/molecule (velocity units)
|
|
<em>vy</em> values = vylo vyhi
|
|
vylo,vyhi = range of y velocities for inserted atom/molecule (velocity units)
|
|
<em>vz</em> values = vzlo vzhi
|
|
vzlo,vzhi = range of z velocities for inserted atom/molecule (velocity units)
|
|
<em>target</em> values = tx ty tz
|
|
tx,ty,tz = location of target point (distance units)
|
|
<em>mol</em> value = template-ID
|
|
template-ID = ID of molecule template specified in a separate <a class="reference internal" href="molecule.html"><span class="doc">molecule</span></a> command
|
|
<em>molfrac</em> values = f1 f2 ... fN
|
|
f1 to fN = relative probability of creating each of N molecules in template-ID
|
|
<em>rigid</em> value = fix-ID
|
|
fix-ID = ID of <a class="reference internal" href="fix_rigid.html"><span class="doc">fix rigid/small</span></a> command
|
|
<em>shake</em> value = fix-ID
|
|
fix-ID = ID of <a class="reference internal" href="fix_shake.html"><span class="doc">fix shake</span></a> command
|
|
<em>units</em> value = <em>lattice</em> or <em>box</em>
|
|
lattice = the geometry is defined in lattice units
|
|
box = the geometry is defined in simulation box units
|
|
</pre>
|
|
</div>
|
|
<div class="section" id="examples">
|
|
<h2>Examples</h2>
|
|
<div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">fix</span> <span class="mi">3</span> <span class="nb">all</span> <span class="n">deposit</span> <span class="mi">1000</span> <span class="mi">2</span> <span class="mi">100</span> <span class="mi">29494</span> <span class="n">region</span> <span class="n">myblock</span> <span class="n">local</span> <span class="mf">1.0</span> <span class="mf">1.0</span> <span class="mf">1.0</span> <span class="n">units</span> <span class="n">box</span>
|
|
<span class="n">fix</span> <span class="mi">2</span> <span class="n">newatoms</span> <span class="n">deposit</span> <span class="mi">10000</span> <span class="mi">1</span> <span class="mi">500</span> <span class="mi">12345</span> <span class="n">region</span> <span class="n">disk</span> <span class="n">near</span> <span class="mf">2.0</span> <span class="n">vz</span> <span class="o">-</span><span class="mf">1.0</span> <span class="o">-</span><span class="mf">0.8</span>
|
|
<span class="n">fix</span> <span class="mi">4</span> <span class="n">sputter</span> <span class="n">deposit</span> <span class="mi">1000</span> <span class="mi">2</span> <span class="mi">500</span> <span class="mi">12235</span> <span class="n">region</span> <span class="n">sphere</span> <span class="n">vz</span> <span class="o">-</span><span class="mf">1.0</span> <span class="o">-</span><span class="mf">1.0</span> <span class="n">target</span> <span class="mf">5.0</span> <span class="mf">5.0</span> <span class="mf">0.0</span> <span class="n">units</span> <span class="n">lattice</span>
|
|
</pre></div>
|
|
</div>
|
|
</div>
|
|
<div class="section" id="description">
|
|
<h2>Description</h2>
|
|
<p>Insert a single atom or molecule into the simulation domain every M
|
|
timesteps until N atoms or molecules have been inserted. This is
|
|
useful for simulating deposition onto a surface. For the remainder of
|
|
this doc page, a single inserted atom or molecule is referred to as a
|
|
“particle”.</p>
|
|
<p>If inserted particles are individual atoms, they are assigned the
|
|
specified atom type. If they are molecules, the type of each atom in
|
|
the inserted molecule is specified in the file read by the
|
|
<a class="reference internal" href="molecule.html"><span class="doc">molecule</span></a> command, and those values are added to the
|
|
specified atom type. E.g. if the file specifies atom types 1,2,3, and
|
|
those are the atom types you want for inserted molecules, then specify
|
|
<em>type</em> = 0. If you specify <em>type</em> = 2, the in the inserted molecule
|
|
will have atom types 3,4,5.</p>
|
|
<p>All atoms in the inserted particle are assigned to two groups: the
|
|
default group “all” and the group specified in the fix deposit command
|
|
(which can also be “all”).</p>
|
|
<p>If you are computing temperature values which include inserted
|
|
particles, you will want to use the
|
|
<a class="reference internal" href="compute_modify.html"><span class="doc">compute_modify</span></a> dynamic option, which insures the
|
|
current number of atoms is used as a normalizing factor each time the
|
|
temperature is computed.</p>
|
|
<p>Care must be taken that inserted particles are not too near existing
|
|
atoms, using the options described below. When inserting particles
|
|
above a surface in a non-periodic box (see the
|
|
<a class="reference internal" href="boundary.html"><span class="doc">boundary</span></a> command), the possibility of a particle
|
|
escaping the surface and flying upward should be considered, since the
|
|
particle may be lost or the box size may grow infinitely large. A
|
|
<a class="reference internal" href="fix_wall_reflect.html"><span class="doc">fix wall/reflect</span></a> command can be used to
|
|
prevent this behavior. Note that if a shrink-wrap boundary is used,
|
|
it is OK to insert the new particle outside the box, however the box
|
|
will immediately be expanded to include the new particle. When
|
|
simulating a sputtering experiment it is probably more realistic to
|
|
ignore those atoms using the <a class="reference internal" href="thermo_modify.html"><span class="doc">thermo_modify</span></a>
|
|
command with the <em>lost ignore</em> option and a fixed
|
|
<a class="reference internal" href="boundary.html"><span class="doc">boundary</span></a>.</p>
|
|
<p>The fix deposit command must use the <em>region</em> keyword to define an
|
|
insertion volume. The specified region must have been previously
|
|
defined with a <a class="reference internal" href="region.html"><span class="doc">region</span></a> command. It must be defined with
|
|
side = <em>in</em>.</p>
|
|
<div class="admonition note">
|
|
<p class="first admonition-title">Note</p>
|
|
<p class="last">LAMMPS checks that the specified region is wholly inside the
|
|
simulation box. It can do this correctly for orthonormal simulation
|
|
boxes. However for <a class="reference internal" href="Section_howto.html#howto-12"><span class="std std-ref">triclinic boxes</span></a>, it
|
|
only tests against the larger orthonormal box that bounds the tilted
|
|
simulation box. If the specified region includes volume outside the
|
|
tilted box, then an insertion will likely fail, leading to a “lost
|
|
atoms” error. Thus for triclinic boxes you should insure the
|
|
specified region is wholly inside the simulation box.</p>
|
|
</div>
|
|
<p>Individual atoms are inserted, unless the <em>mol</em> keyword is used. It
|
|
specifies a <em>template-ID</em> previously defined using the
|
|
<a class="reference internal" href="molecule.html"><span class="doc">molecule</span></a> command, which reads files that define one or
|
|
more molecules. The coordinates, atom types, charges, etc, as well as
|
|
any bond/angle/etc and special neighbor information for the molecule
|
|
can be specified in the molecule file. See the
|
|
<a class="reference internal" href="molecule.html"><span class="doc">molecule</span></a> command for details. The only settings
|
|
required to be in each file are the coordinates and types of atoms in
|
|
the molecule.</p>
|
|
<p>If the molecule template contains more than one molecule, the relative
|
|
probability of depositing each molecule can be specified by the
|
|
<em>molfrac</em> keyword. N relative probablities, each from 0.0 to 1.0, are
|
|
specified, where N is the number of molecules in the template. Each
|
|
time a molecule is deposited, a random number is used to sample from
|
|
the list of relative probabilities. The N values must sum to 1.0.</p>
|
|
<p>If you wish to insert molecules via the <em>mol</em> keyword, that will be
|
|
treated as rigid bodies, use the <em>rigid</em> keyword, specifying as its
|
|
value the ID of a separate <span class="xref doc">fix rigid/small</span>
|
|
command which also appears in your input script.</p>
|
|
<p>If you wish to insert molecules via the <em>mol</em> keyword, that will have
|
|
their bonds or angles constrained via SHAKE, use the <em>shake</em> keyword,
|
|
specifying as its value the ID of a separate <a class="reference internal" href="fix_shake.html"><span class="doc">fix shake</span></a> command which also appears in your input script.</p>
|
|
<p>Each timestep a particle is inserted, the coordinates for its atoms
|
|
are chosen as follows. For insertion of individual atoms, the
|
|
“position” referred to in the following description is the coordinate
|
|
of the atom. For insertion of molecule, the “position” is the
|
|
geometric center of the molecule; see the <a class="reference internal" href="molecule.html"><span class="doc">molecule</span></a> doc
|
|
page for details. A random rotation of the molecule around its center
|
|
point is performed, which determines the coordinates all the
|
|
individual atoms.</p>
|
|
<p>A random position within the region insertion volume is generated. If
|
|
neither the <em>global</em> or <em>local</em> keyword is used, the random position
|
|
is the trial position. If the <em>global</em> keyword is used, the random
|
|
x,y values are used, but the z position of the new particle is set
|
|
above the highest current atom in the simulation by a distance
|
|
randomly chosen between lo/hi. (For a 2d simulation, this is done for
|
|
the y position.) If the <em>local</em> keyword is used, the z position is
|
|
set a distance between lo/hi above the highest current atom in the
|
|
simulation that is “nearby” the chosen x,y position. In this context,
|
|
“nearby” means the lateral distance (in x,y) between the new and old
|
|
particles is less than the <em>delta</em> setting.</p>
|
|
<p>Once a trial x,y,z position has been selected, the insertion is only
|
|
performed if no current atom in the simulation is within a distance R
|
|
of any atom in the new particle, including the effect of periodic
|
|
boundary conditions if applicable. R is defined by the <em>near</em>
|
|
keyword. Note that the default value for R is 0.0, which will allow
|
|
atoms to strongly overlap if you are inserting where other atoms are
|
|
present. This distance test is performed independently for each atom
|
|
in an inserted molecule, based on the randomly rotated configuration
|
|
of the molecule. If this test fails, a new random position within the
|
|
insertion volume is chosen and another trial is made. Up to Q
|
|
attempts are made. If the particle is not successfully inserted,
|
|
LAMMPS prints a warning message.</p>
|
|
<div class="admonition note">
|
|
<p class="first admonition-title">Note</p>
|
|
<p class="last">If you are inserting finite size particles or a molecule or
|
|
rigid body consisting of finite-size particles, then you should
|
|
typically set R larger than the distance at which any inserted
|
|
particle may overlap with either a previouly inserted particle or an
|
|
existing particle. LAMMPS will issue a warning if R is smaller than
|
|
this value, based on the radii of existing and inserted particles.</p>
|
|
</div>
|
|
<p>The <em>rate</em> option moves the insertion volume in the z direction (3d)
|
|
or y direction (2d). This enables particles to be inserted from a
|
|
successively higher height over time. Note that this parameter is
|
|
ignored if the <em>global</em> or <em>local</em> keywords are used, since those
|
|
options choose a z-coordinate for insertion independently.</p>
|
|
<p>The vx, vy, and vz components of velocity for the inserted particle
|
|
are set using the values specified for the <em>vx</em>, <em>vy</em>, and <em>vz</em>
|
|
keywords. Note that normally, new particles should be a assigned a
|
|
negative vertical velocity so that they move towards the surface. For
|
|
molecules, the same velocity is given to every particle (no rotation
|
|
or bond vibration).</p>
|
|
<p>If the <em>target</em> option is used, the velocity vector of the inserted
|
|
particle is changed so that it points from the insertion position
|
|
towards the specified target point. The magnitude of the velocity is
|
|
unchanged. This can be useful, for example, for simulating a
|
|
sputtering process. E.g. the target point can be far away, so that
|
|
all incident particles strike the surface as if they are in an
|
|
incident beam of particles at a prescribed angle.</p>
|
|
<p>The <em>id</em> keyword determines how atom IDs and molecule IDs are assigned
|
|
to newly deposited particles. Molecule IDs are only assigned if
|
|
molecules are being inserted. For the <em>max</em> setting, the atom and
|
|
molecule IDs of all current atoms are checked. Atoms in the new
|
|
particle are assigned IDs starting with the current maximum plus one.
|
|
If a molecule is inserted it is assigned an ID = current maximum plus
|
|
one. This means that if particles leave the system, the new IDs may
|
|
replace the lost ones. For the <em>next</em> setting, the maximum ID of any
|
|
atom and molecule is stored at the time the fix is defined. Each time
|
|
a new particle is added, this value is incremented to assign IDs to
|
|
the new atom(s) or molecule. Thus atom and molecule IDs for deposited
|
|
particles will be consecutive even if particles leave the system over
|
|
time.</p>
|
|
<p>The <em>units</em> keyword determines the meaning of the distance units used
|
|
for the other deposition parameters. A <em>box</em> value selects standard
|
|
distance units as defined by the <a class="reference internal" href="units.html"><span class="doc">units</span></a> command,
|
|
e.g. Angstroms for units = real or metal. A <em>lattice</em> value means the
|
|
distance units are in lattice spacings. The <a class="reference internal" href="lattice.html"><span class="doc">lattice</span></a>
|
|
command must have been previously used to define the lattice spacing.
|
|
Note that the units choice affects all the keyword values that have
|
|
units of distance or velocity.</p>
|
|
<div class="admonition note">
|
|
<p class="first admonition-title">Note</p>
|
|
<p class="last">If you are monitoring the temperature of a system where the atom
|
|
count is changing due to adding particles, you typically should use
|
|
the <a class="reference internal" href="compute_modify.html"><span class="doc">compute_modify dynamic yes</span></a> command for the
|
|
temperature compute you are using.</p>
|
|
</div>
|
|
</div>
|
|
<div class="section" id="restart-fix-modify-output-run-start-stop-minimize-info">
|
|
<h2>Restart, fix_modify, output, run start/stop, minimize info</h2>
|
|
<p>This fix writes the state of the deposition to <a class="reference internal" href="restart.html"><span class="doc">binary restart files</span></a>. This includes information about how many
|
|
particles have been depositied, the random number generator seed, the
|
|
next timestep for deposition, etc. See the
|
|
<a class="reference internal" href="read_restart.html"><span class="doc">read_restart</span></a> command for info on how to re-specify
|
|
a fix in an input script that reads a restart file, so that the
|
|
operation of the fix continues in an uninterrupted fashion.</p>
|
|
<p>None of the <a class="reference internal" href="fix_modify.html"><span class="doc">fix_modify</span></a> options are relevant to this
|
|
fix. No global or per-atom quantities are stored by this fix for
|
|
access by various <a class="reference internal" href="Section_howto.html#howto-15"><span class="std std-ref">output commands</span></a>. No
|
|
parameter of this fix can be used with the <em>start/stop</em> keywords of
|
|
the <a class="reference internal" href="run.html"><span class="doc">run</span></a> command. This fix is not invoked during <a class="reference internal" href="minimize.html"><span class="doc">energy minimization</span></a>.</p>
|
|
</div>
|
|
<div class="section" id="restrictions">
|
|
<h2>Restrictions</h2>
|
|
<p>This fix is part of the MISC package. It is only enabled if LAMMPS
|
|
was built with that package. See the <a class="reference internal" href="Section_start.html#start-3"><span class="std std-ref">Making LAMMPS</span></a> section for more info.</p>
|
|
<p>The specified insertion region cannot be a “dynamic” region, as
|
|
defined by the <a class="reference internal" href="region.html"><span class="doc">region</span></a> command.</p>
|
|
</div>
|
|
<div class="section" id="related-commands">
|
|
<h2>Related commands</h2>
|
|
<p><a class="reference internal" href="fix_pour.html"><span class="doc">fix pour</span></a>, <a class="reference internal" href="region.html"><span class="doc">region</span></a></p>
|
|
</div>
|
|
<div class="section" id="default">
|
|
<h2>Default</h2>
|
|
<p>Insertions are performed for individual atoms, i.e. no <em>mol</em> setting
|
|
is defined. If the <em>mol</em> keyword is used, the default for <em>molfrac</em>
|
|
is an equal probabilities for all molecules in the template.
|
|
Additional option defaults are id = max, delta = 0.0, near = 0.0,
|
|
attempt = 10, rate = 0.0, vx = 0.0 0.0, vy = 0.0 0.0, vz = 0.0 0.0,
|
|
and units = lattice.</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> |