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@12016 f3b2605a-c512-4ea7-a41b-209d697bcdaa

This commit is contained in:
sjplimp 2014-05-22 14:20:18 +00:00
parent 051dfb0706
commit d45d192091
4 changed files with 82 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
doc/Section_errors.html
View File

@ -69,12 +69,26 @@ that you think it should flag, please send an email to the
<P>If you get an error message about an invalid command in your input <P>If you get an error message about an invalid command in your input
script, you can determine what command is causing the problem by script, you can determine what command is causing the problem by
looking in the log.lammps file or using the <A HREF = "echo.html">echo command</A> looking in the log.lammps file or using the <A HREF = "echo.html">echo command</A>
to see it on the screen. For a given command, LAMMPS expects certain to see it on the screen. If you get an error like "Invalid ...
arguments in a specified order. If you mess this up, LAMMPS will style", with ... being fix, compute, pair, etc, it means that you
often flag the error, but it may read a bogus argument and assign a mistyped the style name or that the command is part of an optional
value that is valid, but not what you wanted. E.g. trying to read the package which was not compiled into your executable. The list of
string "abc" as an integer value and assigning the associated variable available styles in your executable can be listed by using <A HREF = "Section_start.html#start_7">the -h
a value of 0. command-line argument</A>. The installation
and compilation of optional packages is explained in the <A HREF = "Section_start.html#start_3">installation
instructions</A>.
</P>
<P>For a given command, LAMMPS expects certain arguments in a specified
order. If you mess this up, LAMMPS will often flag the error, but it
may also simply read a bogus argument and assign a value that is
valid, but not what you wanted. E.g. trying to read the string "abc"
as an integer value of 0. Careful reading of the associated doc page
for the command should allow you to fix these problems. Note that
some commands allow for variables to be specified in place of numeric
constants so that the value can be evaluated and change over the
course of a run. This is typically done with the syntax <I>v_name</I> for
a parameter, where name is the name of the variable. This is only
allowed if the command documentation says it is.
</P> </P>
<P>Generally, LAMMPS will print a message to the screen and logfile and <P>Generally, LAMMPS will print a message to the screen and logfile and
exit gracefully when it encounters a fatal error. Sometimes it will exit gracefully when it encounters a fatal error. Sometimes it will

26
doc/Section_errors.txt
View File

@ -65,12 +65,26 @@ that you think it should flag, please send an email to the
If you get an error message about an invalid command in your input If you get an error message about an invalid command in your input
script, you can determine what command is causing the problem by script, you can determine what command is causing the problem by
looking in the log.lammps file or using the "echo command"_echo.html looking in the log.lammps file or using the "echo command"_echo.html
to see it on the screen. For a given command, LAMMPS expects certain to see it on the screen. If you get an error like "Invalid ...
arguments in a specified order. If you mess this up, LAMMPS will style", with ... being fix, compute, pair, etc, it means that you
often flag the error, but it may read a bogus argument and assign a mistyped the style name or that the command is part of an optional
value that is valid, but not what you wanted. E.g. trying to read the package which was not compiled into your executable. The list of
string "abc" as an integer value and assigning the associated variable available styles in your executable can be listed by using "the -h
a value of 0. command-line argument"_Section_start.html#start_7. The installation
and compilation of optional packages is explained in the "installation
instructions"_Section_start.html#start_3.
For a given command, LAMMPS expects certain arguments in a specified
order. If you mess this up, LAMMPS will often flag the error, but it
may also simply read a bogus argument and assign a value that is
valid, but not what you wanted. E.g. trying to read the string "abc"
as an integer value of 0. Careful reading of the associated doc page
for the command should allow you to fix these problems. Note that
some commands allow for variables to be specified in place of numeric
constants so that the value can be evaluated and change over the
course of a run. This is typically done with the syntax {v_name} for
a parameter, where name is the name of the variable. This is only
allowed if the command documentation says it is.
Generally, LAMMPS will print a message to the screen and logfile and Generally, LAMMPS will print a message to the screen and logfile and
exit gracefully when it encounters a fatal error. Sometimes it will exit gracefully when it encounters a fatal error. Sometimes it will

31
doc/Section_start.html
View File

