SEACAS [Documentation] [Wiki]

• Get the sources
• Build instructions
• Configure, Build, and Install SEACAS
• Parallel Build
• Testing
• Exodus
• Trilinos
• SPACK
• Docker
• CMake Example Usage
• Requred Software: Mac
• License
• Contact information
• NOTE: The old imake-based build has been removed.

Get the sources

git clone https://github.com/sandialabs/seacas.git

This will create a directory that will be referred to as seacas in the instructions that follow. You can rename this directory to any other name you desire. Set an environment variable pointing to this location by doing:

cd seacas && export ACCESS=`pwd`

Build instructions

Automatically download and build dependencies (Third-Party Libraries)

There are a few externally developed third-party libraries (TPL) that are required (or optional) to build SEACAS: HDF5, NetCDF, CGNS, MatIO, Kokkos, and (if MPI set) PnetCDF libraries. You can build the libraries using the install-tpl.sh script, or you can install them manually as detailed in TPL-Manual-Install.md.

• To use the script, simply type ./install-tpl.sh
• The default behavior can be modified via a few environment variables:

• NOTE: The DOWNLOAD and BUILD options can be used to download all TPL source; move to a system with no outside internet access and then build/install the TPLs.
• The arguments can either be set in the environment as: export COMPILER=gnu, or passed on the script invocation line: COMPILER=gnu ./install-tpl.sh

Configure, Build, and Install SEACAS

At this time, you should have all external TPL libraries built and installed into ${ACCESS}/lib and ${ACCESS}/include. You are now ready to configure the SEACAS CMake build.

• cd $ACCESS
• mkdir build
• cd build
• edit the ${ACCESS}cmake-config file and adjust compilers and other settings as needed.
• enter the command ../cmake-config and cmake should configure everything for the build.
• make && make install
• If everything works, your applications should be in ${ACCESS}/bin
• To install in a different location, do INSTALL_PATH={path_to_install} ../cmake-config
• The default behavior can be modified via a few environment variables:

• The arguments can either be set in the environment as: export COMPILER=gnu, or passed on the script invocation line: COMPILER=gnu ./install-tpl.sh

Parallel Build

For some areas of use, a parallel version of SEACAS is required. This will build a "parallel-aware" version of the exodus library and a parallel version of the Ioss library.

The only modification to the serial build described above is to make sure that the mpicc parallel C compiler is in your path and to add the MPI=YES argument to the install-tpl.sh script invocation when building the TPLs. For example:

   MPI=YES ./install-tpl.sh

This will download all requested libraries and build them with parallel capability enabled (if applicable). You can then continue with the steps outlined in the previous section.

Testing

There are a few unit tests for zoltan, exodus, ioss, and aprepro that can be run via make test or ctest if you configured with -D Seacas_ENABLE_TESTS=YES.

There is also a system-level test that just verifies that the applications can read and write exodus files correctly. This test runs off of the installed applications. To run do:

• make install
• cd ../SEACAS-Test
• make clean; make

This will run through several of the SEACAS applications creating a mesh (exodus file) and then performing various manipulations on the mesh. If the test runs successfully, there is some hope that everything has built and is running correctly.

Exodus

If you only want the exodus library, then follow most of the above instructions with the following exceptions:

• Clone entire source tree as above. (There used to be a zip file, but difficult to keep up-to-date)
• You only need the netcdf and optionally hdf5 libraries
• Use the cmake-exodus file instead of cmake-config.
• This will build, by default, a shared exodus library and also install the exodus.py and exomerge.py Python interfaces.

Trilinos

