<h2>Description<aclass="headerlink"href="#description"title="Permalink to this headline">¶</a></h2>
<p>Style <em>dsmc</em> computes collisions between pairs of particles for a
direct simulation Monte Carlo (DSMC) model following the exposition in
<aclass="reference internal"href="#bird"><span>(Bird)</span></a>. Each collision resets the velocities of the two
particles involved. The number of pairwise collisions for each pair
or particle types and the length scale within which they occur are
determined by the parameters of the pair_style and pair_coeff
commands.</p>
<p>Stochastic collisions are performed using the variable hard sphere
(VHS) approach, with the user-defined <em>max_cell_size</em> value used as
the maximum DSMC cell size, and reference cross-sections for
collisions given using the pair_coeff command.</p>
<p>There is no pairwise energy or virial contributions associated with
this pair style.</p>
<p>The following coefficient must be defined for each pair of atoms types
via the <aclass="reference internal"href="pair_coeff.html"><em>pair_coeff</em></a> command as in the examples above,
or in the data file or restart files read by the
<aclass="reference internal"href="read_data.html"><em>read_data</em></a> or <aclass="reference internal"href="read_restart.html"><em>read_restart</em></a>
commands:</p>
<ulclass="simple">
<li>sigma (area units, i.e. distance-squared)</li>
</ul>
<p>The global DSMC <em>max_cell_size</em> determines the maximum cell length
used in the DSMC calculation. A structured mesh is overlayed on the
simulation box such that an integer number of cells are created in
each direction for each processor’s sub-domain. Cell lengths are
adjusted up to the user-specified maximum cell size.</p>
<hrclass="docutils"/>
<p>To perform a DSMC simulation with LAMMPS, several additional options
should be set in your input script, though LAMMPS does not check for
these settings.</p>
<p>Since this pair style does not compute particle forces, you should use
the “fix nve/noforce” time integration fix for the DSMC particles,
e.g.</p>
<divclass="highlight-python"><divclass="highlight"><pre>fix 1 all nve/noforce
</pre></div>
</div>
<p>This pair style assumes that all particles will communicated to
neighboring processors every timestep as they move. This makes it
possible to perform all collisions between pairs of particles that are
on the same processor. To ensure this occurs, you should use
these commands:</p>
<divclass="highlight-python"><divclass="highlight"><pre>neighbor 0.0 bin
neigh_modify every 1 delay 0 check no
atom_modify sort 0 0.0
communicate single cutoff 0.0
</pre></div>
</div>
<p>These commands ensure that LAMMPS communicates particles to
neighboring processors every timestep and that no ghost atoms are
created. The output statistics for a simulation run should indicate
there are no ghost particles or neighbors.</p>
<p>In order to get correct DSMC collision statistics, users should
specify a Gaussian velocity distribution when populating the
simulation domain. Note that the default velocity distribution is
uniform, which will not give good DSMC collision rates. Specify
“dist gaussian” when using the <aclass="reference internal"href="velocity.html"><em>velocity</em></a> command
as in the following:</p>
<divclass="highlight-python"><divclass="highlight"><pre>velocity all create 594.6 87287 loop geom dist gaussian
<p>This pair style does not support mixing. Thus, coefficients for all
I,J pairs must be specified explicitly.</p>
<p>This pair style does not support the <aclass="reference internal"href="pair_modify.html"><em>pair_modify</em></a>
shift option for the energy of the pair interaction.</p>
<p>The <aclass="reference internal"href="pair_modify.html"><em>pair_modify</em></a> table option is not relevant
for this pair style.</p>
<p>This pair style does not support the <aclass="reference internal"href="pair_modify.html"><em>pair_modify</em></a>
tail option for adding long-range tail corrections to energy and
pressure.</p>
<p>This pair style writes its information to <aclass="reference internal"href="restart.html"><em>binary restart files</em></a>, so pair_style and pair_coeff commands do not need
to be specified in an input script that reads a restart file. Note
that the user-specified random number seed is stored in the restart
file, so when a simulation is restarted, each processor will
re-initialize its random number generator the same way it did
initially. This means the random forces will be random, but will not
be the same as they would have been if the original simulation had
continued past the restart time.</p>
<p>This pair style can only be used via the <em>pair</em> keyword of the
<aclass="reference internal"href="run_style.html"><em>run_style respa</em></a> command. It does not support the
<h2>Restrictions<aclass="headerlink"href="#restrictions"title="Permalink to this headline">¶</a></h2>
<p>This style is part of the MC package. It is only enabled if LAMMPS
was built with that package. See the <aclass="reference internal"href="Section_start.html#start-3"><span>Making LAMMPS</span></a> section for more info.</p>
</div>
<divclass="section"id="related-commands">
<h2>Related commands<aclass="headerlink"href="#related-commands"title="Permalink to this headline">¶</a></h2>
Built with <ahref="http://sphinx-doc.org/">Sphinx</a> using a <ahref="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <ahref="https://readthedocs.org">Read the Docs</a>.