ORION/OOI CYBERINFRASTRUCTURE

Transcription

1 ORION/OOI CYBERINFRASTRUCTURE

2

3 Cyberinfrastructure Cyberinfrastructure: : the coordinated aggregate of software, hardware and other technologies, as well as human expertise, required to support current and future discoveries in science and engineering. Fran Berman -SDSC ORION D&I Workshop 27 March 2006

4 MORE THAN HIGH-END COMPUTING AND CONNECTIVITY Focused on sharing and making greater capabilities available across the science and engineering research communities Allows applications to interoperate across institutions and disciplines Ensures that data and software acquired at great expense are preserved and easily available to all Empowers enhanced collaboration over distance and across disciplines. Report of the National Science Foundation Blue-Ribbon Advisory Panel on Cyberinfrastructure

5 In context of ORION/OOI: Support interactive measurement and integration of physical, chemical, biological, and geological phenomena across a range of inter-connected instrument networks. 3 types of observatories Many 10 s of instruments types Many 10 s of sites 1000 s of sensors Many 100 s of investigators For 10 s of years ORION D&I Workshop 27 March 2006

6 THE MREFC ACCOUNT The MREFC Account supports state-of of-the-art tools that are centralized in nature, integrate systems of leading- edge instruments, and/or shared-use networked infrastructure in advancing one or more fields of scientific study. Examples include accelerators, telescopes, research vessels, aircraft, earthquake simulators, networked high-tech research platforms, and advanced computing resources. advanced computing resources. To qualify for MREFC investment, networked infrastructure must exhibit systems characteristics greater than inferred simply by the connectivity of its parts. ORION D&I Workshop 27 March 2006

7 ORION CYBERINFRASTRUCTURE COMMITTEE DESIGN GROUP Ilkay Altintas UCSD Matthew Arrott UCSD Matthew Arrott UCSD Alan Chave WHOI Suzanne Carbotte LDEO John Graybeal MBARI Yi Chao JPL Eric Guillemot NEPTUNE CA Wu-chi Feng Portland State Ingolf Krueger UCSD John Graybeal MBARI Benoit Pirenne NEPTUNE CA Matt Howard NOAA PMEL Jason Leigh Univ. Illinois Andy Maffei John Orcutt WHOI OSC Liaison Larry Mayer Tom Palmatier UNH JHU/APL CI FORUM TUESDAY EVENING Benoit Pirenne NEPTUNE CA 8PM Grand Ballroom F ORION D&I Workshop 27 March 2006

8 ORION CYBERINFRASTRUCTURE Overarching Principles: the BILITIES Interoperability Scalability Extensibility Reliability Public Access ibility ORION D&I Workshop 27 March 2006

9 ORION CYBERINFRASTRUCTURE OVERARCHING STATEMENTS: There must be a centralized facility that takes responsibility for observatory operations The Common Operating Infrastructure

10 ORION CYBERINFRASTRUCTURE OVERARCHING STATEMENTS: There must be a focused authority that takes responsibility for observatory operations The Common Operating Infrastructure account management (what experiments are being done?) performance and fault monitoring (is it working the way it should?) governance and security policy (is it being used the way it should be?) resource management (what is available - including scheduling conflicts and real-time configuration changes?) workflow management (what is the most efficient way to operate the system?)

11 GOVERNANCE AND CYBER-SECURITY The Common Operating Infrastructure will establish a governance infrastructure that: controls access and registry for all services and data products includes, authorization authentication, auditing, and identity management including different levels of access to users with different levels of security addresses national security concerns ORION D&I Workshop 27 March 2006

12 RESOURCE MANAGEMENT The Common Operating Infrastructure will provide authority and ability to resolve scheduling conflicts and limited resource conflicts including: Tracking and allocation of resource usage A policy-based decision support system must be established including security -- they know how. but scientific community input will be required to establish appropriate policies

13 The Common Operating Infrastructure will support: DATA RETURN Near real-time data return from all observatories at designed network latencies (best available delivery cycle -- for global observatories add satellite latencies, for moorings add reporting latency) TWO-WAY WAY AND ON-DEMAND COMMUNICATIONS the ability to send commands for instrument control at designed network latencies es (best available delivery cycle -- for global observatories add satellite latencies, for moorings add command latency). INTERACTIVITY!!! ORION D&I Workshop 27 March 2006

14 INSTRUMENT TO INSTRUMENT COMMS: Peer-to-peer communications and networks of sensors need to account for fact that instruments may invoke activity of other instruments without human intervention (fleet of AUV s). What is going on in the terrestrial wireless world today will be ported to the seafloor over the next decade. (A.C.) ORION D&I Workshop 27 March 2006

15 DATA INGEST: All data collected under ORION/OOI will be acquired by, deposited in, and distributed from the ORION Data Repository -- most likely a distributed grid of storage devices. The Common Operating Infrastructure will be responsible for: 1- spatial and temporal indexing and registration with appropriate catalogue construction and provenance information (metadata) of all data sets as provided by PI or system). ORION D&I Workshop 27 March 2006

