Introductions and OOI Overview

1. Introductions andOOI Overview

2. OOI Overarching Objectives • The design requirements of the OOI lead to three essential objectives: • Sustain, for decades, the delivery of multiple streams of ocean data, resolving ocean processes and properties across a range of temporal and spatial scales; • Facilitate the use of the designed capabilities of the OOI for specific at-sea experiments or extension of the temporal and spatial reach of ocean research; • Sustain the expansion capabilities of the observatory as technology evolves and in response to new science questions. 2

3. The Reality of the OOI Status and Gaps Recovering from a major internal readjustment of core software development, coding of instrument and data set drivers, algorithm implementation, and development of the user interface. Has delayed a full description of the operational situation of data management of the OOI

4. Project Scope Overview

5. Organization Breakdown Structure Ocean Leadership Program Management, Integration engineering, Leadership and oversight Direct CI management Cyberinfrastructure IO (Subawardee) University of California, San Diego Coastal/Global IO (Subawardee) Woods Hole Oceanographic Institution Endurance Array IO (Subawardee) Oregon State University Regional IO (Subawardee) University of Washington Education IO (Subawardee) Rutgers University

6. Scope Defined as Discrete Requirements • Science Themes • high level science theme for the OOI program • Science Questions • Top level science drivers, derived from the L1 Science Themes • Science Requirements • specific requirements detailing the types of measurements, their locations, their accuracies, necessary to answer the science questions • System Requirements • detailed for the infrastructure by system • L3-CG-RQ-573 Pioneer surface moorings shall measure the Partial Pressure of Carbon Dioxide (pCO2) of surface water • Subsystem Requirements • detailed for sub-systems and instruments • L4-CG-IP-RQ-203 pCO2 instruments shall be capable of sampling intervals of no less than one time per hour. ~5500 total requirements across all levels

7. OOI Science Requires Resolution of High Frequency Forcing (minutes-hours) In Distant and/or Extreme Environments for Sustained Periods (years-decades) Four Global high latitude sites Station Papa Irminger Sea Argentine Basin Southern Ocean Two Coastal Arrays Endurance Array Pioneer Array Cabled Array Meso-scale, Plate Scale network The locations and type of infrastructure drive engineering design, deployment, and maintenance profiles

8. Project Scope – Coastal/Pioneer Array • DCN 1600-00004 – Pioneer Array • Three EM surface moorings (B, E, H) • Three Multi-Function Nodes at the base of EM surface moorings (two supporting AUV docks) • Five coastal wire-following profilers • (C, F, G, I, J) • Two coastal surface-piercing profilers • (A, D) • Two AUV docking stations (B, H) • Two AUVs • Six gliders • 24 instrument classes • 157 total instruments

9. Project Scope – Coastal/Endurance Array • Washington Line – 90 instruments • Two EM surface moorings with wind, photovoltaic and fuel cell power generation, high speed and low speed satellite communications, and meteorological sensors (80, 600 m) • One EM surface mooring with battery power and Iridium satellite communications (25 m) • Two bottom-mounted, surface-piercing profilers (25m and 80m) with acoustic communications to the surface buoy • One wire-following profiler mooring at 600 m • Three benthic multifunction nodes (MFN) at 25m, 80m and 600m with sensors, comms to the surface • Six gliders across the Endurance Array • DCN 1600-00002 – Endurance Array • Oregon Line –131 instruments • Two surface moorings with wind and photovoltaic power generation, sat comms, and met sensors (80, 600 m) • One 25m surface mooring with battery power, sat comms • Two bottom-mounted surface-piercing profiler moorings • One hybrid profiler mooring with deep profiler and shallow profiler cabled to RSN (600 m) • One uncabled benthic multifunction node (MFN) at 25m with sensors, commsto the surface • Two cabled benthic experiment packages (BEP) with fiber optic communications and power via cabled nodes

10. Project Scope – Global Arrays DCN 1600-00001 Argentine Basin DCN 1600-00003 Irminger Sea DCN 1600-00005 Southern Ocean DCN 1600-00006 Station Papa *Station Papa does not contain Surface Mooring • One acoustically-linked Global Surface Mooring*, with high-power buoy and high-bandwidth (active antenna) satellite telemetry • One Global Hybrid Profiler mooring with up to two wire-following profiler operating and one surface-piercing profiler • Two subsurface Mesoscale Flanking Moorings with fixed sensors and acoustic communications to gliders • Three gliders with extended endurance and acoustic communications to the Mesoscale Flanking Moorings • 19 Instrument Classes • 80 Instruments - Southern Ocean, Argentine Basin • 76 Instruments – Irminger Sea • 57 Instruments - Station Papa

