R2R ~ a brief overview

1. Rolling Deck to Repository (R2R)~ a project update and open discussionCyndy ChandlerWoods Hole Oceanographic Institution 24 March 2009 Rolling Deck to Repository (R2R)

2. R2R ~ a brief overview • What is R2R? • Who’s involved? • When did it start? • Why?

3. R2R ~ what, when and who • Rolling Deck to Repository (R2R) one year pilot project funded in September 2008 by Jim Holik(Program Director, Div OcSci, NSF Oceanographic Centers and Facilities, OTIS) • develop UNOLS central data system (rvdata.us) that would interact with UNOLS ship scheduling information system (unols.org/strs) • basic idea is that people who are closest to point of data collection should be responsible for sending data to repository • Project Leads: • LDEO (Bob Arko) – fleet data system (UNOLS rvdata.us) • SIO (Steve Miller) – QC, provenance, controlled vocabularies • WHOI (Cyndy Chandler) – scientific sampling event log system

4. R2R ~ guiding principles • NSF supported research vessels produce an enormous volume and diversity of scientific data each year. R2R proposes a fundamental transformation of data management in the fleet, providing a “direct pipeline” for the routine underway data and documentation from each cruise to flow from the operating institution to a central shoreside repository. • Working directly with the ship scheduling offices and technicians will ensure more complete and consistent data acquisition, quality control, archival, and dissemination.

5. We envision the U.S. academic research fleet as an integrated ocean observing system - a network of ships and submersibles around the world that routinely report a standard suite of underway data and documentation to a central repository. An R2R enabled system will facilitate data discovery and integration, quality assessment, cruise planning, compliance with funding agency data policies, and long-term data preservation. R2R ~ sound bite

6. More on what is R2R? • R2R Goals: • reduce expanding # of custom data feeds required of each vessel • preservation of shipboard data • standardization of routine shipboard data products to enable common tool development • local implementations supported and encouraged, but final data products would be consistent across the fleet • UNOLS would publicize best practice recommendations for oceanographic research cruises • include near real-time contribution at end of each cruise: • Cruise metadata profile • Cruise report • Nav (cruise track) data • Cruise event Log

7. Which ‘underway’ data ? R2R proposes these “routine underway data types” to start

8. R2R ~ why? why now? • Why do we need R2R? What’s wrong with what we’re doing now with UNOLS vessel underway data? • data are being lost • NSF program manager expectations have changed with respect to data availability • new UNOLS office (May 2009) • data acquisition becoming more complex • procedures are different on every vessel

9. 21 Sep 2007 CLC WHOI UNOLS Vessels ~ ~ Data Flow WHOI UNOLS VESSELS R/V KNORR R/V OCEANUS R/V ATLANTIS Cruise Synopsis Cruise Track XBT CTD ADCP Underway: SST; Salinity; MET; Nav.; depth; 12/3.5? Khz Bathy ** other WHOI Data Archives Cruise metadata CD- or DVD-ROM contents ** Other Geological samples archived at WHOI Consider third-party tool usage – additional to or replacement for WHOI standard sampling QA/QC – sensor calibration as able and monitored w/in specs and acquiring data during cruise Other Science Instruments Web Siteswww.sssg.whoi.eduwww.whoi.edu S & TShipdata (Knorr, Oceanus, Atlantis, Tioga) - http://4dgeo.whoi.edu/shipdata/Alvin - http://4dgeo.whoi.edu/alvinJason - http://4dgeo.whoi.edu/jason marine.whoi.edu: Cruise Synopsis Database: now in Lotus, would be nice to be moved to Rick C. keeping it. Not easy to harvest b/c no programmatic web interface available. More complete meta data pulled directly off ships than what Maggie has. Ideally we would use Rick’s data and attach metadata to the file. 4D Geobrowser: Frame Grabber Cruise Synopsis becomes part of the cruise report…Chief Sci. no longer required to do that any more. CD-ROM DVD-ROM R/V ATLANTISSeafloor mapping 3.5Khz Bathy ____________________ HOV ALVIN ROV JASON, ABE/Sentry Video Imagery Digital Still Photos Sonar Vehicle navigation Rolling Deck to Repository (R2R)

10. R2R ~ progress update • cruise metadata schema developed • vessel profile schema developed • rvdata.us site created • data at rvdata.us from several operators • list of 16 ‘underway’ data types • prototype event logger (late May 2009)

11. The scientific sampling event log • A scientific sampling event log system is being developed at WHOI as part of the R2R pilot project. • What is a scientific sampling event log ? • a chronological record of all scientific sampling events that happened during a cruise, wherein each sampling event is assigned a unique identifier

12. R2R pilot project event log • test out some approaches to creating a digital file of shipboard sampling events • and making that file available after the cruise or earlier if advantageous and possible

13. some design considerations • review several systems already in use by ship operators • interface should be intuitive • system must be flexible; certain aspects should be easily customized by operator • information ‘entry’ should be automated where possible (from ship’s network) • system must scale – smaller coastal vessels to larger open ocean research vessels

14. a sampling event matrix VERTIGO project KM0414 ALOHA cruise sampling event matrix R/V Kilo Moana (University of Hawaii Marine Center)

15. controlled vocabulary generated automatically using some algorithm date, time and position from shipboard system shipboard sampling event log event date time time_L sta lon lat ev_type person activity 0212208 20020121 2208 1108 TEST -175.220 -53.572 CTD001 nd CTD001 0230442 20020123 0442 1742 0 -171.480 -55.398 CTD002 Wang CTD002 0231556 20020123 1556 0456 0 -171.583 -55.407 ZooTow Landry ZooplankTow 0232351 20020123 2351 1351 1 -171.521 -55.334 CTD003 nd CTD003 0240153 20020124 0153 1453 1 -171.490 -55.329 TM001 Wang TM001 0240356 20020124 0356 1656 1 -171.336 -55.314 CTD004 Bailey CTD004 0240745 20020124 0745 2045 1 -171.408 -55.335 Pump_Cast Andrews PumpCast01 0241133 20020124 1133 0033 1 -171.405 -55.324 TM002 Wang TM002 0241319 20020124 1319 0219 1 -171.384 -55.333 CTD005 Timothy CTD005 0241435 20020124 1435 0335 1 -171.385 -56.333 HPT Tanner HandPlankTow 0241520 20020124 1520 0420 1 -171.383 -55.337 TM003 Landry TM003

16. Event Logger prototype demo • A prototype event logger application is being developed by Alex Dorsk Operational Scientific Support Engineer Scientific Shipboard Support Group WHOI slides contributed by Alex Dorsk

17. Event Logger demo a Web-basedevent logging system Web-based application uses CGI perl and Javascript

18. The main screen has four primary components . Log Panel Search Panel Entry Launcher ActionsLauncher

19. Event logger ~ next steps • activation of additional features (e.g. search, other actions) • identification and adoption of controlled vocabularies and standards (ISO 8601) • adopt the syslog protocol (message send and receive) ‘system of systems’ • combine Event Logger with eLog • test out on a cruise (summer 2009)

20. Contact We are interested in receiving feedback and comments about the Event Logger and scientific event logs in general. Alex Dorsk Cyndy Chandler adorsk@whoi.edu cchandler@whoi.edu

21. R2R ~ next steps • Submit the full 3-5 year proposal(June 2009) • How does R2R fit in with other CyberInformatics programs at WHOI(Andy Maffei’s presentation) • How does R2R relate to existing shipboard data flow at WHOI? (Scott McCue’s presentation)

22. thank you . . . questions ? Photo by WHOI Photo by Michael Moore, WHOI