This page documents RPM files produced for running the Unified Model (UM) version 4.5 under RedHat Linux.
The RPMs are designed to provide a quick start to running the UM and its User Interface (UMUI). Both single-processor and parallel versions are included (the latter included primarily to take advantage of multi-processor PCs), and both 32-bit and 64-bit versions of the model are available. The RPMs contain template jobs for running the UM in atmosphere (HadAM3), ocean (HadOM3) and coupled (HadCM3) configurations. (To achieve this, the RPMs contain a number of code update files ("mods") and ancillary data files beyond those the Met Office distribution.)
The RPMs were built for use on PCs running the following software:
Use on other platforms may or may not work. (See below.)
The RPMs are available via the Portable Unified model page of the BADC. Because of Met Office licensing condition, you will need to sign a registration form. This will then give you access both to the RPMs and also to the UM package in the form originally distributed by the Met Office.
(Note that the need to sign the Met Office agreement does not imply that every package in that BADC directory is subject to that agreement. Each RPM file clearly states in the header which licence is applicable, and in particular if a package is labelled as GPL then you have the full rights granted by the GPL, and the fact that it was distributed alongside the UM does not imply any further restriction.)
Use of RPM pacakages means that installation is straightforward, provided that your system is the target platform.
You should find the following files in the "binaries" directory on the BADC archive. Download and install all these packages on your system (generally using the rpm -i command as root), except that you may omit the 32-bit packages if only intending to run at 64-bit, and vice versa, and other packages described as optional.
This should contain the following line:
localhost usernameSubstitute for username as appropriate. (Ensure that neither the
.rhostsfile nor your home directory is either group- or world-writable, else your
.rhostswill not be honoured by the system.)
This should be a copy of (or a link to) the setvars file in the UM_HOME directory which you will be using, i.e. either /usr/lib/um/um32/setvars or /usr/lib/um/um64/setvars depending on 32- or 64-bit.
All being well, this should be all you need to do to get the UM running a sample job in your chosen configuration. The hope is that these RPMs will have enabled you to get to this starting point relatively quickly. Where you go from here is up to you...
If you are using GNOME, you may find that the GNOME panel obstructs part of the UMUI windows. Consider using the "auto-hide" option in the GNOME panel (right-click on a blank part of the panel to access the properties menu).
If you will be running the UM with a slightly different version of the Linux operating system or compiler than the supported platform, it is possible that the binary RPMs will not work but that you may have some success with downloading the source RPMs and rebuilding.
To rebuild from a source RPM, type: rpmbuild --rebuild source_filename. This will rebuild binary RPMs in /usr/src/redhat/RPMS/i386, which you can then install as normal (although note that for the main UM package rebuilding can be very slow).
If the build process does not complete cleanly, then you can modify the build process by installing the source package with rpm -i source_filename, and then editing the "spec" file in /usr/src/redhat/RPMS/SPECS before building the binary package with rpmbuild -bb spec_filename. (Depending on the changes required, this may be more work than simply performing some post-installation tweaks on your system, but if you generate working RPMs for your platform and feed back the changes then you are providing a valuable contribution to the community -- address below.)
The Unified Model was written by the Met Office. The xconv program was written by Jeff Cole. The RPM packaging, including build scripts and patches to the original source code, was written by myself (Alan Iwi <A.M.Iwi@rl.ac.uk>), and I would welcome any feedback or suggestions.