Shumlib Release#

Note

Additional details for the shumlib/mule releases can be seen here

Releasing Shumlib#

There’s no hard rule on whether a shumlib release is required - it comes down to whether there have been any notable changes to shumlib since the last release. If there haven’t, then a release isn’t necessary. In this case, the shumlib trunk will get a umX.Y tag during the UM release but that is all.

If you are doing a release then do the following,

  • Create a shumlib ticket and branch, checking out a local copy.

  • Update the shumlib version number in common/src/shumlib_version.h

  • Update the shumlib version number (in a comment) in meto_install_shumlib.sh.

  • Test the branch against the UM

  • Get the ticket reviewed and committed

  • Tag the shumlib trunk with YYYY.MM.V and umX.Y (if at a UM release).

Installing Shumlib#

Shumlib is installed with a build script, at scripts/meto_install_mule.sh. This takes a single compulsory argument to set the platform of the install. Generally, this is a platform at the Met Office, currently ex1a or azspice, which will install shumlib for all defined builds on that platform. Alternatively, you can use a specific build, eg. azspice_gnu_12.2, to install just for that build.

By default, shumlib will be installed in a build directory in the working copy. This can be controlled using the BUILD_DESTINATION environment variable.

To install at the Met Office, login as umadmin and checkout a copy of the shumlib trunk (using the mirror repo). First install on azspice,

BUILD_DESTINATION=$UMDIR/shumlib/shumlib-YYYY.MM.V scripts/meto_install_shumlib.sh azspice

Then ssh to each of EXAB, EXCD and EXZ and install there,

BUILD_DESTINATION=$UMDIR/shumlib/shumlib-YYYY.MM.V scripts/meto_install_shumlib.sh ex1a

Finally do the install on Monsoon (using umadmin.mon shared user).