11. Project Scope – Regional Scale Nodes • DCN 4501-00001 and DCN 4500-00001 • Shore Station • Axial Seamount/Hydrate Ridge • Paired Deep and Shallow Profiler Moorings • Extension cables to multiple sites and Endurance Array • LP J-Boxes • MP J-Boxes • Seafloor Instruments • 34 Instrument Classes • 100 Total Instruments

12. Project Scope – Education & Public Engagement • EPE is constructing an integrated suite of software tools and a web portal that enable scientists and educators to enhance undergraduate education (primary) and engage the general public (secondary) using real-time OOI data. Specifically the EPE will provide: • aweb portal enabling virtual collaboration and sharing of materials, • enhanced software for the creation of concept maps that translate science concepts into education material, • integration of a suite of educational data visualization tools, • and step by step guidance on the best practices for developing educational labs & lessons with a real-time data.

13. Data Management

14. OOIN High Level Network Design Adjustments under consideration – to be finalized by fall 2014

15. Release Plan, 2014 February March April May June July August Driver & Algorithm Development Dates subject to revision when performance metrics become available MIP Steps 1 - 4 31 30 Regional Scale Node (29 drivers) 25 Station Papa (13 drivers) 25 Coastal Gliders (6 drivers) 18 14 Pioneer (9 drivers) Integration, Deployment, and Release MIP Step 5 14 2 Release 2.3 31 8 Release 2.2 (3 Drvrs) 31 25 Release 2.2.1 (9 Drvrs) Deployment Cruise Dates 10 16 Station PAPA Endurance WFP 11 13 Pioneer WFP RSN 1 Coastal Gliders OOINET Release 3 Scope to Complete • Release 3.0 (Beta 2) • STC (beta) • UX Screens • Marine Int. • Release 3.0 (Final) • Defect Corrections • PRR Build • Release 3.0 (Beta1) • STC (alpha) • UX Screens • Marine Int. • Release 3.0 (Beta 3) • STC (beta) • UX Screens • Marine Int. PRR July 16 27 25 31 17 21 PRR

16. DATA FLOW • OOI PURPOSE- • Deliver data and products to users and permanent storage • BASIC APPROACH- • Acquire and store measurements from sensors • Make high quality data and products available to all; open access • Provide them quickly (many in near-real time) 15

17. USERS ENTER HERE 16

18. OOINET Data Ingestion From Iridium downlink or recovery • Cyber Pop Post Recovery • OOINET pydap Postgress ERDDAPServer Postgress Glider Platform Separate Data Files Glider • Temp • Press. • Lat./Lon • Etc. Files : Disk Storage Hard Disk Storage Meta-Data data data data OMC OOINET CORE Algorithms UI Server MIO File Server Dataset AgentDriver DatasetAgent Instrument data is now stored in separate files on a hard disk, and Metadata is stored in the Postgress Database Local Storage rsync Local Storage CI File Server

19. OOINET Data Service to Users • Cyber Pop • User Space ERDDAP Website (Browser) • OOINET pydap Postgress ERDDAPServer Files : Disk Storage Algorithms user data user req. Meta-Data Meta-Data user req. User Request OOINET Website (Browser) OOINET CORE UI Server ION Services Drivers Agents Local Storage CI File Server

20. Data Product Levels • Level 0 (L0) • Unprocessed data: Data that are in instrument/sensor units and at instrument/sensor resolution. They are sensor by sensor (unpacked and/or de-interleaved) and are available in OOI supported formats (e.g., NetCDF). • the driver for each instrument will parse the strings from each instrument into uncalibratedsensor values. For example, a voltage reading from a sensor. • Level 1 (L1) • Basic Data: data that have been calibrated, are in well-defined scientific units, and may have some QC applied. • For example, a temperature in degrees C • Level 2 (L2) • Derived Data Products: Data that have been manipulated and/or combined and include new values not present in original data. • For example, salinity derived from conductivity measurements.

21. OOINet

22. Coastal Pioneer Upstream Inshore WFP FLORT-K (fluorometer on wire-following profiler)

23. Summary • Delays in CI code development has put Data Management behind schedule, recovery still underway • led to a revision of final capabilities • moved driver, data agent, algorithm work • moved user interface work • Marine Deployments revealing gaps in functionality and process • Lack of O&M procedures • Inaccuracies in ICDs • Coding errors in drivers, agents, UI, and algorithms • Database performance, now improving

24. Summary Construction is still in progress, follow on presentations detail how we shift focus from building infrastructure to delivering data