Changes between Version 19 and Version 20 of UmFamous


Ignore:
Timestamp:
24/08/17 14:35:21 (22 months ago)
Author:
simon
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • UmFamous

    v19 v20  
    44This is a standalone version of FAMOUS based on version 4.5 of the 
    55Met Office's Unified Model (UM). 
     6 
     7The current version is 1.0.2. 
    68 
    79Two standard FAMOUS versions are supplied, one with the MOSESI land-surface scheme, and the other with MOESEII.2. The base runids for these configurations are xhmkq and xfhcr (under robin) respectively. 
     
    2426 
    2527The UM and FAMOUS can be installed on any linux system, from laptops to clusters. Currently the only job control software supported is the at daemon. 
    26 It is possible to run with other job control systems such as Sun Grid Engine and SLURM, and versions which support these will be released 
    27 in the future. 
     28It is possible to run with other job control systems such as Sun Grid Engine and SLURM, and an experiment system for this functionality is included, see below. 
    2829 
    2930umui configurations are available for both MOSESI and MOSESII. These have been simplified as much as possible with the mods and handedits concatenated and superfluous options removed. 
    3031 
    31 The package tarball is located at: /net/jasmin/users/simon/um_famous.tgz  
     32The package tarball is located at: /net/jasmin/users/simon/um_famous1.0.2.tgz  
    3233 
    3334 
     
    4950== Quick start guide: 
    5051 
    51 1. Copy /net/jasmin/users/simon/um_famous.tgz and unpack on the machine on which you want to run FAMOUS. The system will be unpacked into a directory called um_famous 
     521. Copy /net/jasmin/users/simon/um_famousx.x.x.tgz and unpack on the machine on which you want to run FAMOUS. The system will be unpacked into a directory called um_famous 
    5253 
    53542. Edit example.profile to change the values of UMDIR and DATA_DIR, and append to your $HOME/.profile . (If $HOME/.profile doesn't exist, create it). 
     
    171172been installed, add the line 
    172173{{{ 
    173 export MPICH_DIR=/path/to/top/level/mpich 
     174export MPI_DIR=/path/to/top/level/mpich 
    174175}}} 
    175176to your .profile, before the call to setvars, changing the path as required. If MPI is already installed, then add this line 
    176177to point to the local installation. 
     178 
     179Alternatively, if you local system uses modules, ensure that the required MPI (and compiler if needed) modules are loaded when a session is started, normally be placing the module load command in ~/.profile. 
     180Then ensure that $MPI_DIR is not set and 
     181{{{ 
     182export MPI_MODULES=Y 
     183}}} 
     184is. 
     185 
    177186 
    178187Next gcom (the system the model uses for multi-processor communications) needs to be compiled using MPI. Type 
     
    192201executable to $DATAW/$RUNID.exec or $DATAW/$RUNID.recon otherwise there is a danger that the 
    193202standard executable under UMDIR will be overwritten. 
     203 
     204== Experimental: Cluster options. 
     205 
     206FAMOUS normally run via the "at daemon 
    194207 
    195208