ACCESS Model Output Post-Processor (MOPPeR)

This code is derived from the APP4, initially created by Peter Uhe for CMIP5, and further developed for CMIP6-era by Chloe Mackallah from CSIRO, O&A Aspendale.

ACCESS-NRI Support for ACCESS-MOPPeR

With the conclusion of the ARC Centre of Excellence for Climate Extremes (CLEX), support for ACCESS-MOPPeR is transitioning to ACCESS-NRI.

ACCESS-NRI is committed to providing continuity and will maintain the current version of ACCESS-MOPPeR, ensuring that it remains up to date and usable. Current support will include:

• Bug fixes
• Documentation
• An up-to-date dependency stack
• As time allows, development of new documentation and training examples for users

Community contributions are encouraged, including bug reports, pull requests, and suggestions for new features.

While no new development is currently planned, ACCESS-NRI recognises the value of ACCESS-MOPPeR, particularly for future CMIP7 submissions, and will be actively working with the community to prioritise future work (and resourcing).

ACCESS-NRI acknowledges the outstanding contributions made by the CLEX CMS team in developing and supporting this tool, from the original APP4 (Chloe Mackallah @chloemackallah ) to MOPPeR (Paola Petrelli @Paola-CMS and Sam Green @sam.green). Their work has laid a solid foundation for ACCESS-MOPPeR's continued success.

ACCESS-NRI remains dedicated to making data standardisation easier for users, ensuring that the tool continues to meet the evolving needs of the ACCESS community.

For any questions or support requests, please see ACCESS-Support

What is MOPPeR?

The MOPPeR is a CMORisation tool designed to post-process ACCESS model output. The original APP4 main use was to produce ESGF-compliant formats, primarily for publication to CMIP6. The code was originally built for CMIP5, and was further developed for CMIP6-era activities.
It used CMOR3 and files created with the CMIP6 data request to generate CF-compliant files according to the CMIP6 data standards.The APP4 also had a custom mode option to allow users to post-process output without strict adherence to the ESGF standards. MOPPeR was developed to extend the custom mode as much as it is allowed by the CMOR tool, it can be used to produce CMIP6 compliant data but other standards can also be defined.

CMOR uses Controlled Vocabularies as metadata constraints, with CMIP6_CV.json being the main one. This has an effect on how the data is written in the files, variables' names, directory structure, filenames, and global attributes. The APP4 also relied on mapping files to match the raw model output to CMOR defined variables. To make this approach more flexible we introduced a new tool mopdb that helps the users create their own mapping and handling CMOR tables definitions.

Although we retained a differentiation between custom and cmip mode the main workflow is the same and mode is now only another field in the main configuration file.

See MOPPeR ReadtheDocs for the full documentation.

Install

You can install the latest version of mopper directly from conda (accessnri channel)::

conda install -c coecms mopper

If you want to install an unstable version or a different branch:

* git clone
* git checkout <branch-name>   (if installing a a different branch from master)
* cd mopper
* pip install ./
  use --user flag if you want to install it in ~/.local

Working on the NCI server

MOPPeR is pre-installed into a Conda environment at NCI. Load it with::

module use /g/data3/hh5/public/modules
module load conda/analysis3-unstable

NB. You need to be a member of the hh5 project to load the modules.