COMPILING AND RUNNING

These instructions can also be found in the readme file which accompanies the code delivery to the GDAAC.

Setting the Environment

The environment variables for the site are set in ocean_build.csh or ocean_build.ksh. These files set variable names for various paths (such as toolkit and source code directories) and also set the type of floating point number usage (variable name PGSSGI). These entries must be altered to conform to the paths and floating point number usage of the local site.  Note that ocean_build.csh and ocean_build.ksh also execute the toolkit file pgs-dev-env.csh, which defines more of the environmental variables (e.g. those of the form HDF*).

The names of required environmental variables and the paths they should point to are:

• STORE : $TLCF/MODIS/STORE
• EXEDIR : $TLCF/MODIS/RUN/exec
• OCEANINC : $STORE/shared_src/ocean_incl
• INC : $STORE/shared_src/ocean_incl
• OCEANLIB : $STORE/shared_lib/ocean
• LIB : $STORE/shared_lib/ocean
• API_INC : MAPI2.0 include directory (MAPI2.0/h)
• API_LIB : MAPI2.0 include directory (MAPI2.0/lib)
• # HDFROOT : HDF4.0r1p1
• # HDFEOSROOT : directory which contains "HDF-EOSv1"
• # PGSHOME : PGS toolkit directory

To set environment changes, execute either ocean_build.csh or ocean_build.ksh.

NOTE: The current toolkit defines CFLAGS and CFHFLAGS to include -D_POSIX_SOURCE (for sgi32); ocean_build script redefines these to be just "-g -xansi".

Creating Error Message  Files

MODIS_38101.t is the seed file.  Error message include files can be made using the commands :

$PGSBIN/smfcompile -f MODIS_38101.t -f77 -r -i

$PGSBIN/smfcompile -f MODIS_38101.t -r -i

Compiling the Program

Makefiles are used to help compile the programs. These files contain commands detailing the source files to be used and the linking structure. The UNIX software "make" is then used to compile each program, creating executable (*.exe) files for each main program (such as MODCOL.exe). Each source code directory contains a makefile (called "makefile" or "*.mk"). The source files used can be altered by changing the entries in the makefile.

Use the makefile "makelibs"  to compile the routine libraries (found in Modis/STORE/shared_lib/ocean/oceanLibSrc).  The output from this make will be stored in makelibs.log in the same directory.

To make the MODCOL, MODSST, MSBIN, MTBIN, MCLOUD, MMAP and MSPC  executibles, use the commands:

make -f MOD_PR18.mk,

make -f MOD_PR28.mk,

make -f msbin.mk,

make -f mtbin.mk,

make -f mfill.mk,

make -f mcloud.mk,

make -f mmap.mk, and

make -f mspc.mk

from the appropriate directories (Modis/STORE/PGE09/MOD_PR18, Modis/STORE/PGE10/MOD_PR28, Modis/STORE/shared_src/ocean_src/msbin,   Modis/STORE/shared_src/ocean_src/mtbin,   Modis/STORE/shared_src/ocean_src/mfill, Modis/STORE/shared_src/ocean_src/mcloud, Modis/STORE/shared_src/ocean_src/mmap, and Modis/STORE/shared_src/ocean_src/mspc, respectively).

Running the Program

• the toolkit environment must be defined in ocean_build.csh or ocean_build.ksh
• use : setenv PGS_PC_INFO_FILE path/PCFname

where path is replaced by the path of the PCF and PCFname is replaced by the name of the PCF (e.g. PGE09.pcf for the MODCOL routine).

• use the program executable file (eg. msbin.exe) to run the program

back to MODIS Ocean Data Processing home page

Documented by Jasmine S. Bartlett, COAS, Oregon State University.