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 -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. The installation +and compilation of optional packages is explained in the installation +instructions. +
+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 diff --git a/doc/Section_errors.txt b/doc/Section_errors.txt index a516028fe3..1b6c7adb1a 100644 --- a/doc/Section_errors.txt +++ b/doc/Section_errors.txt @@ -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 diff --git a/doc/Section_start.html b/doc/Section_start.html index 270f7985a0..f8c34710b0 100644 --- a/doc/Section_start.html +++ b/doc/Section_start.html @@ -52,7 +52,7 @@ sub-directories:
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@@ -518,18 +518,29 @@ src/MAKE/Makefile.mac file. Building for Windows:
The LAMMPS download page has an option to download both a serial and -parallel pre-built Windows exeutable. See the Running -LAMMPS section for instructions for running these -executables on a Windows box. +parallel pre-built Windows executable. See the Running +LAMMPS 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 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. +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 diff --git a/doc/Section_start.txt b/doc/Section_start.txt index 9ab2f215f9..e013aea6f3 100644 --- a/doc/Section_start.txt +++ b/doc/Section_start.txt @@ -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