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

small changes to doc page

This commit is contained in:
Steve Plimpton 2016-08-31 16:16:43 -06:00
parent 639ab0fd3e
commit de21cb2cd5
2 changed files with 11 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/html/Section_start.html
View File

@ -459,12 +459,11 @@ MPI version does not recognize “long long” data types. In this case
“long” data type is likely already 64-bits, in which case this setting
will convert to that data type.</p>
<p>The -DLAMMPS_EXCEPTIONS setting can be used to activate alternative
versions of error handling inside of LAMMPS. This is useful for
external codes driving LAMMPS as a library. With this option, a
LAMMPS error does not exit the driving process. Instead, the call
stack is unwound and LAMMPS can return to the caller. The library
interface provides the lammps_has_error() and
lammps_get_last_error_message() functions which the caller can use to
versions of error handling inside of LAMMPS. This is useful when
external codes drive LAMMPS as a library. Using this option, LAMMPS
errors do not kill the caller. Instead, the call stack is unwound and
control returns to the caller. The library interface provides the
lammps_has_error() and lammps_get_last_error_message() functions to
detect and find out more about a LAMMPS error.</p>
<p>Using one of the -DPACK_ARRAY, -DPACK_POINTER, and -DPACK_MEMCPY
options can make for faster parallel FFTs (in the PPPM solver) on some

12
doc/src/Section_start.txt
View File

@ -336,12 +336,12 @@ MPI version does not recognize "long long" data types. In this case a
will convert to that data type.
The -DLAMMPS_EXCEPTIONS setting can be used to activate alternative
versions of error handling inside of LAMMPS. This is useful for external
codes driving LAMMPS as a library. Using this option, errors do not exit
the driving process. Instead, the call stack is unwinded and the library
functions can return. The library interface provides the lammps_has_error
and lammps_get_last_error_message functions to detect and find out more
about an LAMMPS error.
versions of error handling inside of LAMMPS. This is useful when
external codes drive LAMMPS as a library. Using this option, LAMMPS
errors do not kill the caller. Instead, the call stack is unwound and
control returns to the caller. The library interface provides the
lammps_has_error() and lammps_get_last_error_message() functions to
detect and find out more about a LAMMPS error.
Using one of the -DPACK_ARRAY, -DPACK_POINTER, and -DPACK_MEMCPY
options can make for faster parallel FFTs (in the PPPM solver) on some