Top Banner
OOI-CI & IOOS-DMAC Intersection Project FY2010
12

OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

Dec 31, 2015

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

OOI-CI & IOOS-DMAC Intersection Project FY2010

Page 2: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

OOI Overview

Page 3: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

US Integrated Ocean Observing System (IOOS®)

IOOSIOOS®® Plan defines: Plan defines:

• Global ComponentGlobal Component• Coastal ComponentCoastal Component

17 Federal Agencies17 Federal Agencies 11 Regional Associations 11 Regional Associations

Page 4: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

Science Activity Model

Y 1 Y 2 Y 3 Y 4 Y 5

Release Cycle

R-1

R-2

R-3

R-4

R-5

Project Year

R-1

R-2

R-3

R-4

R-5

Data Distribution Network

Managed Instrument Network

OnDemand Measurement Processing

Integrated Modeling Network

Interactive Ocean Observatory

Construction Start

OOI Scientific Investigation

(Mar 2011 end)

Page 5: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

OOI Data Exchange

Page 6: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

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.

Page 7: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

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

Page 8: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

Data Flow Diagram

Page 9: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.
Page 10: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.
Page 11: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.
Page 12: OOI-CI & IOOS-DMAC Intersection Project FY2010. OOI Overview.

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?