Opened 5 years ago

Closed 5 years ago

#1856 closed help (answered)

How to transfer Met Office branch

Reported by: ucfaako Owned by: ros
Component: FCM Keywords:
Cc: Platform: PUMA
UM Version: 6.6.3


I got two branches from the Met Office (Monsoon) that I would like to include in my model run (on ARCHER).
I created an FCM ticket for each of them (252 & 253).
But I accidentally assigned new URLs with the FCM GUI for both Met Office branches outside their directory (rather than in /home/ucfaako/umui_jobs/aniym.monsoon/[branch] they now refer to /home/ucfaako/umui_jobs/aniym.monsoon/).
This means these branches still refer to their old URLs on MONSOON when checking their status inside the branch directory. Could that cause some problems when running the model?
If so is there any way I could change this, so they only refer to their new URL (svn://puma/UM_svn/UM/branches/dev/ucfaako/vn6.6_r24306_CONSERVE_AMTOS_CO2_MAY_2013)?

Many thanks,

Change History (5)

comment:1 Changed 5 years ago by ucfaako

Just realised the tickets are in the FCM Tutorial section not the actual TRAC system. Is it best just to re-create them in the "real" system?

Many thanks for any help!!

comment:2 Changed 5 years ago by ros

  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Alex,

Firstly, the creation of tickets is entirely optional. If it's helpful for you to document the 2 branches then yes, just recreate it/them in the UM Trac.

As for your question about the URLs above, I don't understand what you mean by assigning new URLs.

Running fcm info in /home/ucfaako/umui_jobs/aniym.monsoon/vn6.6_r24306_CONSERVE_ATMOS_CO2_MAY_2013 looks ok:

ros@puma$ fcm info
Path: .
Working Copy Root Path: /home/ucfaako/umui_jobs/aniym.monsoon/vn6.6_r24306_CONSERVE_ATMOS_CO2_MAY_2013
URL: svn://puma/UM_svn/UM/branches/dev/ucfaako/vn6.6_r24306_CONSERVE_ATMOS_CO2_MAY_2013
Relative URL: ^/UM/branches/dev/ucfaako/vn6.6_r24306_CONSERVE_ATMOS_CO2_MAY_2013
Repository Root: svn://puma/UM_svn
Repository UUID: 8ca64e62-1750-0410-b9b8-f1ff413d6028
Revision: 20926
Node Kind: directory
Schedule: normal
Last Changed Author: ucfaako
Last Changed Rev: 20925
Last Changed Date: 2016-04-13 11:22:57 +0100 (Wed, 13 Apr 2016)

We have an FAQ on the website which guides you through applying a patch here:


comment:3 Changed 5 years ago by ros

Oops sorry; I've just realised you're using HG6.6.3 which requires the branches to be created in a different way as 6.6.3 is a minor revision.

Rather than using the GUI to create a branch you must use the create_HG2_branch script. This will prompt you for some input and then create a branch of the form hg6.6.3_<your_branch_name>. Again we have an FAQ which takes you through this:


comment:4 Changed 5 years ago by ucfaako

Many thanks for pointing me in the right direction, worked all well!


comment:5 Changed 5 years ago by ros

  • Resolution set to answered
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.