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

This commit is contained in:
sjplimp 2013-11-25 16:33:24 +00:00
parent 819b351f3f
commit 42d7f88262
4 changed files with 20 additions and 20 deletions

View File

@ -25,9 +25,9 @@ clear
</P>
<P>This command deletes all atoms, restores all settings to their default
values, and frees all memory allocated by LAMMPS. Once a clear
command has been executed, it is as if LAMMPS were starting over, with
only the exceptions noted below. This command enables multiple jobs
to be run sequentially from one input script.
command has been executed, it is almost as if LAMMPS were starting
over, with only the exceptions noted below. This command enables
multiple jobs to be run sequentially from one input script.
</P>
<P>These settings are not affected by a clear command: the working
directory (<A HREF = "shell.html">shell</A> command), log file status

View File

@ -22,9 +22,9 @@ clear
This command deletes all atoms, restores all settings to their default
values, and frees all memory allocated by LAMMPS. Once a clear
command has been executed, it is as if LAMMPS were starting over, with
only the exceptions noted below. This command enables multiple jobs
to be run sequentially from one input script.
command has been executed, it is almost as if LAMMPS were starting
over, with only the exceptions noted below. This command enables
multiple jobs to be run sequentially from one input script.
These settings are not affected by a clear command: the working
directory ("shell"_shell.html command), log file status

View File

@ -145,13 +145,13 @@ this keyword has no further effect.
</P>
<HR>
<P>The <I>buffer</I> keyword applies only to dump styles <I>atom</I>, <I>custom</I>,
<I>local</I>, and <I>xyz</I>. It also applies only to text output files, not to
binary or gzipped files. If specified as <I>yes</I>, which is the default,
then each processor writes its output into an internal text buffer,
which is then sent to the processor(s) which perform file writes, and
written by those processors(s) as one large chunk of text. If
specified as <I>no</I>, each processor sends its per-atom data in binary
<P>The <I>buffer</I> keyword applies only to dump styles <I>atom</I>, <I>cfg</I>,
<I>custom</I>, <I>local</I>, and <I>xyz</I>. It also applies only to text output
files, not to binary or gzipped files. If specified as <I>yes</I>, which
is the default, then each processor writes its output into an internal
text buffer, which is then sent to the processor(s) which perform file
writes, and written by those processors(s) as one large chunk of text.
If specified as <I>no</I>, each processor sends its per-atom data in binary
format to the processor(s) which perform file wirtes, and those
processor(s) format and write it line by line into the output file.
</P>

View File

@ -133,13 +133,13 @@ this keyword has no further effect.
:line
The {buffer} keyword applies only to dump styles {atom}, {custom},
{local}, and {xyz}. It also applies only to text output files, not to
binary or gzipped files. If specified as {yes}, which is the default,
then each processor writes its output into an internal text buffer,
which is then sent to the processor(s) which perform file writes, and
written by those processors(s) as one large chunk of text. If
specified as {no}, each processor sends its per-atom data in binary
The {buffer} keyword applies only to dump styles {atom}, {cfg},
{custom}, {local}, and {xyz}. It also applies only to text output
files, not to binary or gzipped files. If specified as {yes}, which
is the default, then each processor writes its output into an internal
text buffer, which is then sent to the processor(s) which perform file
writes, and written by those processors(s) as one large chunk of text.
If specified as {no}, each processor sends its per-atom data in binary
format to the processor(s) which perform file wirtes, and those
processor(s) format and write it line by line into the output file.