© Crown copyright Met Office SRNWP Interoperability Workshop, ECMWF, January 2008 SRNWP Interoperability Terry Davies Met Office

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Contents This presentation covers the following areas Introduction Why? How? Discussion

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Why interoperability? Business continuity Initial and lateral boundary conditions Comparison, verification Ensembles Sub-models, e.g. surface model

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 How to achieve interoperability Regular/routine data exchange. Convert between model data formats through agreed common format.

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Flowchart from first draft interoperability proposal

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Simple flowchart of typical NWP or climate suite

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Simple flowchart of typical NWP or climate suite plus imported or exported data in common format

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Common format structure – Header(s) Coded (GRIB) or self describing (NetCDF) Header per record (GRIB) or for collection of records (NetCDF) Main header + sub-headers (NetCDF)

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January D records (GRIB) or 2,3 or 4D records (NetCDF) Number format – 64-bit IEEE? Leave as native? i.e. model level Will need pressure/height converters Horizontal Grids Rotated lat-lon, spherical harmonics, Gaussian, Cubed sphere, Icosahedral, Ying-Yang Lateral boundary frames, variable resolution, Schmidt transform, reduced grids, Staggered grids Common format structure – Data Vertical Grids

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Reconfiguration Putting data in a form used by a particular model configuration. May include change of domain e.g. global to LAM, lateral boundary conditions. May include horizontal and/or vertical interpolation. May include changes to non-atmosphere variables – ancillary fields e.g orography, surface/soil fields (temperature, moisture, vegetation, ice, snow etc.), aerosols, chemistry.

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Reconfiguration issues I Models using different atmosphere variables e.g. hydrostatic/non-hydrostatic, (potential) temperature, specific quantities or mixing ratios etc. Models using different grids e.g. pressure or height based, grid-point or other, staggered/skipped etc. Different ancillary fields e.g. surface/soil fields (land use, vegetation, ice, snow, lakes etc.), aerosols, chemistry.

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Reconfiguration issues II Where models use different algorithms or science then need to exchange information to execute appropriate data conversions. May find it convenient to mix & match i.e. import atmosphere data but use own ancillary data. Allow mix & match only to begin with and add ancillary conversions later.

© Crown copyright Met Office SRNWP Interoperability Workshop ECMWF January 2008 Interoperability programme Agree to where data exchange should fit into archetypal suite structure. Specify supported common formats Allow more than 1? Agree on technical details supported by common formats. Common format documentation and user manual Each consortium to develop its own conversion programs to and from the common formats. Consortia to exchange any algorithmic details required for reconfiguration.

© Crown copyright Met Office SRNWP Interoperability Workshop, ECMWF, January 2008 Questions and answers