Changes between Version 7 and Version 8 of UmFamous


Ignore:
Timestamp:
14/04/16 14:04:49 (5 years ago)
Author:
simon
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • UmFamous

    v7 v8  
    11 
    2 == Standalone UM system and FAMOUS == 
     2= Standalone UM system and FAMOUS = 
    33 
    44This is a standalone version of FAMOUS based on version 4.5 of the 
     
    1616details. 
    1717 
     18All of the standard FAMOUS input ancillaries are supplied, together with a selection of dumps. 
     19 
    1820The 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. 
    1921It is possible to run with other job control systems such as Sun Grid Engine and SLURM, and versions which support these will be released 
     
    2224This document assumes the user is familiar with the UM and umui. 
    2325 
    24 === Prerequisites: 
     26== Prerequisites: 
    2527 
    2628Running without compilation: 
     
    3335* A MPI implementation  
    3436 
    35 === Quick start guide: 
     37== Quick start guide: 
    3638 
    37391. Copy /net/jasmin/users/simon/um_famous.tgz and unpack on the machine on which you want to run FAMOUS. 
     
    53555. On the installation machine type: 
    5456{{{ 
    55 umsubmit_local -u pumaid runid 
     57umsubmit_local -u pumauserid runid 
    5658}}} 
    5759 
     
    6365}}} 
    6466 
    65 === FAMOUS configuration 
     67== FAMOUS configuration 
     68 
     69=== MOSESI and MOSESII 
     70 
     71Seperate MOSESI and MOSESII.2 configurations are available. The base umui jobs can be used to build and run each of these.  
     72 
     73=== modsets 
     74 
     75The difference between MOSESI and MOSESII modsets are considerable. In fact, MOSESII code 
     76does not exist as part of the standard UM4.5 release and can only be configured as mods. Therefore it was decided that there should be different standard mods for each configuration. All of the various model mods for the two FAMOUS configurations are now held in 5 mods, these are: 
     77 
     78 source_common.mod:: FORTRAN mods which are common to both MOSESI and MOSESII 
     79 
     80 source_common_c.mod:: C mods which are common to both MOSESI and MOSESII 
     81 
     82 source_MOSESI.mod:: MOSESI exclusive mods 
     83 
     84 source_MOSESII.mod:: MOSESII exclusive mods 
     85 
     86 port_end_f.mod:: mod which allows IO on little endian machine, such as Linux. UM files are natively bigendian. It was decided to keep this separate to allow easy porting of a model configuration to a bigendian machine such as IBM Power. 
     87 
     88Similarly there mods for the reconfiguration. 
     89 
     90 recon_common.mod:: FORTRAN mods which are common to both MOSESI and MOSESII 
     91 
     92 recon_MOSESI.mod:: MOSESI exclusive mods 
     93 
     94 recon_MOSESII.mod:: MOSESII exclusive mods 
     95 
     96 
     97These mods are concatenations of the standard mods for each model. The tool $UMDIR/tools/make_mod.sh was used for this.  
     98 
     99=== handedits 
     100 
     101=== umui 
    66102 
    67103FAMOUS is configured via the umui as usual. The standard FAMOUS jobs have be rationalised to make their configuration as simple as possible. 
    68104 
    69 Output dir 
     105=== Directories 
    70106 
    71 ARCHIVE_DIR 
    72  
    73 CHange dates 
    74  
    75 mods 
    76  
    77 handedits 
    78  
    79 processor number 
    80  
    81 === Intel FORTRAN, MPI and gcom 
     107== Intel FORTRAN, MPI and gcom 
    82108 
    83109The model tarball comes complete with a pre-built MPICH3.2 system. The default installation is configured to use this. If the model needs recompilation, or 
     
    104130in $UMDIR/gcom3.8/gcom/lib. 
    105131 
    106 === Changes from standard UM/FAMOUS 
     132== Changes from standard UM/FAMOUS 
    107133 
    108134* Linux only.