@ -52,7 +52,7 @@ sub-directories:
</TD></TR></TABLE></DIV> </TD></TR></TABLE></DIV>
<P>If you download one of the Windows executables from the download page, <P>If you download one of the Windows executables from the download page,
then you just get a single file: then you get a single file:
</P> </P>
<PRE>lmp_windows.exe <PRE>lmp_windows.exe
</PRE> </PRE>
@ -518,18 +518,29 @@ src/MAKE/Makefile.mac file.
<A NAME = "start_2_6"></A><B><I>Building for Windows:</I></B> <A NAME = "start_2_6"></A><B><I>Building for Windows:</I></B>
<P>The LAMMPS download page has an option to download both a serial and <P>The LAMMPS download page has an option to download both a serial and
parallel pre-built Windows exeutable. See the <A HREF = "#start_6">Running parallel pre-built Windows executable. See the <A HREF = "#start_6">Running
LAMMPS</A> section for instructions for running these LAMMPS</A> section for instructions on running these executables
executables on a Windows box. on a Windows box.
</P> </P>
<P>The pre-built executables are built with a subset of the available <P>The pre-built executables hosted on the <A HREF = "http://lammps.sandia.gov/download.html">LAMMPS download
pacakges; see the download page for the list. If you want page</A> are built with a subset
a Windows version with specific packages included and excluded, of the available packages; see the download page for the list. These
you can build it yourself. are single executable files. No examples or documentation in
included. You will need to download the full source code package to
obtain those.
</P>
<P>As an alternative, you can download "daily builds" (and some older
versions) of the installer packages from
<A HREF = "http://rpm.lammps.org/windows.html">rpm.lammps.org/windows.html</A>.
These executables are built with most optional packages and the
download includes documentation, some tools and most examples.
</P>
<P>If you want a Windows version with specific packages included and
excluded, you can build it yourself.
</P> </P>
<P>One way to do this is install and use cygwin to build LAMMPS with a <P>One way to do this is install and use cygwin to build LAMMPS with a
standard Linus make, just as you would on any Linux box; see standard unix style make program, just as you would on a Linux box;
src/MAKE/Makefile.cygwin. see src/MAKE/Makefile.cygwin.
</P> </P>
<P>The other way to do this is using Visual Studio and project files. <P>The other way to do this is using Visual Studio and project files.
See the src/WINDOWS directory and its README.txt file for instructions See the src/WINDOWS directory and its README.txt file for instructions

31
doc/Section_start.txt
View File

@ -46,7 +46,7 @@ src: source files
tools: pre- and post-processing tools :tb(s=:) tools: pre- and post-processing tools :tb(s=:)
If you download one of the Windows executables from the download page, If you download one of the Windows executables from the download page,
then you just get a single file: then you get a single file:
lmp_windows.exe :pre lmp_windows.exe :pre
@ -512,18 +512,29 @@ src/MAKE/Makefile.mac file.
[{Building for Windows:}] :link(start_2_6) [{Building for Windows:}] :link(start_2_6)
The LAMMPS download page has an option to download both a serial and The LAMMPS download page has an option to download both a serial and
parallel pre-built Windows exeutable. See the "Running parallel pre-built Windows executable. See the "Running
LAMMPS"_#start_6 section for instructions for running these LAMMPS"_#start_6 section for instructions on running these executables
executables on a Windows box. on a Windows box.
The pre-built executables are built with a subset of the available The pre-built executables hosted on the "LAMMPS download
pacakges; see the download page for the list. If you want page"_http://lammps.sandia.gov/download.html are built with a subset
a Windows version with specific packages included and excluded, of the available packages; see the download page for the list. These
you can build it yourself. are single executable files. No examples or documentation in
included. You will need to download the full source code package to
obtain those.
As an alternative, you can download "daily builds" (and some older
versions) of the installer packages from
"rpm.lammps.org/windows.html"_http://rpm.lammps.org/windows.html.
These executables are built with most optional packages and the
download includes documentation, some tools and most examples.
If you want a Windows version with specific packages included and
excluded, you can build it yourself.
One way to do this is install and use cygwin to build LAMMPS with a One way to do this is install and use cygwin to build LAMMPS with a
standard Linus make, just as you would on any Linux box; see standard unix style make program, just as you would on a Linux box;
src/MAKE/Makefile.cygwin. see src/MAKE/Makefile.cygwin.
The other way to do this is using Visual Studio and project files. The other way to do this is using Visual Studio and project files.
See the src/WINDOWS directory and its README.txt file for instructions See the src/WINDOWS directory and its README.txt file for instructions