ooi ci lca review august 2010 ocean observatories initiative external observatory integration...

OOI CI LCA REVIEW August 2010

Ocean Observatories Initiative

External Observatory Integration

Christopher Mueller, Matt Arrott, John Graybeal

Life Cycle Objectives ReviewLa Jolla, CA


Agenda

Life Cycle Objectives Review

• Strategy

• Subsystem Purpose

• Release 1 Product Description Use Case Overview

• Architectural Overview

• Status of Progress

• Use Cases Address, Use Cases Demonstrated

• Technology Challenges and Achievements

• Plan for Elaboration

• Significant Risks

2


OOI-CI – IOOS DMAC Strategy

• OOI Cyberinfrastructure (CI): a transformational integrated observing

infrastructure, providing a link between ocean research and discovery

• Integrated Ocean Observing System: a federal, regional, and private-sector

partnership working to enhance our ability to collect, deliver, and use ocean information

• IOOS Data Management and Communications (DMAC) Subsystem: a

subsystem capable of delivering real-time, delayed-mode, and historical data for in-situ

and remotely-sensed physical, chemical and biological observations, as well as, model-

generated outputs, including forecasts, to IOOS® users and of delivering all forms of

information to and from secure archive facilities.

(http://ioos.gov/library/dmac_implementation_2010.pdf)

• What is our strategy for aligning OOI and IOOS?

• "OOI is NSF's contribution to IOOS” (then)

• “One cyberinfrastructure (implementation) shared between two

organizations” (now) (now)

3


External Observatory Integration Subsystem: Purpose

1.Integrates external observatories (IOOS in R1)

with the OOI Integrated Observatory

2.Facilitates inclusion of external data

3.Delivers data in community specific forms

4.Allows immediate full scale testing of the OOI-CI

System

5.Introduces OOI to a community of early adopters

4


EOI R1 Product Description Use Case Overview

Responsible For

Supports

Uses

5


Architectural Overview – Client View

Researcher’s Process

OOI-CI ProcessApply CF conventions

LDM THREDDSCatalog

CDM

IDD

GTS

NOAA Port

NetCDFJava Library

Model Analysis

NDBC: Observing System Monitoring Center (OSMC)

UnidataOr NDBC

1 2

3 4

NCO & User Scripts

PU

LL

DAP & CF

Matlab(test CDM)

5

Navy/NASA/Other Model output

1A

2A

CI-DMAC_project_20100128.doc

OOI-CI & IOOS-DMAC Intersection Development Project-FY2010

*Improve the process by which researchers get data to drive models

6


Rutgers Modeling Process

https://docs.google.com/drawings/edit?id=1SldZ3cfzrR5wsimdsSt6f_lLMyKUquVDpUfNCt9ak2c&hl=en&authkey=CMe04JwM

7


2650-00007 OV2 CI

Architectural Overview – OOI-CI View

ApplicationServices

InfrastructureServices

8

IOOS


User Interfaces

Core Infrastructure Services

Architectural Overview – OOI-CI View

CommonOperating

Infrastructure

Data Distribution andPreservation Infrastructure

CommonExecution

Infrastructure

DataManagement

Application LevelServices

Externalization andIntegration

InstrumentAgents

External Observatory Integration

Sensing & Acquisition

9

IOOS


Status of Progress

• Established the Rutgers modeling team (John Wilkin)

as the initial scientific user group

• Started developing interaction patterns between

OOI-CI, IOOS, & Rutgers modeling team

• Compiled lists of data sources, outputs and

workflows required by the Rutgers modeling team

10


Status of Progress – List of Rutgers Data Sources

• Providers:

• PFEG, Rutgers, NAVY, USGS, RADS, NCEP, AOML

• Acquisition Protocols:

• OPeNDAP, curl, wget, urlread

• Prospective CDM Types:

• Grid, Station, Trajectory, Profile

• Data Variables:

• Sea Surface Height, Currents, Winds, Salinity, Temperature, River

Discharge, …

• Acquisition Forms:

• NetCDF, ASCII

11


Status of Progress – List of Rutgers Data Products

• Names:

• ROMS, 4DVAR Observational Files

• Distribution Protocol:

• OPeNDAP

• Prospective CDM Types:

• Grid, Station Collection

• Data Variables:

• Currents, Temperature, Salinity, Sea Surface Height, & Many

More…

• Output Forms:

• NetCDF

12


EOI Technology List

IDD/LDM

Matlab

NetCDF Java

13


Technology Challenges and Achievements

•Achievements:

•Functional prototypes of NetCDF DAP

translation in both JAVA & Python

•Challenges:

•Potential structural differences between DAP

objects generated by pyDAP and Java OPeNDAP

libraries

14


Plan for Elaboration: Derive Data Product Externally


15

Acquire data from OOI




16

Apply algorithm externally to generate new data




17

Make new data available to OOI


Plan for Elaboration

• Continue to work with selected scientific modeling groups and

• Register each data source as a Provider in the OOI-CI System

• Translation/transformation to achieve CDM/CF compliance

• Leverage IOOS data sources wherever possible

• Work with scientists to utilize the OOI-CI System for acquiring data

• Develop client-side tool that receives OOI-CI syndication

notifications to fetch data and start a science user process locally

• Register observational files and model output as products in OOI-CI

18


Risk Assessment – EOI

Use Case

ID Name Delivery Risk Maturity Level Target Use

UC.R1.21 Derive Data Product Externally (Merge Data) Low Required User

19


EOI Technologies at Risk for Release 1

None at this time!

20


Thanks !

Questions ?

21

ooi ci lca review august 2010 ocean observatories initiative external observatory integration...

Documents