wiki:Projects/NEMOVAR/Instructions

NEMO-NEMOVAR assimilation suite for MONSooN

Instructions for running puma-aa145 on MONSooN. This refers to revision 429.

This is a port of the Met Office suite mi-af769@33134 developed by Chris Hughes.

Running

The suite is set up to run a 2 day test with 1 day cycling, starting from 1 Jan 2011. Note that for this particular date, no profile data are available, so the "daily_observations_profile" app will fail. The NEMO observation operator can still run without this data, however, and the suite should continue to run.

  • Take a copy of the suite (using rosie suite-copy or rosie checkout).
  • Edit the GROUP variable in the rose-suite.conf file to your MONSooN project (it is currently set to "jomp"). No other changes should be required.
  • The suite can then be run using rose suite-run.

Editing

To change the start date and run length, edit the START_POINT and RUN_LENGTH variables in the rose-suite.conf file.

You will also need to edit the "daily_fluxes", "daily_observations" and "fixed_restarts" apps to point to the locations of the input data.

Unlike many other suites, the app definitions are held in a branch of the UKMO repository:
r5062_standalone_apps_MONSooN/config/Rose/apps

This is specified in the rose-suite.conf file as follows:

[file:app/daily_fluxes]
source=svn://puma.nerc.ac.uk/NEMOCICE_svn/UKMO/branches/dev/annette/r5062_standalone_apps_MONSooN/config/Rose/apps/operational_atmospheric_forcing@5256

To make changes, checkout a copy of the branch and set source to be the path to the working copy.

To checkout run:

fcm checkout svn://puma.nerc.ac.uk/NEMOCICE_svn/UKMO/branches/dev/annette/r5062_standalone_apps_MONSooN

Navigate to the app directories (eg config/Rose/apps/operational_atmospheric_forcing) and edit the environment variables set in the rose-app.conf files.

If profile input data is available, be sure to switch to the proper version of the "nemo_cice" app.

[file:app/nemo_cice]
source=svn://puma.nerc.ac.uk/NEMOCICE_svn/UKMO/branches/dev/annette/r5062_standalone_apps_MONSooN/config/Rose/apps/GO5_nemo_GSI6_cice@5256
#source=/home/aospre/code/ukmo/r5062_standalone_apps_MONSooN_no_profile/config/Rose/apps/GO5_nemo_GSI6_cice

To do: Move environment variables to higher level so that don't need to change branch to change data directories.

Input data

Data required:

  • ancillary (same files used throughout the run):

nemo_cice_nemovar_ancillary.txt

  • restarts (first timestep only):
    restart_YYMMDD/
      restart_xxxx.nc 
      pcbias_xxxx.nc
      cice_restart.dat
    
  • observations:
    DATE has the form YYYYMMDD
    
    Altimeter/sla_${DATE}.nc.gz  
    GHRSST/GHRSST_AVHRR.${DATE}.nc.gz 
          /GHRSST_METOP.${DATE}.nc.gz
    Profile/
    SeaIce/seaice.1.${DATE}.nc.gz  
          /seaice.2.${DATE}.nc.gz  
    Surface/Surface_${DATE}.nc.gz  
    

  • fluxes (every day +- 1):

sbc_core_forcing.txt

Output data

Rose suites write output to two directories. Data volumes are from /opt/freeware/bin/du -sh:

  • work : 90 GB per day
  • share : 4 GB initial (fcm_make_nemo and data/ancillary) + 5.5 GB per run day

To do: Make sure suite not making unnecessary copies of data. Plan for post-processing.

Timings

From 2 day test run on 196 MPI tasks (6 nodes).

App Day 1 Day 2
nemo_cice_obsoper 685 s 703 s
nemovar 543 s 558 s
nemo_cice_iau 609 s 603 s

Note these times are for the full app which includes the parallel executable and serial processing scripts.

Last modified 4 years ago Last modified on 01/07/15 18:54:37