1 / 19

Massimo Cocco & Joern Lauterjung

The Technical architecture. Massimo Cocco & Joern Lauterjung. EPOS PP Council Rome September 19 th 2013. Material prepared by WG7. Technical (for the next 5 years). pending challenges/activities Metadata catalogue (demonstrator, FUTUREVOLC as proxies) ICS timeline for implementation

najila
Download Presentation

Massimo Cocco & Joern Lauterjung

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Technical architecture Massimo Cocco & JoernLauterjung EPOS PP Council Rome September 19th2013 Material prepared by WG7

  2. Technical (for the next 5 years) pending challenges/activities • Metadata catalogue • (demonstrator, FUTUREVOLC as proxies) • ICS timeline for implementation • Distributed ICS • (definition & resources) • TCS implementation • (data products, data repository, i.e. rockypedia) • Compatibility layer • Use Case Technical description • IAAA, DOI, PID consolidated issues • Mapping of national RIs (RIDE) • ICS definition & functional architecture • TCS design (role of pillars, and key data products & services) • Metadata structure (3 layers)

  3. EPOS services The EPOS Integrated Core Services will provide access to multidisciplinary data, data products, synthetic data from simulations, processing and visualization tools, ....Not just data access but EPOS means to integrate, analyze, compare, interpret and present data and information about Solid Earth Thematic Core Services are infrastructures to provide data services to specific communities (they can be international organizations, such as ORFEUS for seismology) National Research Infrastructures and facilities provide services at national level and send data to the European thematic data infrastructures.

  4. The National RIs • MAP OF: • - Seismic/GPS stations • Laboratories • - etc…. Diversity in data type and formats http://www.epos-eu.org/ride/ ResearchInfrastructure LIst • 246 Research Infrastructures • 138 Institutions • 22 countries • 2272 GPS receivers • 4939 seismic stations • 464 TB Seismic data • 1.095 PB Storage capacity • 828 instruments in 117 Laboratories

  5. National RI & ThematicServices WG1 - Seismology WG2 - Volcanology WG3 –Geological Data WG4 – GNSS Data WG6 –Analytical and Experimental Laboratories WG8 –Satellite Data WG 9 – Geomagnetic Observ. WG10 - Infrastructures for Georesources

  6. Thematic Services: WG1 Seismological Observatories EPOS Board of Service Providers EPOS Seismology Products and Services (ESPS) EPOS Volcanology EPOS Geology … Other EPOS Communities Governance and coordination by Board of Service representatives, 4-6 members COMPUTATIONAL SEISMOLOGY HAZARD AND RISK EARTHQUAKE PRODUCTS WAVEFORM DATA Parametric earthquake information and event-related additional information Structure: Distributed ~ 5 nodes, including EMSC & its key nodes, AHEAD Products (indicative list) Earthquake parameters & bulletins; earthquake catalogues (instrumental, macroseismic, historic, synthetic); moment tensors; source models Services (…) Rapid earthquake information dissemination (felt maps, ShakeMaps) Ground motion recordings from seismic sensors (possible extension to infrasound) Structure: Distributed (ORFEUS umbrella) ~8 nodes, including ORFEUS & EIDA nodes, SISMOS, SMdB Products (indicative list) Continuous and event waveforms from permanent and temporary stations (broadband, short period, strong motion); historical waveform archive; synthetic waveform data; strong motion data (products) Services (…) Station information (metadata, site characterization…); data quality (control) information European Infrastructures Mobile pools, OBS pools… High performance and high end computing, data intensive computing Structure: Distributed ~3 nodes (build upon VERCE) Products (indicative list) Tools for massive scale data applications (processing, mining, visualization,…) Services (…) Access to HPC resources; data staging; data massive applications; data simulation; model repository and model handling tools (large 3D velocity models, rupture models,…) Seismic hazard & risk products and services Structure: Distributed ~3 nodes, including EFEHR (EUCENTER & ETH nodes) Products (indicative list) Hazard: Fault maps & models; source zones; hazard maps & curves & disaggregation; GMPEs Risk: Inventories & inventory models; vulnerability functions; risk maps & scenarios Services (…) Tools for model building and visualization; product viewer; hazard & risk calculation software & infrastructure Seismological services for visualisation, discovery and access to portal (based on seismicportal.eu ) expert groups, standards e-Seismology & common services EPOS “COMPATIBILITY LAYER” EPOS Integrated Services Visualisation tool / discovery & access portal high performance and high end computing (may absorb E-Seismology) expert groups, standards

  7. Functional Architecture EPOS “COMPATIBLITY LAYER” Arclink seiscomp EUDAT-EPOS EPOS-COOPEUS

  8. EPOS interoperability Metadataorganization Creationof a compatibilitylayer EPOS INTEGRATED SERVICES Thematic service etc. ProperietaryMetadata COMPATIBILITY LAYER EPOS Metadata

  9. Centralized and DistributedICS Distributed Centralized

  10. Notonlydata discovery & mining Processing & Services Visualization Metadata System Manager Code, software, Models... Data Products Raw data

  11. 3-layers metadata model Anticipates data.gov domains Discovery (DC) and (CKAN, eGMS) Web portal, Spatio-Temporal Search Processing & Services Generate Visualization Contextual (CERIF metadata model) Search for instruments, software, models... Metadata System Manager Code, software, Models... Point to Data Products Detailed (community specific) domain-specific data with detailed metadata Raw data Under discussionalso in RDA reccomendationW3Cstandard domain specific - geographically distributed data

  12. Data Taxonomy • Level 0: raw data, or basic data (example: seismograms, accelerograms, time series...) • Level 1: data products coming from nearly automated procedures (earthquake locations, magnitudes, focal mechanism, shakemaps, ....) • Level 2: data products resulting by scientists’ investigations (crustal models, strain maps, earthquake source models, etc...) • Level 3: integrated data products coming from complex analyses or community shared products (hazards maps, catalogue of active faults, etc....) • New Level for software, codes & processing tools!

  13. Technical (for the next 5 years) pending challenges/activities • Metadata catalogue • (demonstrator, FUTUREVOLC as proxies) • ICS timeline for implementation • Distributed ICS • (definition & resources) • TCS implementation • (data products, data repository, i.e. rockypedia) • Compatibility layer • Use Case Technical description • IAAA, DOI, PID consolidated issues • Mapping of national RIs (RIDE) • ICS definition & functional architecture • TCS design (role of pillars, and key data products & services) • Metadata structure (3 layers)

  14. ThankYou WebSite R.I.D.E. www.epos-eu.org www.epos-eu.org/ride Newsletter Epos Social twitter facebook youtube www.epos-eu.org/newsletter

  15. Demonstrator: it is a virtual realization of a piece of the services dedicated to show and disseminate the added value and the features of the integrated core services. Users can play with the demonstrator to understand or perceive what the integrated core services will be. The Demonstrator is needed at the conclusion of the Design phase and during the Validation/Testing Phase. demonstrator/prototype • Prototype: It is the final deliverable of the preparatory phase. It contains the preliminary but quite complete instructions to build and operate the Integrated Core Services (it might also apply to some TCS). It contains a complete list of IT requirements, a check on their availability (existence in TCS) from data providers, a plan for retrieving missing info, the IT and e-science tools and solutions, strategies to build, and needed resources, validation and testing completed, and a designed engineering phase (how to construct) with mid-term sustainability.  The prototype is expected at the end of the delivery phase (M48). GOAL to have a DEMONSTRATOR - Possibly a prototype

  16. ThematicServices: anexample Data Products, analisys & visualization Raw and standardized Data Processing and modeling EPOS “COMPATIBILITY LAYER”

  17. Functional Architecture #1 UserRequest Reporting Visualization Discovery Analysis Mining Simulation IAAA Accounting & Citation Validation Aggregation Access and Retrieval Data / software storage, PID, replication, preservation, versioning Data loading / update / basic validation

  18. USE CASES High Level Use Cases (what the user is trying to achieve) Medium level Use Cases (steps to achieve) ICT Requirements (what the ICT system has to deliver) functional and non-functional

  19. EPOSFramework: a complexmachine SERVICES TO USERS Management Legal Governance Financial Data Users & Scientists Technical Data providers Stakeholders & outreach

More Related