ROMS UNSW2008

Installing and Running ROMS for First Time Users

A Tutorial at the UNSW Computer Labs, 30 March 2009

John Wilkin - this is work in progress

A tutorial for new ROMS users will be held at the UNSW Computer Labs on Monday 30 March 2009, immediately prior to the ROMS Sydney 2009 User Workshop at the Sydney Institute of Marine Sciences, 31 March to 2 April 2009.

This tutorial is intended for complete newcomers to ROMS. It assumes basic knowledge of working in a UNIX environment, and that the essential components required to compile and execute ROMS are already installed on the host computer network. This wiki page borrows heavily from David's Robertson's excellent Installing ROMS under Cygwin tutorial where you will find more information about setting up the required computing environment (compilers, libraries etc.) for ROMS.

In this tutorial, we cover how to download the code, configure it for an application, and run the model. Error messages that arise during the configuration process will be explained so that these can better be debugged when users return to their home institutions and try to work through this process again.

This wiki entry will be updated on tutorial day as we discover the questions that arise when a set of novice users approach using ROMS for the first time.

Download ROMS

The disk space available on the UNSW Computer Lab machines is quite limited, so for the purposes of this tutorial we have downloaded the ROMS source code to /tmp/jwilkin/src on host matht001. Instructions below will explain how to point the build.bash script that compiles ROMS to this directory.

To download the code to your own machine, these are the steps you follow:

• You must have already registered on the ROMS portal and obtained your ROMS username/password as indicated in the Register.

• Create a src folder where you will keep the ROMS source code. You can place this wherever you wish in your directory tree (here we assume under your home directory "~") and name it whatever you like.

cd ~
mkdir src

• Check out the ROMS source code replacing bruce with the ROMS user name you registered with.

svn checkout --username bruce https://www.myroms.org/svn/src/trunk src

Note the target directory src at the end of the command. If your code ends up in the wrong place, you may have omitted this.

You will see many lines stream by indicating the files that are being added to your src directory. When it finishes, you can type ls src to see the contents of the directory.

To see the contents of the directory where the code is downloaded for this tutorial, type this:

cd /tmp/jwilkin
ls src

Customize the Build Script

The ROMS source code comes with a build script in the ROMS/Bin directory. Examples written with bash (build.bash) and csh (build.sh) are provided. The UNSW Computer Lab machines are configured to use bash as the default login shell, so we will work with build.bash. A full description of the build script can be found here.

• In your home directory, or in whichever directory you want to organize your ROMS projects, create a new folder named Projects and change into it.

cd ~
mkdir Projects
cd Projects

• Create a folder named upwelling and change into it. upwelling is the name of the ROMS test case we are going to compile and run.

mkdir upwelling
cd upwelling

• Copy the build.bash file distributed with ROMS to your Projects/upwelling directory.

cp /tmp/jwilkin/src/ROMS/Bin/build.bash .

Next we need to configure a few options inside build.bash so that it finds the directories where the source code and your Project are located.

• Open the build.bash script you just copied into your upwelling directory using your preferred text editor, e.g. vi.

vi build.bash

• Scroll down until you find MY_PROJECT_DIR and set it as follows.

export MY_PROJECT_DIR=${HOME}/Projects/upwelling

This obviously assumes you put Projects/upwelling under your home directory.

If you frequently move your ROMS project between hosts where you have a different directory structure, e.g. a temporary scratch space, you can use the MY_ROOT_DIR variable to minimize the changes you make to build.bash.

• For example:

export MY_ROOT_DIR=/usr/scratch/bruce
export MY_PROJECT_DIR=${MY_ROOT_DIR}/Projects/upwelling

Next we tell build.bash where to find the ROMS source code downloaded from the svn repository (which you can keep up to date the svn update command - see more on this at LINK ). Note that most of the source code changes you make to customize ROMS will be made in your Projects space, and need not be made to the downloaded code directly. We will discuss exceptions to this during the tutorial, and how source code modifications interact with svn.

• Set MY_ROMS_SRC to the location of the source code:

export MY_ROMS_SRC=/tmp/jwilkin/src

In practise, you will probably do something more like this:

export MY_ROMS_SRC=${MY_ROOT_DIR}/src

assuming this is the relative path in which you keep your source code on the various machines you work on.

Make sure that MY_CPP_FLAGS is not set. Sometimes this is set in the distributed build.bash exmaple. Comment out options with the # symbol like so:

#export MY_CPP_FLAGS="-DAVERAGES"

The UNSW Computer Lab machines are single core, so we need to tell build.bash not to assume MPI parallel compilation.

• Comment out the options for USE_MPI and USE_MPIF90

#export USE_MPI=on
#export USE_MPIF90=on

• If you were compiling in parallel you would leave the default entries in build.bash. We also leave the compiler option as the default because this says use the ifort (Intel FORTRAN) compiler which is what we want on the UNSW machines.

export USE_MPI=
export USE_MPIF90=
export FORT=ifort

• We leave the compiler option as the default because this says use the ifort (Intel FORTRAN) compiler which is what we want on the UNSW machines.

export FORT=ifort

Save and close the build.bash file.

• You will need to add the following two lines anywhere above the line that reads cd ${MY_ROMS_SRC}

export NETCDF_INCDIR=/usr/local/include
export NETCDF_LIBDIR=/usr/local/lib

Copy the input and CPPDEFS options files

We need two more files in Projects/upwelling to configure and run ROMS. We copy the versions downloaded with svn because these are files you will work with locally when you experiment with changes to the test case example configuration.

• Copy files ocean_upwelling.in and upwelling.h into the Projects/upwelling directory you just created.

cd ~/Projects/upwelling
cp /tmp/jwilkin/src/ROMS/External/ocean_upwelling.in .
cp /tmp/jwilkin/src/ROMS/Include/upwelling.h .

View the file upwelling.h. It contains all the C-Pre-Processor (CPP) options that the compiler interprets to activate certain source code options within ROMS.

View the file ocean_upwelling.in. It contains the inputs options that ROMS reads at run time to set options that need not be fixed at compile time.

Now we are ready to compile ROMS by executing the build.bash script.

Compile ROMS

Before you run ROMS, you need to compile it to create an executable oceanS file (S for serial or single processor computer), or oceanM file (if using MPI on a parallel computer).

• Go to your upwelling project directory:

cd ~/Projects/upwelling

• Then type:

./build.bash

• If lots of stuff comes on the screen then compilation is proceeding, and make take some time.

• If the build process ends quickly with an error, then it is likely that build.bash does not point to the correct location for the upwelling.h file, the compiler, or libraries.

Compile time error messages

Getting past the first few errors with compilation is often tricky. Carefully read any error messages you get for clues on what might be wrong with your configuration

• Compilers/../ROMS/Include/cppdefs.h:709:22:
  error: /student/0/a0000020/Projects/upwelling/upwelling.h: No such file or directory
  This says the file upwelling.h is not where Build expects it to be, which is in MY_PROJECT_DIR. You set this to ~/Projects/upwelling.

• cp: cannot stat `/opt/intelsoft/netcdf/include/netcdf.mod': No such file or directory
  This says the netcdf include file upwelling.h is not where Build expects it to be.