forked from lijiext/lammps
git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@12016 f3b2605a-c512-4ea7-a41b-209d697bcdaa
This commit is contained in:
sjplimp
parent
051dfb0706
commit
d45d192091
|
|
@ -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
|
||||
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>
|
||||
to see it on the screen. 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 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 and assigning the associated variable
|
||||
a value of 0.
|
||||
to see it on the screen. If you get an error like "Invalid ...
|
||||
style", with ... being fix, compute, pair, etc, it means that you
|
||||
mistyped the style name or that the command is part of an optional
|
||||
package which was not compiled into your executable. The list of
|
||||
available styles in your executable can be listed by using <A HREF = "Section_start.html#start_7">the -h
|
||||
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>Generally, LAMMPS will print a message to the screen and logfile and
|
||||
exit gracefully when it encounters a fatal error. Sometimes it will
|
||||
|
|
|
|||
|
|
@ -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
|
||||
script, you can determine what command is causing the problem by
|
||||
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
|
||||
arguments in a specified order. If you mess this up, LAMMPS will
|
||||
often flag the error, but it may 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 and assigning the associated variable
|
||||
a value of 0.
|
||||
to see it on the screen. If you get an error like "Invalid ...
|
||||
style", with ... being fix, compute, pair, etc, it means that you
|
||||
mistyped the style name or that the command is part of an optional
|
||||
package which was not compiled into your executable. The list of
|
||||
available styles in your executable can be listed by using "the -h
|
||||
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
|
||||
exit gracefully when it encounters a fatal error. Sometimes it will
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ sub-directories:
|
|||
</TD></TR></TABLE></DIV>
|
||||
|
||||
<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>
|
||||
<PRE>lmp_windows.exe
|
||||
</PRE>
|
||||
|
|
@ -518,18 +518,29 @@ src/MAKE/Makefile.mac file.
|
|||
<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
|
||||
parallel pre-built Windows exeutable. See the <A HREF = "#start_6">Running
|
||||
LAMMPS</A> section for instructions for running these
|
||||
executables on a Windows box.
|
||||
parallel pre-built Windows executable. See the <A HREF = "#start_6">Running
|
||||
LAMMPS</A> section for instructions on running these executables
|
||||
on a Windows box.
|
||||
</P>
|
||||
<P>The pre-built executables are built with a subset of the available
|
||||
pacakges; see the download page for the list. If you want
|
||||
a Windows version with specific packages included and excluded,
|
||||
you can build it yourself.
|
||||
<P>The pre-built executables hosted on the <A HREF = "http://lammps.sandia.gov/download.html">LAMMPS download
|
||||
page</A> are built with a subset
|
||||
of the available packages; see the download page for the list. These
|
||||
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>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
|
||||
src/MAKE/Makefile.cygwin.
|
||||
standard unix style make program, just as you would on a Linux box;
|
||||
see src/MAKE/Makefile.cygwin.
|
||||
</P>
|
||||
<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
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ src: source files
|
|||
tools: pre- and post-processing tools :tb(s=:)
|
||||
|
||||
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
|
||||
|
||||
|
|
@ -512,18 +512,29 @@ src/MAKE/Makefile.mac file.
|
|||
[{Building for Windows:}] :link(start_2_6)
|
||||
|
||||
The LAMMPS download page has an option to download both a serial and
|
||||
parallel pre-built Windows exeutable. See the "Running
|
||||
LAMMPS"_#start_6 section for instructions for running these
|
||||
executables on a Windows box.
|
||||
parallel pre-built Windows executable. See the "Running
|
||||
LAMMPS"_#start_6 section for instructions on running these executables
|
||||
on a Windows box.
|
||||
|
||||
The pre-built executables are built with a subset of the available
|
||||
pacakges; see the download page for the list. If you want
|
||||
a Windows version with specific packages included and excluded,
|
||||
you can build it yourself.
|
||||
The pre-built executables hosted on the "LAMMPS download
|
||||
page"_http://lammps.sandia.gov/download.html are built with a subset
|
||||
of the available packages; see the download page for the list. These
|
||||
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
|
||||
standard Linus make, just as you would on any Linux box; see
|
||||
src/MAKE/Makefile.cygwin.
|
||||
standard unix style make program, just as you would on a Linux box;
|
||||
see src/MAKE/Makefile.cygwin.
|
||||
|
||||
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
|
||||
|
|
|
|||
Loading…
Reference in New Issue