mirror of https://github.com/lammps/lammps.git
git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@6268 f3b2605a-c512-4ea7-a41b-209d697bcdaa
This commit is contained in:
parent
201628e11b
commit
bc08589f97
|
@ -36,7 +36,7 @@ section of the manual</A>. The "opt" style
|
||||||
corrsponds to the OPT package, the "gpu" style to the GPU package, and
|
corrsponds to the OPT package, the "gpu" style to the GPU package, and
|
||||||
the "cuda" style to the USER-CUDA package.
|
the "cuda" style to the USER-CUDA package.
|
||||||
</P>
|
</P>
|
||||||
<P>These are the relevant packages and the variants they provide:
|
<P>These are the variants these packages provide:
|
||||||
</P>
|
</P>
|
||||||
<UL><LI>OPT = a handful of pair styles, cache-optimized for faster CPU performance
|
<UL><LI>OPT = a handful of pair styles, cache-optimized for faster CPU performance
|
||||||
<LI>GPU = a handful of pair styles and the PPPM kspace_style, optimized to run on one or more GPUs or multicore CPU/GPU nodes
|
<LI>GPU = a handful of pair styles and the PPPM kspace_style, optimized to run on one or more GPUs or multicore CPU/GPU nodes
|
||||||
|
@ -44,24 +44,24 @@ the "cuda" style to the USER-CUDA package.
|
||||||
</UL>
|
</UL>
|
||||||
<P>As an example, all of the packages provide a <A HREF = "pair_lj.html">pair_style
|
<P>As an example, all of the packages provide a <A HREF = "pair_lj.html">pair_style
|
||||||
lj/cut</A> variant, with style names lj/cut/opt or
|
lj/cut</A> variant, with style names lj/cut/opt or
|
||||||
lj/cut/gpu or lj/cut/cuda. Any variant styles can be specified
|
lj/cut/gpu or lj/cut/cuda. A variant styles can be specified
|
||||||
explicitly in your input script, e.g. pair_style lj/cut/gpu. If the
|
explicitly in your input script, e.g. pair_style lj/cut/gpu. If the
|
||||||
suffix command is used with the appropriate style, you do not need to
|
suffix command is used with the appropriate style, you do not need to
|
||||||
modify your input script. The specified suffix (opt,gpu,cuda) is
|
modify your input script. The specified suffix (opt,gpu,cuda) is
|
||||||
automatically appended whenever an input script command creates a new
|
automatically appended whenever your input script command creates a
|
||||||
<A HREF = "atom_style.html">atom</A>, <A HREF = "pair_style.html">pair</A>, <A HREF = "fix.html">fix</A>,
|
new <A HREF = "atom_style.html">atom</A>, <A HREF = "pair_style.html">pair</A>, <A HREF = "fix.html">fix</A>,
|
||||||
<A HREF = "compute.html">compute</A>, or <A HREF = "run_style.html">integrate</A> style. If the
|
<A HREF = "compute.html">compute</A>, or <A HREF = "run_style.html">integrate</A> style. If the
|
||||||
variant version does not exist, the standard version is created.
|
variant version does not exist, the standard version is created.
|
||||||
</P>
|
</P>
|
||||||
<P>If the specified style is <I>off</I>, then any previously specified suffix
|
<P>If the specified style is <I>off</I>, then any previously specified suffix
|
||||||
is temporarily disabled, whether it was specified by a command-line
|
is temporarily disabled, whether it was specified by a command-line
|
||||||
switch or a previous suffix command. If the specified style is <I>on</I>,
|
switch or a previous suffix command. If the specified style is <I>on</I>,
|
||||||
a previously specified suffix is turned back on. The use of these 2
|
a disabled suffix is turned back on. The use of these 2 commands lets
|
||||||
commands lets your input script use a standard LAMMPS style (i.e. a
|
your input script use a standard LAMMPS style (i.e. a non-accelerated
|
||||||
non-accelerated variant), which can be useful for testing or
|
variant), which can be useful for testing or benchmarking purposes.
|
||||||
benchmarking purposes. Of course this is also possible by not using
|
Of course this is also possible by not using any suffix commands, and
|
||||||
the suffix command, and explictly appending or non appending the
|
explictly appending or not appending the suffix to the relevant
|
||||||
suffix to the relevant commands in your input script.
|
commands in your input script.
|
||||||
</P>
|
</P>
|
||||||
<P><B>Restrictions:</B> none
|
<P><B>Restrictions:</B> none
|
||||||
</P>
|
</P>
|
||||||
|
|
|
@ -33,7 +33,7 @@ section of the manual"_Section_start.html#2_3. The "opt" style
|
||||||
corrsponds to the OPT package, the "gpu" style to the GPU package, and
|
corrsponds to the OPT package, the "gpu" style to the GPU package, and
|
||||||
the "cuda" style to the USER-CUDA package.
|
the "cuda" style to the USER-CUDA package.
|
||||||
|
|
||||||
These are the relevant packages and the variants they provide:
|
These are the variants these packages provide:
|
||||||
|
|
||||||
OPT = a handful of pair styles, cache-optimized for faster CPU performance
|
OPT = a handful of pair styles, cache-optimized for faster CPU performance
|
||||||
GPU = a handful of pair styles and the PPPM kspace_style, optimized to run on one or more GPUs or multicore CPU/GPU nodes
|
GPU = a handful of pair styles and the PPPM kspace_style, optimized to run on one or more GPUs or multicore CPU/GPU nodes
|
||||||
|
@ -41,24 +41,24 @@ USER-CUDA = a collection of atom, pair, fix, compute, and intergrate styles, opt
|
||||||
|
|
||||||
As an example, all of the packages provide a "pair_style
|
As an example, all of the packages provide a "pair_style
|
||||||
lj/cut"_pair_lj.html variant, with style names lj/cut/opt or
|
lj/cut"_pair_lj.html variant, with style names lj/cut/opt or
|
||||||
lj/cut/gpu or lj/cut/cuda. Any variant styles can be specified
|
lj/cut/gpu or lj/cut/cuda. A variant styles can be specified
|
||||||
explicitly in your input script, e.g. pair_style lj/cut/gpu. If the
|
explicitly in your input script, e.g. pair_style lj/cut/gpu. If the
|
||||||
suffix command is used with the appropriate style, you do not need to
|
suffix command is used with the appropriate style, you do not need to
|
||||||
modify your input script. The specified suffix (opt,gpu,cuda) is
|
modify your input script. The specified suffix (opt,gpu,cuda) is
|
||||||
automatically appended whenever an input script command creates a new
|
automatically appended whenever your input script command creates a
|
||||||
"atom"_atom_style.html, "pair"_pair_style.html, "fix"_fix.html,
|
new "atom"_atom_style.html, "pair"_pair_style.html, "fix"_fix.html,
|
||||||
"compute"_compute.html, or "integrate"_run_style.html style. If the
|
"compute"_compute.html, or "integrate"_run_style.html style. If the
|
||||||
variant version does not exist, the standard version is created.
|
variant version does not exist, the standard version is created.
|
||||||
|
|
||||||
If the specified style is {off}, then any previously specified suffix
|
If the specified style is {off}, then any previously specified suffix
|
||||||
is temporarily disabled, whether it was specified by a command-line
|
is temporarily disabled, whether it was specified by a command-line
|
||||||
switch or a previous suffix command. If the specified style is {on},
|
switch or a previous suffix command. If the specified style is {on},
|
||||||
a previously specified suffix is turned back on. The use of these 2
|
a disabled suffix is turned back on. The use of these 2 commands lets
|
||||||
commands lets your input script use a standard LAMMPS style (i.e. a
|
your input script use a standard LAMMPS style (i.e. a non-accelerated
|
||||||
non-accelerated variant), which can be useful for testing or
|
variant), which can be useful for testing or benchmarking purposes.
|
||||||
benchmarking purposes. Of course this is also possible by not using
|
Of course this is also possible by not using any suffix commands, and
|
||||||
the suffix command, and explictly appending or non appending the
|
explictly appending or not appending the suffix to the relevant
|
||||||
suffix to the relevant commands in your input script.
|
commands in your input script.
|
||||||
|
|
||||||
[Restrictions:] none
|
[Restrictions:] none
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue