jianmu
/
lammps
forked from lijiext/lammps
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

This commit is contained in:
sjplimp 2012-05-18 23:37:24 +00:00
parent f35d71d798
commit 7481744eca
2 changed files with 42 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/read_data.html
View File

@ -13,14 +13,26 @@
</H3>
<P><B>Syntax:</B>
</P>
<PRE>read_data file
<PRE>read_data file keyword args ...
</PRE>
<UL><LI>file = name of data file to read in
<LI>zero or more keyword/arg pairs may be appended
<LI>keyword = <I>fix</I>
<PRE> <I>fix</I> args = fix-ID header-string section-string
fix-ID = ID of fix to process header lines and sections of data file
header-string = header lines containing this string will be passed to fix
section-string = section names with this string will be passed to fix
</PRE>
</UL>
<P><B>Examples:</B>
</P>
<PRE>read_data data.lj
read_data ../run7/data.polymer.gz
read_data ../run7/data.polymer.gz
read_data data.protein fix mycmap crossterm CMAP
</PRE>
<P><B>Description:</B>
</P>
@ -50,6 +62,14 @@ depends on the section keyword as described below. Zero or more blank
lines can be used between sections. Sections can appear in any order,
with a few exceptions as noted below.
</P>
<P>If the keyword <I>fix</I> is used, it specifies a fix that will be used to
process portions of the data file. Any header line containing
<I>header-string</I> and any section with a name containing
<I>section-string</I> will be passed to the fix. See the <A HREF = "fix_cmap.html">fix
cmap</A> command for an example of a fix that operates in
this manner. The doc page for the fix defines the syntax of the
header line(s) and section(s) that it reads from the data file.
</P>
<P>The formatting of individual lines in the data file (indentation,
spacing between words and numbers) is not important except that header
and section keywords (e.g. atoms, xlo xhi, Masses, Bond Coeffs) must

23
doc/read_data.txt
View File

@ -10,14 +10,23 @@ read_data command :h3
[Syntax:]
read_data file :pre
read_data file keyword args ... :pre
file = name of data file to read in :ulb,l
zero or more keyword/arg pairs may be appended :l
keyword = {fix} :l
{fix} args = fix-ID header-string section-string
fix-ID = ID of fix to process header lines and sections of data file
header-string = header lines containing this string will be passed to fix
section-string = section names with this string will be passed to fix :pre
:ule
file = name of data file to read in :ul
[Examples:]
read_data data.lj
read_data ../run7/data.polymer.gz :pre
read_data ../run7/data.polymer.gz
read_data data.protein fix mycmap crossterm CMAP :pre
[Description:]
@ -47,6 +56,14 @@ depends on the section keyword as described below. Zero or more blank
lines can be used between sections. Sections can appear in any order,
with a few exceptions as noted below.
If the keyword {fix} is used, it specifies a fix that will be used to
process portions of the data file. Any header line containing
{header-string} and any section with a name containing
{section-string} will be passed to the fix. See the "fix
cmap"_fix_cmap.html command for an example of a fix that operates in
this manner. The doc page for the fix defines the syntax of the
header line(s) and section(s) that it reads from the data file.
The formatting of individual lines in the data file (indentation,
spacing between words and numbers) is not important except that header
and section keywords (e.g. atoms, xlo xhi, Masses, Bond Coeffs) must