Setting Up for the UM FCM Tutorial

In order to complete the tutorial you must be authorized to access the UM Repository and have a Trac account. If you do not already have an account please send an email to r.s.hatcher (at) requesting access to the UM repository. (Note: If you are using the tutorial as part of the UM Training course run by CMS then you will have been sent details of your UM Trac login by email when you registered for PUMA. Email entitled "Access to UM on PUMA")

Enabling Login to Trac

If you are going to complete the 'Making Code Changes' section of the tutorial you will need to be able to login to the Trac wiki/code browser. To do this you must have cookies enabled. In Firefox this can be done by going to Edit->Preferences and enabling the 'Accept cookies from sites' checkbox on the Privacy tab.

Setting up your default text editor

When you attempt to create a branch or commit changes to the repository, you will normally be prompted to edit your commit log message using a text editor. The system chooses its editor by searching for a non-empty string through a hierarchy of environment variables in this order: SVN_EDITOR, VISUAL, and EDITOR. Note that the editor you select must able to run in the foreground. For example, you can add one of the following in your $HOME/.kshrc (Korn) or $HOME/.bashrc (Bash):

# Emacs
export SVN_EDITOR=emacs

# NEdit
export SVN_EDITOR='nedit'

# vi
export SVN_EDITOR='xterm -e vi' 

Set up ssh-agent to allow passwordless login from PUMA to ARCHER

During submission of a job to the remote machine, the system requires to issue multiple commands on the remote machine, it is not possible to supply/capture the password from you during the submit process.

If you can login to ARCHER (ssh <archer_username> without being prompted for a password or passphrase then you are already have ssh-agent set up correctly and can move onto the next section "Setting up UM environment variables on ARCHER" otherwise please follow the instructions on setting up ssh-agent.

Setting up UM environment variables on ARCHER

If you are completely new to the UM (ie. never run a UM job before), then you will need to make sure that you have, at the very least, the following environment variables set in your .profile file on ARCHER, otherwise the UM will fail.

. /etc/bash.bashrc > /dev/null 2>&1

export UMDIR=/work/y07/y07/umshared

# Setup UM Variables
if test -f $HOME/.umsetvars_$VN; then
  . $HOME/.umsetvars_$VN
  . $UMDIR/vn$VN/$TARGET_MC/scripts/.umsetvars_$VN
Last modified 3 years ago Last modified on 03/15/17 20:16:03