Changes between Version 9 and Version 10 of UM/SingleColumnModel


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

Legend:

Unmodified
Added
Removed
Modified
  • UM/SingleColumnModel

    v9 v10  
    1313== Later versions of the SCM == 
    1414 
    15 The 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. 
     15The Met Office Single Column Model  (SCM) ([https://code.metoffice.gov.uk/doc/um/latest/umdp.html UM documentation paper] C09)  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.