Version 11 (modified by ros, 2 years ago) (diff)

The Post Processing App for ARCHER/NEXCS

This page refers to the Rose post processing App used within cycling suites to archive data (e.g to the RDF for ARCHER) and optionally to subsequently transfer the data to JASMIN. This is valid from UM version 10.0 onwards. The app archives and deletes model output files, not only for the UM, but also for NEMO, including MEDUSA if appropriate, and CICE in coupled configurations. The app is designed to run once at the end of each cycle of a model run.

Upgrading the Post Processing App

Moving from UM Repository to MOCI - Version postproc_1.0

Note: This only applies if you are using a UM version prior to version 10.3

The post processing app originally resided in the UM repository, but was removed prior to the release of version 10.3. In January 2016 postproc_1.0 was released on the MOSRS MOCI repository, and users should upgrade all suites currently using the UM repository to use the new version. A short guide is available on the MOSRS for users needing to make this upgrade.

Upgrading to the ARCHER/NEXCS Post Processing Release Version

The post processing for ARCHER has now been accepted onto the Met Office MOCI trunk and was included in release version postproc_2.2.

Please ensure that the Rose Editor is closed before attempting to upgrade. These instructions assume you are upgrading using centrally held meta-data.

  1. Upgrade the fcm_make_pp app:
  • cd to app/fcm_make_pp
  • Make sure the app is using centrally held metadata (e.g. meta=archive_and_meaning/fcm_make/postproc_2.1 in rose-app.conf)
  • Run rose app-upgrade -a postproc_2.2
  1. Upgrade the postproc app:
  • cd to app/postproc
  • Make sure the app is using centrally held metadata (e.g. meta=archive_and_meaning/postproc/postproc_2.1 in rose-app.conf)
  • Run the command: rose app-upgrade -a postproc_2.2

If it fails to find the upgrade tag postproc_2.2 then run the command rose app-upgrade -a to list all available tags to check what is listed. You should see something like:

$ rose app-upgrade -a
= postproc_2.1
* postproc_2.2

Configuring fcm_make_pp

In Rose edit navigate to panel "fcm_make_pp → Configuration" and make the following changes:

  1. Set config_base to: fcm:moci.xm-tr
  1. Set config_rev to: @postproc_2.2
  1. Set pp_rev to: postproc_2.2
  1. Remove old branches that refer to old postproc versions.

Configuring postproc

Postproc can be configured for Archer to archive data to the RDF (Research Data Facility) or for NEXCS to a temporary location on the /projects disk before optionally transferring to JASMIN.

  1. In panel "postproc → Post Processing - common settings" select the appropriate archive_command.
  1. In panel "postproc → Post Processing - common settings → Archer Archiving" set the following:
    • archive_root_path - The directory you wish to archive to. Usually somewhere under /nerc/n02/n02/<username> for RDF or /projects/nexcs-n02/<username> for NEXCS. This will have the archive_name (by default the suite id) appended to it.

The next 4 points (3-6) are for Archer setup only.

  1. In panel "postproc → CICE → Diagnostics → Meaning" set:
    • means_cmd to be ncra -64bit -O
  1. In panel "postproc → NEMO" set:
    • exec_rebuild to be $UMDIR/nemo/utils/src/REBUILD_NEMO/BLD/bin/rebuild_nemo.exe
  1. In panel "postproc → NEMO → Diagnostics → Meaning" set:
    • means_cmd to be $UMDIR/nemo/utils/bin/
    • ncatted_cmd to be ncatted
  1. In panel "postproc → Atmosphere" set:
    • um_utils to be $UMDIR/vn10.7/cce/utilities, replacing vn10.7 with the appropriate UM version as necessary.

Transfer of archived files to JASMIN

Optionally, it is possible to initiate a transfer of the files from the RDF on ARCHER or from NEXCS onto JASMIN - this is called the transfer app and is a variation of the postproc app.

If you wish to transfer your archived data to JASMIN, you will need to do some further setup.

In panel "postproc → JASMIN Transfer" set:

  • transfer_dir - Enter the directory on JASMIN to transfer to. This should be one of the group workspaces.
  • transfer_type - This should be set to "Push" for both Archer and NEXCS.
  • remote_host - This is the host to which you are pushing data to (e.g. or
  • verify_chksums - Select "True" if you wish the transfer app to verify integrity of the transferred files by verifying their checksums.
  • gridftp - Select this option if you wish to use gridftp rather than rsync to transfer the files. (This option is not available on NEXCS)

The transfer runs either on the Data Transfer Node ( for ARCHER or in the shared queue on NEXCS.

[To Do: Add a note about the 2 JASMIN transfer nodes.]

ARCHER setup instructions

NEXCS setup instructions