Changes between Version 19 and Version 20 of UmFamous
- Timestamp:
- 24/08/17 14:35:21 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UmFamous
v19 v20 4 4 This is a standalone version of FAMOUS based on version 4.5 of the 5 5 Met Office's Unified Model (UM). 6 7 The current version is 1.0.2. 6 8 7 9 Two 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. … … 24 26 25 27 The 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. 28 It 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. 28 29 29 30 umui 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. 30 31 31 The package tarball is located at: /net/jasmin/users/simon/um_famous .tgz32 The package tarball is located at: /net/jasmin/users/simon/um_famous1.0.2.tgz 32 33 33 34 … … 49 50 == Quick start guide: 50 51 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_famous52 1. 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 52 53 53 54 2. 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). … … 171 172 been installed, add the line 172 173 {{{ 173 export MPI CH_DIR=/path/to/top/level/mpich174 export MPI_DIR=/path/to/top/level/mpich 174 175 }}} 175 176 to your .profile, before the call to setvars, changing the path as required. If MPI is already installed, then add this line 176 177 to point to the local installation. 178 179 Alternatively, 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. 180 Then ensure that $MPI_DIR is not set and 181 {{{ 182 export MPI_MODULES=Y 183 }}} 184 is. 185 177 186 178 187 Next gcom (the system the model uses for multi-processor communications) needs to be compiled using MPI. Type … … 192 201 executable to $DATAW/$RUNID.exec or $DATAW/$RUNID.recon otherwise there is a danger that the 193 202 standard executable under UMDIR will be overwritten. 203 204 == Experimental: Cluster options. 205 206 FAMOUS normally run via the "at daemon 194 207 195 208