Home

Introduction

This is a public version of the run manager (RMANAGER) I wrote for the Earth System Modeling Group at Rutgers University. The idea is not new and largely inspired by Jean-Marc Molines' Drakkar Config Manager for NEMO configurations. This tool aims at helping the ocean modeler at :

• running a long simulation, divided in N jobs, by auto-filling the namelist from a template and creating the scripts for the batch scheduler.
• keeping tracks of input files (modified source code, namelist, forcing files,...) used for his/her simulation
• storing output files in an organized way

It is mostly written in python, except for batch scripts. The pre-req are python 2.X with netCDF4 and numpy installed and of course a fortran compiler to compile ROMS.

Installation

The install is not very pythonic and does not use a setup.py script. Simply clone the repository and run the install script with ./install

It will add several environment variables to your .bashrc or .cshrc to point to the python libraries,... You may want to change the value of SCRATCH (by default set to $HOME) to make it point to the scratch of your system. It will also add your login under RMANAGER/user, this is your user space to put namelists (ocean.in), code (config.h,sourcecode.F90),... for your simulations.

testing the install

Open ipython and try:

import libmanager

if you don't see any errors, congrats you're done!

Usage, example from upwelling test case

Let's walk through the usage of the RMANAGER using ROMS simple upwelling test case. First you need a copy of ROMS on your computer. RMANAGER is designed to work with Rutgers ROMS and its close relatives, such as kate hedstrom's branch