Changes between Version 2 and Version 3 of Projects/NEMOVAR/Instructions


Ignore:
Timestamp:
01/07/15 17:36:45 (4 years ago)
Author:
annette
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Projects/NEMOVAR/Instructions

    v2 v3  
    1 = Running the NEMO-NEMOVAR assimilation suite =  
     1= NEMO-NEMOVAR assimilation suite for MONSooN =  
    22 
    3 Instructions for running [https://puma.nerc.ac.uk/trac/roses_puma/browser/a/a/1/4/5 puma-aa145] on MONSooN.  
     3Instructions for running [https://puma.nerc.ac.uk/trac/roses_puma/browser/a/a/1/4/5 puma-aa145] on MONSooN. This refers to revision 429.  
    44 
    55This is a port of the Met Office suite mi-af769@33134 developed by Chris Hughes. 
     6 
     7== Running ==  
     8 
     9The 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.  
     10 
     11* Take a copy of the suite (using {{{rosie suite-copy}}} or {{{rosie checkout}}}).  
     12 
     13* 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.  
     14 
     15* The suite can then be run using {{{rose suite-run}}}.  
     16 
     17== Editing ==  
     18 
     19To change the start date and run length, edit the {{{START_POINT}}} and {{{RUN_LENGTH}}} variables in the {{{rose-suite.conf}}} file. 
     20 
     21You will also need to edit the "daily_fluxes", "daily_observations" and "fixed_restarts" apps to point to the locations of the input data.  
     22 
     23Unlike many other suites, the app definitions are held in a branch of the UKMO repository: [[br]] 
     24[https://puma.nerc.ac.uk/trac/NEMOCICE/browser/UKMO/branches/dev/annette/r5062_standalone_apps_MONSooN/config/Rose/apps r5062_standalone_apps_MONSooN/config/Rose/apps]  
     25 
     26This is specified in the {{{rose-suite.conf}}} file as follows:  
     27{{{ 
     28#!ini 
     29[file:app/daily_fluxes] 
     30source=svn://puma.nerc.ac.uk/NEMOCICE_svn/UKMO/branches/dev/annette/r5062_standalone_apps_MONSooN/config/Rose/apps/operational_atmospheric_forcing@5256 
     31}}} 
     32 
     33To make changes, checkout a copy of the branch and set {{{source}}} to be the path to the working copy.  
     34 
     35To checkout run:  
     36{{{ 
     37fcm checkout svn://puma.nerc.ac.uk/NEMOCICE_svn/UKMO/branches/dev/annette/r5062_standalone_apps_MONSooN 
     38}}}  
     39 
     40Navigate to the app directories (eg config/Rose/apps/operational_atmospheric_forcing) and edit the environment variables set in the {{{rose-app.conf}}} files.  
     41 
     42If profile input data is available, be sure to switch to the proper version of the "nemo_cice" app.  
     43{{{ 
     44#!ini 
     45[file:app/nemo_cice] 
     46source=svn://puma.nerc.ac.uk/NEMOCICE_svn/UKMO/branches/dev/annette/r5062_standalone_apps_MONSooN/config/Rose/apps/GO5_nemo_GSI6_cice@5256 
     47#source=/home/aospre/code/ukmo/r5062_standalone_apps_MONSooN_no_profile/config/Rose/apps/GO5_nemo_GSI6_cice 
     48}}} 
     49 
     50To do: Move environment variables to higher level so that don't need to change branch to change data directories.  
     51 
     52== Input data ==  
     53 
     54There are interface definitions for each of the apps. 
     55 
     56== Output data ==  
     57 
     58== Timings == 
     59