A Small Glitch In SeaDAS Installation

[alakes]

There is a small glitch during installing SeaDAS. It's happening for a long time, in between I upgraded & changed my system several times, but the issue is still there. So hope it is not a system related issue. SeaDAS team may look into this.

In pconvert.sh

#! /bin/sh

export SEADAS_HOME=${installer:sys.installationDir}

if [ -z "$SEADAS_HOME" ]; then
    echo
    echo Error: SEADAS_HOME not found in your environment.
    echo Please set the SEADAS_HOME variable in your environment to match the
    echo location of the SeaDAS 7.x installation
    echo
    exit 2
fi

. "$SEADAS_HOME/bin/detect_java.sh"

"$app_java_home/bin/java" \
-Xmx${installer:maxHeapSize} \
    -Dceres.context=seadas \
    "-Dseadas.mainClass=org.esa.beam.pconvert.PConvertMain" \
    "-Dseadas.processorClass=" \
    "-Dseadas.home=$SEADAS_HOME" \
    "-Dncsa.hdf.hdflib.HDFLibrary.hdflib=$SEADAS_HOME/modules/lib-hdf-2.7/lib/libjhdf.so" \
    "-Dncsa.hdf.hdf5lib.H5.hdf5lib=$SEADAS_HOME/modules/lib-hdf-2.7/lib/libjhdf5.so" \
    -jar "$SEADAS_HOME/bin/ceres-launcher.jar" "$@"

exit $?

[OB SeaDAS - dshea]

That is kind of a vestigial script that was never added to the install4j installer process.  We will see if we can update it or simplify it in newer SeaDAS releases.

don