| 1 |
======================================================================== |
| 2 |
CONTACT: |
| 3 |
|
| 4 |
Greg Sjaardema, |
| 5 |
Sandia National Laboratories, |
| 6 |
[email protected] |
| 7 |
|
| 8 |
======================================================================== |
| 9 |
LICENSE: |
| 10 |
The Exodus library is licensed under the terms of the BSD License. |
| 11 |
|
| 12 |
Legal stuff (copyright, licensing restrictions, etc.) can be found in |
| 13 |
the file COPYRIGHT which contains: |
| 14 |
|
| 15 |
1. The Sandia Corporation Copyright Notice. |
| 16 |
2. The BSD License. |
| 17 |
|
| 18 |
We appreciate feedback from users of this package. Please send |
| 19 |
comments, suggestions, and bug reports to Greg Sjaardema |
| 20 |
<[email protected]>. |
| 21 |
|
| 22 |
Please identify the version of the package. |
| 23 |
|
| 24 |
======================================================================== |
| 25 |
BUILDING |
| 26 |
|
| 27 |
There are 4 methods for building exodus. |
| 28 |
|
| 29 |
1. SEAMS/SEACAS Build system which is based on imake. If you have a |
| 30 |
SEAMS or SEACAS installation, you can use its build system. In the |
| 31 |
top-level exodus directory, do 'accmkmf' followed by 'make |
| 32 |
Makefiles' and then 'make' |
| 33 |
|
| 34 |
2. CMAKE: type 'cmake .' or 'cmake -i' to generate the Makefiles |
| 35 |
followed by 'make'. There is a cmake-script file which shows how I configure |
| 36 |
cmake. |
| 37 |
|
| 38 |
3. Makefile.standalone. Edit the top-level Makefile.standalone file |
| 39 |
and specify the compiler and other options as detailed in the |
| 40 |
file. Then, do "make -f Makefile.standalone". |
| 41 |
|
| 42 |
4. Building in the Trilinos system as part of the seacas package. |
| 43 |
See the Trilinos documentation for more details. |
| 44 |
|
| 45 |
Once you have built the library, you can test it by typing "make |
| 46 |
check" |
| 47 |
|
| 48 |
|
| 49 |
======================================================================== |
| 50 |
NETCDF |
| 51 |
|
| 52 |
The exodus library uses the netcdf library for low-level data |
| 53 |
storage. |
| 54 |
|
| 55 |
Exodus requires NetCDF version 4.2.1.1 or later. |
| 56 |
|
| 57 |
The netcdf library must be modified slightly in order to handle the |
| 58 |
exodus datamodel. The specific changes are: |
| 59 |
|
| 60 |
1. include/netcdf.h -- Modify the following defines: |
| 61 |
|
| 62 |
#define NC_MAX_DIMS 65536 /* max dimensions per file */ |
| 63 |
#define NC_MAX_VARS 524288 /* max variables per file */ |
| 64 |
#define NC_MAX_VAR_DIMS 8 /* max per variable dimensions */ |
| 65 |
|
| 66 |
If these changes are not made, the exodus library will still function |
| 67 |
for "normal" size models, but it will fail for "large" models. The |
| 68 |
error message from exodus/netcdf should be somewhat clear when this |
| 69 |
happens... |
| 70 |
|
| 71 |
2. I typically configure netcdf as follows: |
| 72 |
|
| 73 |
./configure --enable-netcdf-4 --disable-fsync --disable-dap --disable-cdmremote |
| 74 |
|
| 75 |
Replace "--enable-netcdf-4" with "--disable-netcdf-4" to not use the |
| 76 |
netcdf4 extensions. They are not necessarily needed for exodus, but |
| 77 |
will provide compression, larger model sizes, and may be faster in |
| 78 |
some cases. |
| 79 |
|
| 80 |
3. When running the netcdf tests, you may have to do "unlimit |
| 81 |
stacksize" (csh/tcsh) to avoid some failures due to the increased define sizes |
| 82 |
above. |
| 83 |
|
| 84 |
======================================================================== |