16 METADATA Metadata is an essential key to QA, data integration and analysis -- metadata that meets or exceeds national requirements (e.g., FGDC ) must be provided with all data. The Common Operating Infrastructure will specify interface and metadata requirements for output of domain specific products At a minimum this metadata must address data provenance, description, quality, maturity level (raw data streams, automated QC, processed, ed, derivative products), collection context, and support interoperability with other observatories, archives, and databases ORION D&I Workshop 27 March 2006

17 DATA INGEST: The Common Operating Infrastructure will: 2- Provide initial QA/QC tools for automated validation 3- Support of delayed mode QA/QC by instrument providors or others through notification and archive updates 4- Support of associated datasets which can (at the Observatory s discretion) be incorporated into The ORION Data Repository 5- Track multiple versions of data sets (version control) ORION D&I Workshop 27 March 2006

18 DATA DISTRIBUTION: A data distribution process that will provide: 1- a robust data archive mechanism 2- online access in accordance with ORION DATA POLICY and in a form that supports interoperability 3- both Query and Subscribe data distribution services ORION D&I Workshop 27 March 2006

19 ORION/OOI DATA POLICY The Ocean Observatory Initiative, by establishing an interactive, distributed and integrated network of ocean sensors and software, represents a fundamentally new approach to marine science that requires new policies regarding data access and distribution. Both the nature of the science to be addressed under OOI, and the auspices under which the data are collected, demand that OOI data be rapidly disseminated, open, and freely available (within constraints of national security). ORION D&I Workshop 27 March 2006

20 ORION/OOI DATA POLICY Rapidly disseminated implies that data will be made available as soon as technically feasible (i.e., there will be no delays in distribution for non-technical, non-security reasons). Open implies that data distribution will be unrestricted (unless for reasons of national security). Freely available means that data will be distributed without charge. There may be charges for the cost of reproduction and delivery unless access is obtained through the Internet

21 DATA INTEGRATION AND ANALYSIS: A basic set of applications that will: 1- provide efficient 4-D data discovery, integration, analysis, and visualization capability including semantic cross-referencing capabilities 2- facilitate data access in forms accessible via other data fusion systems, programmatic interfaces, and services (e.g., GIS, visualization, etc) 3- provide efficient interaction with other data, databases and MODELS e.g. IODP, OAPS, NGDC, CLASS, DAAC, ROMS

22 ORION Modeling Committee Lewis Rothstein (U. Rhode Island) - Chair John Allen (Oregon State U.) Fei Chai (U. Maine) Shuyi Chen (U. Miami) Bruce Cornuelle (Scripps) Katja Fennel (Rutgers) Pierre Lermusiaux (Harvard) Raghu Murtugudde (U. Maryland) Yvette Spitz (Oregon State U.) Cisco Werner (U. North Carolina)

23 Terms of Reference To help establish the role of each of a hierarchy of coupled numerical physical-biogeochemical ocean/atmosphere/geophysical models (including global, regional and coastal models) in the evolving plan for ocean observatories. Forward Models Ocean System Simulation Experiments (OSSEs) To provide advice on the current status of the different types of models required to achieve the objectives of the ORION program, and the primary issues or needs for development of those models. To explore ways in which the ocean modeling community should interface with the atmospheric and geophysical modeling community for achieving the objectives of the ORION program.

24 General Recommendations Foster a scientific approach where ocean observatories are fully integrated with ocean modeling for better understanding and predictions through: Dynamical interpolation and synthesis of multiple data sets Utilization of models to iteratively guide the sampling design and adaptive sampling plans (e.g. OSSEs) Evaluation and improvement of models, including error estimates

25 General Recommendations Utilize models within ORION to study, synthesize, discover and resolve (multi)-scale interactions, physicalbiogeochemical-ecological coupling and ocean/earth processes, e.g.: Quantify interactions among coastal and global scale, mesoscale and sub-mesoscale that are not directly observable Assess uncertain, or discover new, interdisciplinary ocean coupling Monitor, explain and better forecast climate dynamics, ecosystem evolution, and earthquakes

26 How to do it - General Encourage modeling proposals as integral part of ORION observatory and/or analysis RFPs Facilitate modeling evaluation, assessment and sharing of knowledge and skill levels between observatories Serve resource management needs by providing prediction capability for specific regions Foster collaborations among different universities, institutions, government agencies and modeling centers

27 How to do it - Operational Plan modeling continuity through the long life of ORION Support efficient & cooperative transition of methodologies & technologies among research & operational centers, involving universities, institutions and other agencies Preliminary proposal: Establish Modeling Centers for: Maintaining hierarchy Modeling of evolving Forum interdisciplinary models (e.g. from reduced process-oriented models to operational forecast systems) Wednesday 8:00PM Model repositories with support for writing modeling manuals, etc. Grand Ballroom F Archiving and disseminating model data sets Flexible formats for wide range of research endeavors Linking to other IOOS activities & operational centers (e.g. NCEP) Coordinating between the ORION research community and the Modeling Centers through: Visiting scientist and community postdoc programs Student workshops

28