Changes between Version 8 and Version 9 of UM/SingleColumnModel


Ignore:
Timestamp:
24/05/19 11:51:40 (7 months ago)
Author:
willie
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • UM/SingleColumnModel

    v8 v9  
    1313== Later versions of the SCM == 
    1414 
    15 The Met Office Single Column Model  (SCM) \cite{UMDPC9a} \cite{UMDPC9b}  is part of the UM code.  At the Met Office it is run on their desktop PCs. This has Rose, Cylc and FCM together with GCOM and the UM shared library. The SCMs are now in Rose suites and can be discovered through the Rosie tool by searching for "SCUM Template": the template suites have this in the projects field.  Running the suite is a simple matter as it extracts the code, builds it and runs it all on the same desktop. The SCM runs as a parallel MPI program on a single process. The Met Office suite u-bc355 was chosen as a starting point. 
     15The Met Office Single Column Model  (SCM) ([https://code.metoffice.gov.uk/doc/um/latest/umdp.html UM documentation papers] C9a  and C9b)  is part of the UM code.  At the Met Office it is run on their desktop PCs. This has Rose, Cylc and FCM together with GCOM and the UM shared library. The SCMs are now in Rose suites and can be discovered through the Rosie tool by searching for "SCUM Template": the template suites have this in the projects field.  Running the suite is a simple matter as it extracts the code, builds it and runs it all on the same desktop. The SCM runs as a parallel MPI program on a single process. The Met Office suite u-bc355 was chosen as a starting point. 
    1616 
    1717The conversion for NCAS use requires modifications to deal with the PUMA/ARCHER split. Rose, Cylc and FCM are already installed on PUMA, but the SCM executable needs to run on the remote computer ARCHER.  This requires changes to the suite so support the remote operation and also changes to the build process to cope with the ARCHER architecture. 
     
    3434The original intention was to create a version of the SCM that would run on the ARCHER post processor, the non-parallel part of ARCHER.  However, the differences between the compute nodes (the parallel part of ARCHER) and the post processor are too great, involving different Intel Xeon chip sets (Westmere for the post processor and Ivy Bridge for the compute nodes) and consequently different cross compilers.  It was much simpler to build for the compute nodes. 
    3535 
    36 [ARCHERScmTechnical] 
    3736 
    3837=== ARCHER ===