1. Ocean Observatories Initiative OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 Analysis and Synthesis (AS): Modeling 1 Designer: Yi Chao Architect: Michael Meisinger Product Manager: John Graybeal

2. OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 AS Modeling Tasks Users interviews Model survey Model descriptions Model catalog (implemented by CI) Modeling community engagement plan Model registration (by users) Model schematic (end-to-end) with example

3. OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 Users Interviews Planned: Interview at least one of the OOI IO groups (e.g., RSN, Endurance Array, CGSN) Accomplished: o Visited CGSN at WHOI on Nov. 19, 2012, and met with PIs (John Trowbridge, Bob Weller) and Project Scientist (Al Plueddemann) o Visited RSN at UW on Dec. 21, 2012, and met with PI (John Delaney), Associate Director for Science (Deb Kelley) and Project Scientist (Giora Proskurowski) 3

4. OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 Model Catalog: Global Systems 4

5. OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 Model Catalog: Regional Systems 5

6. OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 Modeling Community Engagement Plan (DRAFT) OOI o Reached out to CGSN at WHOI; RSN at UW o Need to reach out to CGSN at OSU; EPE at Rutgers Integrated Ocean Observing System (IOOS) o Central Office, Regional Associations National Operational Facilities o Navy, NOAA Community Models o HYCOM, ROMS, POM, FVCOM (unstructured grid) 6

7. OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 Model Registration (DRAFT) 7

8. OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 R3 & R4 Goals: OOI CI Modeling & On-Demand Modeling Service 8 External sources Feedback

9. OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 Example: HOPS/MSEAS to support MOOS-IVP in PP Software reads and displays any model output for MOOS-IVP o Provides ocean images on which vehicle simulations are superimposed o Snapshots or animations as appropriate o Provides ocean inputs to MOOS planning, or path plans themselves Acquires ocean model output through the Net o Format: NetCDF, Grib, binary, Matlab ©, etc. o Procedure: http, sftp, OpenDAP, scp, etc. o Can handle any model data (MSEAS, MIT-GCM, ROMS, NLOM, etc.) Displays ocean model data using Google Earth (what MOOS uses) o Calls Matlab ©, NCAR Graphics, or similar package to generate a set of images for the desired physical field(s) at desired depth and times o Uses ImageMagick or similar software to automatically crop images o Prepares KML file to display set of images as stills or animations For path planning with MOOS or with MSEAS software o Uses Matlab © or Octave to read model data (temp., salinity, velocity, etc.) and interpolates them at 4D vehicle locations for use by MOOS-IVP o Or provides path plans directly (computed from other MSEAS software) 9

10. OOI Cyberinfrastructure Life Cycle Objectives Review January 8-9, 2013 10 Temperature at 10 meters, with velocity vectors overlays Area is Pioneer Array vehicle sampling region Courtesy of the MIT group (Leslie, Haley and Lermusiaux) Example: HOPS/MSEAS to support MOOS-IVP in PP