Although SEACAS is included in Trilinos (https://github.com/trilinos/Trilinos), it is also possible to use the SEACAS code from this repository to override the possibly older SEACAS code in Trilinos. The steps are to directly pull SEACAS from github under Trilinos and then build SEACAS under Trilinos with that version using SEACAS_SOURCE_DIR_OVERRIDE. Here is how you do it:

cd Trilinos/
git clone https://github.com/sandialabs/seacas.git
cd BUILD/
cmake -DSEACAS_SOURCE_DIR_OVERRIDE:STRING=seacas/packages/seacas -DTrilinos_ENABLE_SEACAS [other options] ..

SPACK

The SPACK package manager (https://spack.io/) can be used to install SEACAS and all dependent third-party libraries. SEACAS is a supported package in SPACK as of December 2018.

git clone https://github.com/spack/spack.git
. spack/share/spack/setup-env.sh
spack install seacas~mpi   # Serial build (most common)

Docker

An Ubuntu-based Docker image, with SEACAS built and installed, is available on Docker Hub.

docker pull mrbuche/seacas

SEACAS is located in /seacas when running the container. There is also a similar image available on Docker Hub with only Exodus built and installed.

docker pull mrbuche/exodus

CMake Example Usage

A simple example of using the SEACAS Exodus library in your external project. Here is the CMakeLists.txt file:

project(ExodusCMakeExample VERSION 1.0 LANGUAGES C Fortran)
cmake_minimum_required(VERSION 3.1...3.26)

#### C ####
find_package(SEACASExodus CONFIG)
add_executable(ExodusWriteC ExodusWrite.c)
target_link_libraries(ExodusWriteC PRIVATE SEACASExodus::all_libs)

#### FORTRAN #####
IF ("${CMAKE_Fortran_COMPILER_ID}" MATCHES "GNU")
  SET(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -fcray-pointer -fdefault-real-8 -fdefault-integer-8 -fno-range-check")
ELSEIF ("${CMAKE_Fortran_COMPILER_ID}" MATCHES "XL")
  SET(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -qintsize=8 -qrealsize=8")
ELSEIF ("${CMAKE_Fortran_COMPILER_ID}" MATCHES "Cray")
  SET(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -sdefault64")
ELSE()
  SET(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -r8 -i8")
ENDIF()

find_package(SEACASExodus_for CONFIG)
add_executable(ExodusReadFor ExodusRead.f)
target_link_libraries(ExodusReadFor PRIVATE SEACASExodus_for::all_libs)

The cmake-use-example directory contains this sample CMakeLists.txt file and a couple C and Fortran files which provide an example of how to build and link a C or Fortran program with the Exodus library installed as part of a build of this package.

To use this, copy the contents of the directory to your own filespace and modify the contents as needed. The example provides a C executable and a Fortran Executable which both are linked to the Exodus library.

To configure and build, you would do something like:

  mkdir build; cd build
  CMAKE_PREFIX_PATH={path_to_root_of_seacas_install} cmake ..
  make

And you would then get ExodusWriteC and ExodusReadFor compiled and linked against the Exodus library.

Required Software

The SEACAS system requires that there be some libraries and applications already existing on the chosen system prior to building SEACAS and its required Third-Party Liberaries.

These include:

• The git application is used to access the SEACAS and TPL git repositories

• CMake is used to generate the build system.

• C, C++, and (optionally) Fortran compilers. The C compiler must support the C11 standard and C++ must support C+++17. GNU, Clang, Intel, Cray, compilers are supported and tested regularly.

• For parallel capability, an MPI library is needed. We have used openmpi, mpich, mvapich, intel, and cray MPI libraries. It is recommended to use as current an MPI library as possible.

• Automake is used to configure some of the TPL builds

• wget is needed to download some of the TPL library source code.

• python is required to use the exodus.py and exomerge.py Python interfaces to Exodus databases. Python3 is recommended.

• To use the blot and fastq applications, an X11 development environment is needed.

• Flex and Bison are optional if you are developing new capabilities in aprepro.

• M4 is needed to build the netCDF library.

Mac

On a mac system, I use the brew system which provides all of the applications listed above. The X11 system I use is XQuartz. The Mac also requires XCode

Linux

On an ubuntu system, the following is used to set up the basic packages needed to compile SEACAS:

apt install -y libaec-dev zlib1g-dev automake autoconf \
libcurl4-openssl-dev libjpeg-dev wget curl bzip2 m4 flex bison cmake \
libzip-dev openmpi-bin libopenmpi-dev \

Windows

On windows, I have used the following packages for MINGW64:

git mingw-w64-x86_64-toolchain make mingw-w64-x86_64-hdf5 \
mingw-w64-x86_64-cgns mingw-w64-x86_64-netcdf mingw-w64-x86_64-zlib \
mingw-w64-x86_64-gcc-fortran mingw-w64-x86_64-gcc-libgfortran \
mingw-w64-x86_64-cmake mingw-w64-x86_64-fmt

There is also a Visual Studio build performed at each commit to the SEACAS git repository. See the file .appveyor.yml for more details.

License

SEACAS is licensed under the Modified BSD License. See the LICENSE file for details.

The following externally-developed software routines are used in some of the SEACAS applications and are under a separate license:

Contact information

Greg Sjaardema ([email protected], [email protected])