The second InfraStructure for the European Network for Earth System Simulation project (IS-ENES2) begun in May 2013, and will run for four years. It is the continuation of two previous projects: IS-ENES and Metafor.

NCAS is engaged in a number of work packages in IS-ENES2, through CMS, NCAS/Climate and the NCAS/BADC (via the BADC host organisation, the Centre for Environmental Data Archival, CEDA. The lead investigator in CMS is Professor Bryan Lawrence. This page summarises the CMS and Climate activities.

The formal engagement is via the following work packages:

Id Effort Short Description of Work Package Activities
NA1 (WP2) 8 pm ENES Strategy: aiming at strengthening the integration of the ENES community. Three main task areas: strengthening the governance of ENES, further develop the ENES strategy, and support community building (including training). CMS is co-leader of this work package with CNRS, and has particular responsibilities for governance and reporting, developing the strategy, and training.
NA2 (WP3) 12 pm Model Futures: The general aim of this work package is to prepare the community for future computing platforms. The CMS engagement in this is three-fold: implementing radiation codes (2014 or later), examining and documenting existing model codes (2013-2014), and organising a workshop on model code comparisons.
NA5 (WP6) 2pm Innovation through collaboration with ICT companies: The main role of CMS is in attending workshops aimed at mutual exchange of information between climate modellers and industry to foster the co-design idea in hardware and software development.
JRA1 (WP9) 16 pm Multi-model, multi-member (M4) high resolution Earth System Models: The main aim is to identify and tackle isues reducing the efficiency of high resolution M4 simulations. The CMS component of this activity, in partnership with NCAS/Climate (Professor Pier-Lugi Vidale) is to set up and run some high resolutions runs and construct and assessment of deficiencies in the infrastructure (including technical aspects of the model itself). There is also a small engagement in submission and job-control issues.
JRA3 (WP11) 21 pm Developing software infrastructure . The CMS role in this wide ranging work package is to develop, extend, and maintain tools for model metadata capture and generation. The existing tools are heavily customised for CMIP5, and need re-factoring to improve flexibility for alternative users, and to support the evolving CIM. The developer will also be responsible for helping validate the scientific content of the model descriptions.

Less formally, CMS is also responsible for leading the model metadata activities across JRA3, NA2 and NA5, and the IS-ENES2 service work packages (not documented here).

NCAS staff can view the google doc plan for who does what using their NCAS logins here.

Last modified 8 years ago Last modified on 05/06/13 08:09:30

Attachments (1)

Download all attachments as: .zip