1 / 12

OOI-CI & IOOS-DMAC Intersection Project FY2010

OOI-CI & IOOS-DMAC Intersection Project FY2010. US Integrated Ocean Observing System (IOOS ® ). IOOS ® Plan defines: Global Component Coastal Component 17 Federal Agencies 11 Regional Associations . OOI Overview. OOI Scientific Investigation. Science Activity Model. (Mar 2011 end).

thuong
Download Presentation

OOI-CI & IOOS-DMAC Intersection Project FY2010

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. OOI-CI & IOOS-DMAC Intersection Project FY2010

  2. US Integrated Ocean Observing System (IOOS®) • IOOS® Plan defines: • Global Component • Coastal Component • 17 Federal Agencies • 11 Regional Associations

  3. OOI Overview

  4. OOI Scientific Investigation Science Activity Model (Mar 2011 end)

  5. The Problem • Each modeler has separate collection of scripts and procedures which are typically ad hoc, brittle and hard to maintain. • NCEP NAM: NOMADS/OPeNDAP =>NCO=>NetCDF • USGS Rivers: USGS/SOAP => XML • HFRADAR: Rutgers/OPeNDAP=>NetCDF • GTS CTD/XBT: AOML/Database query=>ASCII

  6. OOI Data Exchange

  7. Cloud Computing • Infrastructure as a Service • Compute Nodes • Storage • Present resources as infinite • Advantages • No capitalization of compute infrastructure • No operations of compute infrastructure • Very useful in development phase and during peak load • Easy to use, proven, quick turn around • Disadvantages • Higher costs during the operations phase • Reduced control of data, location, authority, security etc. • Existing Clouds • Commercial clouds: “Pay per use” and “allocation” model • Examples: Amazon EC2/EBS, Microsoft Azure, Google AppEngine etc.

  8. Data Flow Diagram

  9. Community Involvement Feedback on this plan Other data streams we should handle immediately? Plan to brief NFRA Modeling Committee regularly Wilkin (MARCOOS) has been identified as an ideal end-user modeler for participation (tech savvy, heavy data assimilation) We would like to add two others. Volunteers?

More Related