pleiades_build.script

#!/bin/bash
# Build for Pleiades system

usage()
{
    cat <<EOF
Usage $0 [options] <install directory> <absco directory> <merra directory>

This is used to build the Level 2 executable on Pleiades. Note that you need
to supply a "install" directory. This *must* be on one of the NFS systems
(e.g., you home directory). You should not have an executable run from the Lustre
file system (e.g. /nobackup). You can see the Pleiades documentation for a discussion
of this (http://www.nas.nasa.gov/hecc/support/kb/Lustre-Best-Practices_226.html),
but the summary is that they've encounted problems with executables on Lustre and
recommend that you don't run from there.

It is perfectly ok, and even recommended, to have the source and build on the
Lustre filesystem.

Because we aren't on the scf-srv machines, we also don't know where the absco
data is. You need to supply a top directory for this. Note that we need several
versions. Currently (B10.0) we use 3.3.0, v4.1.1_rescaled, and whatever version
we are currently running with (v5.2_final). This can be copied from the
scf-srv system at jpl from the base directory /groups/algorith/l2_fp/absco.

Note that the absco data should be on the Lustre system (e.g., /nobackup)

OPTIONS:
   -h Show this message

   -k Normally we strip out debugging symbols to rduce the space of
      the install. This option keeps them. The code is still compiled
      optimized, it just has the debugging symbols still available.

   -t Include running tests
EOF
}
run_test=n
strip=y
while getopts “htk” OPTION; do
    case $OPTION in
        h)
            usage
            exit 1
            ;;
        t)
            run_test=y
            ;;
        k)
            strip=n
            ;;
        ?)
            usage
            exit
            ;;
    esac
done
shift $((OPTIND-1))
if [ -z "$1" ]; then
    usage
    exit 1
fi
if [ -z "$2" ]; then
    usage
    exit 1
fi
if [ -z "$3" ]; then
    usage
    exit 1
fi

# Die on error
set -e

# Select a newer version of gcc and python
# Note if you change this, also change script/setup_fp_env.sh.in
if [ -e /usr/share/modules/init/bash ]; then
    source /usr/share/modules/init/bash
    # Note we can't use TOSS-4 python3/3.9.5. This pulls in
    # a too new version of HDF5, which I never could figure out how
    # to avoid. Instead we build our own copy of python 3.9.
    # This contains ruby 2.7
    # Note if you update this, make sure to change script/setup_fp_env.sh.in
    # also
    module load  pkgsrc/2022Q1-rome
    # Needed to get ruby working. Not sure why
    ulimit -Ss unlimited
fi
# Create a build directory

mkdir -p build
cd build

# Do configuration
# The extra boost path is needed for libraries boost picks up
../configure THIRDPARTY=build --with-extra-boost-rpath=$PKGSRC_BASE/lib --prefix=$1 --with-absco=$2 --with-python-module --with-merra=$3

# The frontend system typically has 32 processors. We use 20 here, pretty much 
# arbitrarily. This can be adjusted to whatever if needed.

(make -j 20 all || echo $?) 2>&1 | tee make_all.log
if [ "$run_test" == "y" ]; then
   (make -j 20 long_check || exit $?) 2>&1 | tee long_check.log
   (make -j 20 run_tests || exit $?) 2>&1 | tee run_tests.log
fi
# Note that we strip out debugging symbols here. This significanly reduces
# the size of what we install, which matters a lot on Pleiades. If we end up
# have particular issues, we can build and leave in the debugging symbols
if [ "$strip" == "y" ]; then
    (make install-strip || exit $?) 2>&1 | tee install.log
else
    (make install || exit $?) 2>&1 | tee install.log
fi