You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
26 lines
1.2 KiB
26 lines
1.2 KiB
2 years ago
|
The Nemesis library is licensed under the terms of the BSD License.
|
||
|
|
========================================================================
|
||
|
|
|
||
|
|
NEMESIS is an enhancement to the EXODUSII finite element database
|
||
|
|
model used to store and retrieve data for unstructured parallel finite
|
||
|
|
element analyses. NEMESIS adds data structures which facilitate the
|
||
|
|
partitioning of a scalar (standard serial) EXODUSII file onto parallel
|
||
|
|
disk systems found on many parallel computers. Since the NEMESIS
|
||
|
|
application programming interface (API) can be used to append
|
||
|
|
information to an existing EXODUSII database, any existing software
|
||
|
|
that reads EXODUSII files can be used on files which contain NEMESIS
|
||
|
|
information. The NEMESIS information is written and read via C or C++
|
||
|
|
callable functions which compromise the NEMESIS I API.
|
||
|
|
|
||
|
|
NOTE:
|
||
|
|
All nemesis functionality has been moved into the exodus library API.
|
||
|
|
All (almost) nemesis API functions are available in exodus by
|
||
|
|
replacing the `ne_` at the beginning of the function name with `ex_`.
|
||
|
|
|
||
|
|
For example, the nemesis function `ne_get_init_global` is known as
|
||
|
|
`ex_get_init_global` in the exodus library API.
|
||
|
|
|
||
|
|
The nemesis library is only retained for backward compatibility; for
|
||
|
|
all new development, the exodus library should be used instead.
|
||
|
|
|