From 42d7f882625756d33df55bbdeabb0cc6113901c6 Mon Sep 17 00:00:00 2001 From: sjplimp Date: Mon, 25 Nov 2013 16:33:24 +0000 Subject: [PATCH] git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@11058 f3b2605a-c512-4ea7-a41b-209d697bcdaa --- doc/clear.html | 6 +++--- doc/clear.txt | 6 +++--- doc/dump_modify.html | 14 +++++++------- doc/dump_modify.txt | 14 +++++++------- 4 files changed, 20 insertions(+), 20 deletions(-) diff --git a/doc/clear.html b/doc/clear.html index 43e58c3e2b..ddb7f19a13 100644 --- a/doc/clear.html +++ b/doc/clear.html @@ -25,9 +25,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 command), log file status diff --git a/doc/clear.txt b/doc/clear.txt index 0bb18454bc..7ac4da5c8d 100644 --- a/doc/clear.txt +++ b/doc/clear.txt @@ -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 diff --git a/doc/dump_modify.html b/doc/dump_modify.html index db3b102a5a..ce27761188 100644 --- a/doc/dump_modify.html +++ b/doc/dump_modify.html @@ -145,13 +145,13 @@ this keyword has no further effect.

-

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.

diff --git a/doc/dump_modify.txt b/doc/dump_modify.txt index 0501874c1a..dfb3073aa4 100644 --- a/doc/dump_modify.txt +++ b/doc/dump_modify.txt @@ -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.