Context Navigation

ARCHERSCMTechnical

Timestamp:: 24/05/19 11:25:11 (2 years ago)
Author:: willie
Comment:: —

Legend:

: Unmodified
: Added
: Removed
: Modified

UM/SingleColumnModel/ARCHERSCMTechnical

-                      v1
+                      v2
 The Rose suite modifications are in u-bf976.
 The FCM make was modified to include the UM branch and remove FORTRAN flag overrides that were not relevant. The mirror mechanism was added to transfer the code to ARCHER and the platform configuration was set to that specified in the PLATFORM environment variable and the compute host was changed from \verb|self| to ARCHER.
+The FCM make was modified to include the UM branch and remove FORTRAN flag overrides that were not relevant. The mirror mechanism was added to transfer the code to ARCHER and the platform configuration was set to that specified in the PLATFORM environment variable and the compute host was changed from `self` to ARCHER.
 The task graph in the suite configuration file was modified to introduce the "compile on ARCHER" step (second phase of FCM). The following ARCHER modules were set up in the initial script,
 …
 The PLATFORM environment variable was set to \verb|ncas-x86-ifort|\footnote{This is not a good choice of name, the original intention was to emulate the Met Office PC setup which has the x86 architecture.  Subsequently I switched to the compute nodes which have the Cray XC30 architecture}. The environment for building on ARCHER was added.
+The PLATFORM environment variable was set to `ncas-x86-ifort` (This is not a good choice of name, the original intention was to emulate the Met Office PC setup which has the x86 architecture.  Subsequently I switched to the compute nodes which have the Cray XC30 architecture). The environment for building on ARCHER was added.
 == GCOM ==
 On ARCHER GCOM 6.6, built with the Intel compiler via `ftn` for the xc30 compute nodes, was used for the NCAS site. The parallel version \verb|mpp| was used, thus ensuring that the SCM operates in parallel mode.  Later versions of GCOM can be used.
+On ARCHER GCOM 6.6, built with the Intel compiler via `ftn` for the xc30 compute nodes, was used for the NCAS site. The parallel version `mpp` was used, thus ensuring that the SCM operates in parallel mode.  Later versions of GCOM can be used.
 The current build of GCOM is incorrectly labelled on ARCHER - the `ifort15` version is actually built with the Intel version 17 compiler for the compute nodes.
 …
 The SCM is part of the UM code and the build configuration is part of the code too.
+Some modifications of the UM 11.1 code are required. See the development branch `dev/williammcginty/vn11.1_NCAS_SCM_ARCHER`. A new set of make
+        configurations for the ARCHER post processor was created in
+        `ncas-x86-ifort`, based on the Met Office version `meto-x86-ifort`.
+Some modifications of the UM 11.1 code are required. See the development branch `dev/williammcginty/vn11.1_NCAS_SCM_ARCHER`. A new set of make configurations for the ARCHER post processor was created in `ncas-x86-ifort`, based on the Met Office version `meto-x86-ifort`.
 The following FCM make configuration files were modified: under the `inc` directory, the external paths, libraries, parallel and serial configurations. These are shared with the UM. The remaining modifications were restricted to the SCM configuration files. There is one for each level of build: debug, high, rigorous or safe.