In the discussion below, we assume the workbench will run on some local machine while the component models will run on one or more different machines.
You must have Java 2 Development Kit installed on the machine the workbench will run on.
The machines the models will run on must have a full Globus installation on them. See Instructions.
Since the workbench only issues Globus commands, the machine it runs on only needs a partial Globus install. This can be done as follows:
globus-install --without-threads --disable-services --disable-devlopment --prefix=DIR --with-ssl-path=DIRSSL
Where DIR is the directory you wish to install Globus in and DIRSSL is the directory containing SSL.
Download and untar the Workbench
Edit JAVADIR at the top of the Makefile to be the location of
the Java Development Kit.
Edit GLOBUSDIR to point to the location of the globus commands such as globusrun
Type 'make' to build the workbench.
Make sure globus will know what your host is by entering (for csh)
setenv GLOBUS_HOSTNAME yourhostyourhost must be the full domain name of the machine you're running the workbench on. If the full name is in /etc/hosts, this is not necessary.
To simplify the possible scenarios presented by the workbench, some of the base components were combined into what looks like one program. The workbench calls a small script which then invokes the pieces.
Download workbench version of runoff model
Download workbench version of mm5coupler (includes a copy of the coupler).
Download workbench version of precipsend (includes a copy of the coupler).
Untar each component in your home directory of the machine you wish to run on. cd to the directory created and build the components as before (./configure followed by 'make all'. You will need GNU make).
In the Workbench directory, edit the file 'input' and replace the machine names there (such as pitcairn.mcs.anl.gov) with the machine you've installed the component on.
While the other components of the workbench are very simple, MM5 is a complex numerical code for simulating thunderstorms. You should gain experience running MM5 "by hand" before running it with the workbench
The workbench can invoke a normal run of MM5. This would use the same executable and runscript you normally use to run MM5. In the globus version of the workbench, the runscript should have complete pathnames and be executable.
When doing a coupled run of MM5 with the runoff model, the version of MM5 will be identical to that used when running the models by hand. That is, it will be an executable compiled with the sockets option. However, you will need a slightly modified namelist and runscript from those used to run the models by hand. The modified namelist contains temporary variables for the hostname and port number. The modified runscript edits this namelist and replaces the temporary variables with the proper values via command line arguments passed to it by the Workbench. Note that the runscript used with the workbench must be executable.
Back to the technical information page
Back to Worbench Main Page