ICODE-ADC/lammps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
sjplimp
2010-09-08 23:47:51 +00:00
parent 44a309c8c4
commit 712afcc462
2 changed files with 18 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
doc/Section_errors.html
View File

@ -74,12 +74,15 @@ 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 string "abc" as an integer value and assigning the associated variable
a value of 0. a value of 0.
</P> </P>
<P>Generally, LAMMPS will print a message to the screen and exit <P>Generally, LAMMPS will print a message to the screen and logfile and
gracefully when it encounters a fatal error. Sometimes it will print exit gracefully when it encounters a fatal error. Sometimes it will
a WARNING and continue on; you can decide if the WARNING is important print a WARNING to the screen and logfile and continue on; you can
or not. If LAMMPS crashes or hangs without spitting out an error decide if the WARNING is important or not. A WARNING message that is
message first then it could be a bug (see <A HREF = "#9_2">this section</A>) or one generated in the middle of a run is only printed to the screen, not to
of the following cases: the logfile, to avoid cluttering up thermodynamic output. If LAMMPS
crashes or hangs without spitting out an error message first then it
could be a bug (see <A HREF = "#9_2">this section</A>) or one of the following
cases:
</P> </P>
<P>LAMMPS runs in the available memory a processor allows to be <P>LAMMPS runs in the available memory a processor allows to be
allocated. Most reasonable MD runs are compute limited, not memory allocated. Most reasonable MD runs are compute limited, not memory

15
doc/Section_errors.txt
View File

@ -71,12 +71,15 @@ 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 string "abc" as an integer value and assigning the associated variable
a value of 0. a value of 0.
Generally, LAMMPS will print a message to the screen and exit Generally, LAMMPS will print a message to the screen and logfile and
gracefully when it encounters a fatal error. Sometimes it will print exit gracefully when it encounters a fatal error. Sometimes it will
a WARNING and continue on; you can decide if the WARNING is important print a WARNING to the screen and logfile and continue on; you can
or not. If LAMMPS crashes or hangs without spitting out an error decide if the WARNING is important or not. A WARNING message that is
message first then it could be a bug (see "this section"_#9_2) or one generated in the middle of a run is only printed to the screen, not to
of the following cases: the logfile, to avoid cluttering up thermodynamic output. If LAMMPS
crashes or hangs without spitting out an error message first then it
could be a bug (see "this section"_#9_2) or one of the following
cases:
LAMMPS runs in the available memory a processor allows to be LAMMPS runs in the available memory a processor allows to be
allocated. Most reasonable MD runs are compute limited, not memory allocated. Most reasonable MD runs are compute limited, not memory