git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@3683 f3b2605a-c512-4ea7-a41b-209d697bcdaa

This commit is contained in:
sjplimp
2010-01-14 19:44:28 +00:00
parent 9cecf81520
commit 522ea749e2
4 changed files with 16 additions and 14 deletions

View File

@ -61,12 +61,13 @@ commands are two examples of commands that require this setting to
work efficiently. Several <A HREF = "fix.html">fixes</A>, most notably time work efficiently. Several <A HREF = "fix.html">fixes</A>, most notably time
integration fixes like <A HREF = "fix_nve.html">fix nve</A>, also take advantage of integration fixes like <A HREF = "fix_nve.html">fix nve</A>, also take advantage of
this setting if the group they operate on is the group specified by this setting if the group they operate on is the group specified by
this command. this command. Note that specifying "all" as the group-ID effectively
turns off the <I>first</I> option.
</P> </P>
<P>It is OK to use the <I>first</I> keyword with a group that has not yet been <P>It is OK to use the <I>first</I> keyword with a group that has not yet been
defined, e.g. to use the atom_modify command at the beginning of your defined, e.g. to use the atom_modify first command at the beginning of
input script. LAMMPS will check that the group exists before the your input script. LAMMPS does not use the group until a simullation
first simulation is performed. is run.
</P> </P>
<P>The <I>sort</I> keyword turns on a spatial sorting or reordering of atoms <P>The <I>sort</I> keyword turns on a spatial sorting or reordering of atoms
within each processor's sub-domain every <I>Nfreq</I> timesteps. This can within each processor's sub-domain every <I>Nfreq</I> timesteps. This can
@ -113,7 +114,7 @@ command.
</P> </P>
<P>The <I>first</I> and <I>sort</I> options cannot be used together. Since sorting <P>The <I>first</I> and <I>sort</I> options cannot be used together. Since sorting
is on by default, it will be turned off if the <I>first</I> keyword is is on by default, it will be turned off if the <I>first</I> keyword is
used. used with a group-ID that is not "all".
</P> </P>
<P><B>Related commands:</B> none <P><B>Related commands:</B> none
</P> </P>

View File

@ -55,12 +55,13 @@ commands are two examples of commands that require this setting to
work efficiently. Several "fixes"_fix.html, most notably time work efficiently. Several "fixes"_fix.html, most notably time
integration fixes like "fix nve"_fix_nve.html, also take advantage of integration fixes like "fix nve"_fix_nve.html, also take advantage of
this setting if the group they operate on is the group specified by this setting if the group they operate on is the group specified by
this command. this command. Note that specifying "all" as the group-ID effectively
turns off the {first} option.
It is OK to use the {first} keyword with a group that has not yet been It is OK to use the {first} keyword with a group that has not yet been
defined, e.g. to use the atom_modify command at the beginning of your defined, e.g. to use the atom_modify first command at the beginning of
input script. LAMMPS will check that the group exists before the your input script. LAMMPS does not use the group until a simullation
first simulation is performed. is run.
The {sort} keyword turns on a spatial sorting or reordering of atoms The {sort} keyword turns on a spatial sorting or reordering of atoms
within each processor's sub-domain every {Nfreq} timesteps. This can within each processor's sub-domain every {Nfreq} timesteps. This can
@ -107,7 +108,7 @@ command.
The {first} and {sort} options cannot be used together. Since sorting The {first} and {sort} options cannot be used together. Since sorting
is on by default, it will be turned off if the {first} keyword is is on by default, it will be turned off if the {first} keyword is
used. used with a group-ID that is not "all".
[Related commands:] none [Related commands:] none

View File

@ -31,8 +31,8 @@
</P> </P>
<PRE>communicate multi <PRE>communicate multi
communicate multi group solvent communicate multi group solvent
communicate single ghost yes communicate single vel yes
communicate single cutoff 5.0 ghost yes communicate single cutoff 5.0 vel yes
</PRE> </PRE>
<P><B>Description:</B> <P><B>Description:</B>
</P> </P>

View File

@ -24,8 +24,8 @@ keyword = {cutoff} or {group} or {vel} :l
communicate multi communicate multi
communicate multi group solvent communicate multi group solvent
communicate single ghost yes communicate single vel yes
communicate single cutoff 5.0 ghost yes :pre communicate single cutoff 5.0 vel yes :pre
[Description:] [Description:]