Create Monsoon version of c09p0 suite

[endaodea]

• Create version of suite on met office code shared repository (u)
• Create branch on Paris repository (4.0.2 as placeholder until GO version is finally solidified)
• Check suites extracts, runs and builds on monsoon (current developmental suite is on internal cray)
• Sanity check all required inputs are available if not in /projects will make analogue in $DATADIR

Medium term:

• Revise GO suite to run Shelf configuration (upgrade rose version used, this is a nice to have rather than a must have)
• Implement It also in Rob King's all bells and whistles OFRD suite, step one does that suite work with NEMO V4.x Might only work for 3.6
  • Can also bring in obs operator potentially to allow direct comparison with obs as the runs proceeds.

[endaodea]

Have a version of the rose suite at version 4.0.2 on monsoon.

The suite is: u-ca880 It can be found on the Met office collaboration repository under: https://code.metoffice.gov.uk/svn/roses-u/c/a/8/8/0/trunk

To check it out and run: (once you have set up collab repos credentials)

1. fcm co https://code.metoffice.gov.uk/svn/roses-u/c/a/8/8/0/trunk u-ca880
2. cd u-ca880
3. rose suite-run

Making Version 404 should be straightforward. Note for some reason on monsoon the initial stage of nemo takes a very long time, this is even the case if using the same executable and xios executable from the internal MO cray. This adds considerably to the overall run time. As the suite is set up to run in a daily cycle this is a bit of an issue for longer runs.

Either we solve what is the initialization problem on monsoon or we rewrite the suite to cycle on longer timescales e.g. months. Otherwise it probably isn't very efficient to run long runs on monsoon.

[endaodea]

Also have 4.0.4 version of this suite: u-ca907

uses the 404 package branch: nemo_sources=branches/UKMO/NEMO_4.0.4_CO9_package

As in 402 we have an odd slow down (factor of ten) for the initialisation step of NEMO compared to running on internal cray. Source of issue as yet not known

For longer cycle runs e.g. a month the problem wont be to bad but it is a problem for daily cycles which the suite is defaulted to adding order 2 minutes to a <8 minute run.