1. H. Thiemann (M&D) / 02.12.2015 / 1 Hannes Thiemann M&D Statusseminar, 22. April 2004

2. H. Thiemann (M&D) / 02.12.2015 / 2 CERA is the backbone ERA40 IPCC CEOP BALTEX HOAPS CARIBIC WOCE ERA15 NCEP GEBCO COSMOS Simulations @ MPI, GKSS,…

3. H. Thiemann (M&D) / 02.12.2015 / 3 CERA & DKRZ Strong interlink to DKRZ: The application CERA is based on an Oracle database. The Oracle software is supplied by DKRZ. The database itself is maintained by DKRZ (in theory). CERA uses DKRZ hardware (from HLRE) Major changes of CERA implementation within HLRE.

4. H. Thiemann (M&D) / 02.12.2015 / 4 CERA Hierarchy 1.Data catalogue – enable search and identification of data described in a unified way 2.Application oriented data storage within the CERA database. Typically time series of 2 dimensional variables. –Quicker access to data possible –Reduces user requirements 3.Pointer to (external) raw data. –All data can be documented

5. H. Thiemann (M&D) / 02.12.2015 / 5 Metadata Entry This is the central CERA Block, providing information on the entry's title type and relation to other entries the project the data belong to a summary of the entry a list of general keywords related to data creation and review dates of the metadata Additionally: Modules and Local Extensions Module DATA_ORGANIZATION (grid structure) Module DATA_ACCESS (physical storage) Local extension for specific information on (e.g.) data usage data access and data administration Coverage Information on the volume of space-time covered by the data Reference Any publication related to the data together with the publication form Status Status information like data quality, processing steps, etc. Distribution Distribution information including access restrictions, data format and fees if necessary Contact Data related to contact persons and institutes like distributor, investigator, and owner of copyright Parameter Block describes data topic, variable and unit Spatial Reference Information on the coordinate system used CERA-2 Data Model Blocks

6. H. Thiemann (M&D) / 02.12.2015 / 6 User Interface Two choices Web based Graphical User Interface * (GUI) –Search and retrieval of data Batch interface (jblob) * –retrieval of data Both give users the choice of data reduction within one dimension, typically selection based on time. * certain firewall requirements to be fulfilled by users.

7. H. Thiemann (M&D) / 02.12.2015 / 7

8. H. Thiemann (M&D) / 02.12.2015 / 8 Input to CERA 1.Creation of metadata – requires extensive cooperation of data producers with M&D 2.Preparation of input data according to user requirements Strong need for processing capacities at DKRZ for IPCC runs Typically preparation of data split into two parts (1 st level preparation (afterburner), 2 nd level preparation (pingos)). 3.Ingest of data into CERA, problems may arise from certain data formats.

9. H. Thiemann (M&D) / 02.12.2015 / 9 Processing Close cooperation with MPI Pingos: basic bug fixing but no new features. User support! CDOs: still not released. User support! Processing not yet incorporated into CERA environment. (underway).

10. H. Thiemann (M&D) / 02.12.2015 / 10 roblems Organization of workflow Quality of DKRZ data service, to be considered within HLRE 2 Processing capabilities for IPCC More disk space on database servers needed Ingest and retrieval (not storage) of arbitrary formats. GUI needs more flexibility – inclusion of data processing.