Presentation is loading. Please wait.

Presentation is loading. Please wait.

Information Technology  What is GEM  Architecture and Why  Development Process  Demonstration John Tarter/Damiano Monelli| e-Science workshop.

Similar presentations


Presentation on theme: "Information Technology  What is GEM  Architecture and Why  Development Process  Demonstration John Tarter/Damiano Monelli| e-Science workshop."— Presentation transcript:

1 Information Technology  What is GEM  Architecture and Why  Development Process  Demonstration John Tarter/Damiano Monelli| e-Science workshop

2 What is GEM  State of the Art Models and Tools for earthquake risk assessment worldwide  Design, Development and Deployment with the Global Community  3 Major Components – Hazard, Risk and Social Economic Impact. Will provide complete calculation from Hazard through to the SEI impacts.  Global Collaboration – 10 Global Components Partner Projects Catalogues/Data Collection Contribution to PSHA Model input to Hazard – 3 Regional programmes and increasing  Defined by the Science teams  Design will enable other Risks to be assessed in future Global Earthquake Model

3 GEM Founders and Partners

4 GEM - Architecture  Open Source http://openquake.org/http://openquake.org/  Python  Early development in Java – Rewriting various components for performance  Natural hazard Risk ML standardized input/outputs  API for UI and Application accesses into system  Open Source GIS Partner  UI development starting Q2 OpenQuake Web service

5 GEM Architecture

6 GEM to the Cloud  Operational – Back Ups - Restores – Immediate rebuilds – Known/Few Change Windows – Detailed Billing  Hardware – Immediate Provisioning – Team focus on development – Maintenance and Repair – Upgrades to memory and disk in minutes – Vendor manages Operating Systems Patching Upgrading Addressing the Unknown

7 GEM - Development  Agile  Test Driven Development  2 -3 week Sprints  Science Team – Write Blue Prints – Defines Stores – Sets priorities  Able to respond to emerging priorities and new science developments  Daily Scrums  Science Writes Blue prints and development stories

8 GEM - Development  Code Reviews  Test Coverage validation  Code Quality validation  GitHub  Automated Build Processes  Full Smoke test before merging to main branch  Sphinx documentation generation  Same Rules Apply for GEM developers as Open Source Contributors  3 contributors so far Quality and Documentation

9 GEM – Future Considerations  Adaptable to new or emerging science  Designed using tools and standards that are mature and not heading to end of life  Open Source Community involvement  All Interface points are documented and published to assure future integration

10 GEM - Demonstration  Questions?


Download ppt "Information Technology  What is GEM  Architecture and Why  Development Process  Demonstration John Tarter/Damiano Monelli| e-Science workshop."

Similar presentations


Ads by Google