Version 10 (modified by ros, 17 months ago) (diff)

Flexible Configuration Management System

The Flexible Configuration Management (FCM) system, written by the Met Office, is used to manage code development and release cycles. It has been designed to simplify the task of managing and building source code. FCM uses Subversion for version control; it adds a layer on top of Subversion and defines a common process and naming convention to simplify usage. FCM features a powerful build system, mainly aimed at building modern Fortran software applications.

It is used to manage many difference source codes, including:

  • Unified Model (from vn6.6.3)
  • NEMO
  • CICE

Using FCM

FCM is installed and supported on many platforms. You may need to modify your environment to make FCM available to you.

  • PUMA - fcm is in the user's default environment
  • JASMIN - export PATH=$PATH:/apps/contrib/metomi/bin
  • ARCHER - - module use $UMDIR/modules; module load fcm
  • MONSooN - fcm is in the user's default environment
  • Polaris - export PATH=$PATH:/home/polaris_lds1/earhum/fcm/bin

See the FCM User Guide (html) for full details on FCM.

Using FCM with the UM

There are several things you need to set up before you can use the UM within FCM, these are detailed on the UM Trac pages. We recommend that you begin by reading the FCM Overview document to gain a general understanding of the system components and typical workflow.

An in-depth Tutorial is available for you to have hands-on practice with the system. The tutorial repository is completely separate from the live UM repository and as such is a sandpit for you to try out any FCM commands, etc that you wish. The tutorial takes you through running a UM job, making code changes and resolving conflicts, including all the commands you will need on a day to day basis. It is requested that you complete the tutorial before moving on to working with the real UM repository.

FCM Documentation and Related Links: