Administering OpenMadrigal

This document is meant as a manual for administering the OpenMadrigal web site. The OpenMadrigal web site serves a number of purposes:

  1. It distributes the latest version of Madrigal metadata and geophysical data to all the individual sites when they run updateMaster.
  2. It serves as a central web site to inform about the OpenMadrigal project, and to distribute the latest version of the code.

This manual also covers the building and testing of a new Madrigal release. All files relating to OpenMadrigal (including this document) are located in CVS under Millstone/Madrigal/OpenMadrigal.

Distributing Madrigal metadata and geophysical data

Two cron jobs are required to collect these data, createExpUpdate.py and createGeoUpdate.py.

createExpUpdate.py - located in CVS under Millstone/Madrigal/OpenMadrigal/scripts. Usage: createGeoUpdate.py [-e emailAddress] [-e emailAddress2] ... where any number of email addresses can be notified of the results. This script collects the metadata files expTab.txt and fileTab.txt from each of the Madrigal sites listed in siteTab.txt, and stores them in the directory metadata/[site_name]_[site_id]. The site_name and site_id are also set by siteTab.txt. This cron job should be set to run at least once a day, and the results should be emailed to the OpenMadrigal administrator. The results are accessed via the web from the url http://www.haystack.mit.edu/madrigal/distributionFiles/metadata.

createGeoUpdate.py - located in CVS under Millstone/Madrigal/OpenMadrigal/scripts. Usage: no arguments needed. Change name of OpenMadrigal administrator in last line of script to get email notification of script results. This script will update the geofil.tar.Z and ig_rz.dat file on OpenMadrigal. Also updates the file status.dat which indicates the last update date of each type of geophysical data. All the files updated are accessed via the url http://www.haystack.mit.edu/madrigal/distributionFiles. Due to relatively infrequent updates to the base files, this cron job is now run only once a week.

Three core metadata files are also distributed via updateMaster:

The OpenMadrigal administrator is responsible for manually updating these three files on http://www.haystack.mit.edu/madrigal/distributionFiles/metadata whenever they are changed.

Building a new release of Madrigal

From the main directory OpenMadrigal/madroot, a new distribution of Madrigal can be built by running make -f Makefile.gnu distribution or make -f Makefile.solaris distribution. The file MANIFEST in the madroot directory controls which files are included in the tar file. The general test procedure is to build the distribution, and then test install on both linux and solaris machines, both as updates and as new installs. There are also regression tests to be run on the core C and Fortran libraries, and on the Python library.

A regression test for the C and Fortrans libraries is runMadrecDiagnostics, found in CVS under OpenMadrigal/madroot/source/madc/madrec. This regression test can also be run under purify. To do so build the Fortran library geolib with a debug flag. Then build the madrec library using the Makefile.purify file in the madrec directory.

The python regression tests are in OpenMadrigal/madroot/source/madpy/scripts/regressionTests. Each of the following three regression tests are run as $MADROOT/bin/python script:

Revised: May 30, 2008