From 522ea749e2e33b723fcc5aebb42aa66c9781f42c Mon Sep 17 00:00:00 2001 From: sjplimp Date: Thu, 14 Jan 2010 19:44:28 +0000 Subject: [PATCH] git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@3683 f3b2605a-c512-4ea7-a41b-209d697bcdaa --- doc/atom_modify.html | 11 ++++++----- doc/atom_modify.txt | 11 ++++++----- doc/communicate.html | 4 ++-- doc/communicate.txt | 4 ++-- 4 files changed, 16 insertions(+), 14 deletions(-) diff --git a/doc/atom_modify.html b/doc/atom_modify.html index de192c7067..a4cad5b9f1 100644 --- a/doc/atom_modify.html +++ b/doc/atom_modify.html @@ -61,12 +61,13 @@ commands are two examples of commands that require this setting to work efficiently. Several fixes, most notably time integration fixes like fix nve, also take advantage of 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 -defined, e.g. to use the atom_modify command at the beginning of your -input script. LAMMPS will check that the group exists before the -first simulation is performed. +defined, e.g. to use the atom_modify first command at the beginning of +your input script. LAMMPS does not use the group until a simullation +is run.

The sort keyword turns on a spatial sorting or reordering of atoms within each processor's sub-domain every Nfreq timesteps. This can @@ -113,7 +114,7 @@ command.

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 -used. +used with a group-ID that is not "all".

Related commands: none

diff --git a/doc/atom_modify.txt b/doc/atom_modify.txt index 2a2b3bf15e..e7a0afd8ca 100644 --- a/doc/atom_modify.txt +++ b/doc/atom_modify.txt @@ -55,12 +55,13 @@ commands are two examples of commands that require this setting to work efficiently. Several "fixes"_fix.html, most notably time 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 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 -defined, e.g. to use the atom_modify command at the beginning of your -input script. LAMMPS will check that the group exists before the -first simulation is performed. +defined, e.g. to use the atom_modify first command at the beginning of +your input script. LAMMPS does not use the group until a simullation +is run. The {sort} keyword turns on a spatial sorting or reordering of atoms 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 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 diff --git a/doc/communicate.html b/doc/communicate.html index 3d691b24f5..8eeb707ebf 100644 --- a/doc/communicate.html +++ b/doc/communicate.html @@ -31,8 +31,8 @@ 

communicate multi
 communicate multi group solvent
-communicate single ghost yes
-communicate single cutoff 5.0 ghost yes 
+communicate single vel yes
+communicate single cutoff 5.0 vel yes

Description:

diff --git a/doc/communicate.txt b/doc/communicate.txt index 51169fe99d..b24ff976f3 100644 --- a/doc/communicate.txt +++ b/doc/communicate.txt @@ -24,8 +24,8 @@ keyword = {cutoff} or {group} or {vel} :l communicate multi communicate multi group solvent -communicate single ghost yes -communicate single cutoff 5.0 ghost yes :pre +communicate single vel yes +communicate single cutoff 5.0 vel yes :pre [Description:]