Opened 6 years ago

Closed 6 years ago

#1415 closed help (answered)

Adapting a UM job from the Met Office to run on ARCHER

Reported by: swr04ojb Owned by: um_support
Component: UM Model Keywords: porting
Cc: mbollasi@… Platform: ARCHER
UM Version: 7.3


Hello (cc Massimo),

I am helping Massimo in his attempts to port UM job aihsu to ARCHER, to be run with some updated ancillaries. (aihsu was originally run by Nikos Christidis of the Met Office on the M.O. machine). I have seen your page about converting jobs from MONSooN..

and was wondering if there was anything extra we would need to do for jobs from the Met Office?

kind regards,


Change History (3)

comment:1 Changed 6 years ago by grenville


Our usual porting route is MONSooN → ARCHER, with the MO doing the bit prior to that, ie MO → MONSooN, so there may be some small tweaks needed; probably not more than file path issues. Are you planning to go via MONSooN?


comment:2 Changed 6 years ago by mbollasi

Hi Grenville,

I believe we are porting a configuration of an experiment that was run at MO (not on MONSooN). Do you think this would require substantial additional work (beside changes to paths, etc.)?


comment:3 Changed 6 years ago by annette

  • Keywords porting added
  • Resolution set to answered
  • Status changed from new to closed

Hi Oliver and Massimo,

I believe that Grenville discussed this with you further offline, but just for the benefit of others who might look at this ticket…

The main thing that needs to be done when porting directly from the Met Office is that code branches need to be copied over to puma. Some of these may exist on puma already, so it's worth searching the trac system and carefully checking the Met Office revision numbers. Otherwise you need to create a patch:

The FCM settings will also need to be changed - it is best to use an example puma job at the corresponding UM version as a reference.


Note: See TracTickets for help on using tickets.