Community Tools and Datasets

Here, we have compiled tools that community members have built to access, analyze, and visualize datasets. We hope you find them helpful in advancing your efforts to use OOI data in your work.

Should you have a tool or dataset to share, please contact the HelpDesk. We will get it posted right away so others can benefit from your work and, perhaps, foster collaborative efforts.

Data Status and Data Visualization Tools

Near Real-time CTD Data from Irminger 8 Cruise (August 2021)

In August, members of the OOI team aboard the R/V Neil Armstrong for the eighth turn of the Global Irminger Sea Array and members of OSNAP (Overturning in the Subpolar North Atlantic Program) onshore are making near-real time shipboard CTD data available here.

Onshore expert hydrographer, Leah McRaven (PO WHOI) from the US OSNAP team, is working with the shipboard team to support collection of an optimized hydrographic data product. A special feature of this collaboration is the near real-time sharing of OOI shipboard CTD data with the public. Interested parties will have access to the same CTD profiles that McRaven will be reviewing.

McRaven is sharing her reports here while the cruise is underway:

BLOGPOST #4 (September 13, 2021)

Another OOI cruise is in the books! Now that things have wrapped up and I’ve had a chance to dig into the data a bit more thoroughly, how did we do? In my previous post I reported that the Irminger 8 CTD data looked to be very promising, but I like to include one more step before recommending data to be used for science: carefully considering salinity bottle data.

Salinity bottle data can be used in many ways to support a particular scientific objective or research question. The two that I’ve become most familiar with are 1) to support the analysis of additional bottle samples (e.g. dissolved oxygen) and 2) to provide an additional assessment and calibration of the CTD conductivity sensors. Both applications are necessary when researchers require salinity values more accurate than what CTD sensors are able to provide. However, even if this is not required, it can help ensure that users receive data that are reasonably within manufacturer specifications.

I find it easiest to consider the GO-SHIP approach to bottle data first. Using ship-based hydrography, GO-SHIP provides approximately decadal resolution of the changes in inventories of heat, freshwater, carbon, oxygen, nutrients, and transient tracers, covering the ocean basins with global measurements of the highest required accuracy to detect these changes. For a program like this, 36 salinity samples are taken every CTD station in order to provide an extremely accurate and precise calibration for the CTD sensors. Interestingly, the Irminger OOI array is bracketed by three GO-SHIP repeat transects. While GO-SHIP provides invaluable measurements, drawing a large number of samples can be expensive and time consuming. Additionally, measurements occur on a decadal timescale, so there is a lot of the picture we miss.

One of the research programs that aims to provide a higher temporal and special resolution picture of the North Atlantic is OSNAP. This program has several scientific objectives, but generally aims to quantify intra-seasonal to interannual variability of the Atlantic Meridional Overturning Circulation(AMOC) in the subpolar Atlantic. This includes a focus on heat and freshwater fluxes, pathways of currents throughout the region, and air-sea interaction, all of which require highly calibrated data products. In order to accomplish this, PIs from the program need to be able to consistently merge their shipboard and moored data products for cohesive and accurate quantification of parameters. Because much of the variability being studied is so large, researchers do not necessarily need salinity accuracies at the level of GO-SHIP, but they do need to use salinity bottle samples to ensure that CTD casts are at the very least within manufacturer specifications.

In the end, no one approach to hydrographic sampling is necessarily better than another. What is important is the delicate balance of resources while at sea that best support the scientific objectives. For both OSNAP and OOI, where the primary work at sea is focused on servicing moorings, the resources for a GO-SHIP approach to sample bottle collection is simply not feasible. However, one very key feature of the OOI CTD data is that they are collected annually, while ONSAP data are collected every two years, and GO-SHIP data are collected every ten years. Hence, OOI is able to fill in some of the temporal data gaps in the region and greatly bolster many of the international programs working in the region.

This year OOI collaborated with numerous PIs and representatives from research programs that operate in the Irminger Sea region to produce a more optimized CTD and bottle sampling strategy that better complements goals similar to GO-SHIP, as well as several additional objectives from international programs, such as OSNAP. The goal of this updated plan was to provide OOI data end users and collaborators with data that are more appropriate for CTD, mooring, glider, and float instrumentation calibration purposes. In particular, the update included increased sampling of the deep ocean. Such data are critical in the Irminger Sea region due to the uniquely large variability of temperature, salinity, and chemical properties throughout the shallow and intermediate depths of the water column. Deeper CTD and bottle data will allow all end users to more carefully reference their scientific findings to more stable water masses and allow for better intercomparison with other available datasets, such as the available GO-SHIP and OSNAP data from the region.

The majority of methods that I use when considering salinity bottle data have been adapted from GO-SHIP and NOAA/PMEL. In particular, many of the cruises I work with, including OOI, often have far fewer bottle samples than recommended by GO-SHIP or PMEL methods. This isn’t necessarily bad, since we don’t need to achieve the same goals as those programs, however, great care in adapting methods does need to be considered (and I encourage you to reach out if this is something you have an interest in). So, with the improved OOI sampling scheme, what are the potential benefits to CTD data quality?

More strategically planned salinity bottle sample collection allows users to:

  • Decide if data from primary or secondary sensors are more physically consistent
  • Identify times when CTD contamination was not obvious
  • Assess manufacturer sensor calibrations
  • Potentially provide a post-cruise calibration

In the case of the Irminger 8 cruise, I see that all four uses of salinity bottle data are possible, which will make a lot of collaborators very happy! Starting with Figure 1, we can see a summary of CTD and bottle sample salinity differences as a function of pressure for both the primary and secondary sensors. As a rule of thumb, the average offset of these differences can be considered an estimate of sensor accuracy, and the spread, or standard deviation, can be considered an estimate of sensor precision. While the data have a fairly large spread to the eye, the standard deviations (indicated by the dashed lines) are placing the spread for each sensor within what we expect from the manufacturer precision. The striking result from this figure is that before using the bottle data to further calibrate the data, we see that the primary sensor had a higher accuracy than the secondary sensor. In going back to the Seabird Electronics calibration reports for the primary and secondary sensors (available via the OOI website), I noted that the calibrations for each sensor was a bit older than what we normally work with (last performed in May 2019). Additionally, the secondary sensor had a larger correction at its time of manufacturer calibration than the primary. This is corroborated by the differing sensor accuracies as determined by the bottle data. Lastly, while there are a few spurious differences shown, on average there doesn’t look to be any CTD and bottle differences due to factors other than expected calibration drifts.

Figure 1

In order to apply a calibration based on the bottle data to the CTD data, I first QC’d the bottle data and then followed methods described in the GO-SHIP manual. There are several sources of error that can contribute to incorrect salinity bottle values, ranging from poor sample collection technique to an accidental salt crystal dropping into a sample just before being run on a salinometer. This is why all methods of CTD calibration using bottle data stress the importance of using many bottle values in a statistical grouping. However, sometimes there are “fly-away” values that are so far gone they don’t contribute meaningful information to the statistics, and in those cases I simply disregard those values. As a reference, for the Irminger 8 cruise I threw out 9 of the ~125 salinity samples collected before proceeding with calibration methods. Note that within the methods described in the above documentation, systematics approaches are used to further control for outlier or “bad” bottle values.

Figure 2

Since the majority of CTD stations for OOI are performed close to one another (and consequently in similar water masses), I grouped all stations together to characterize sensor errors. The resulting fits produced primary and secondary sensor calibrations that allow for more meaningful comparison of data with other programs. Figure 2 shows how primary and secondary data compare before and after bottle calibrations have been applied. Post calibration, primary and secondary sensors now agree more closely in terms of their differences. Similarly, Figure 3 summarizes data before and after calibration in temperature-salinity space, providing visual context for the magnitude of bottle calibration. Many folks working with CTD data would say that this is a rather small adjustment!

Figure 3

Figure 4

However, Figure 4 shows a comparison of the bottle-calibrated OOI data with nearby OSNAP CTD profiles from 2020. The results here are extremely important as OSNAP currently has moorings deployed near the OOI array and the OOI CTD profiles provide a midway calibration point for the moored instrumentation that is currently deployed for two years. These midway calibration CTD casts are critical in providing information on moored sensor drift and biofouling in a region where there has been a slow freshening of deep water (colder than 2.5 ºC) throughout the duration of these programs. Quantifying the rate of freshening is one of the objectives that OSNAP focuses on, but it is nearly impossible without high-quality CTD data for comparison. Figure 4 demonstrates that the freshening trend has continued from 200 to 2021 and that the bottle-calibrated OOI CTD data will be critical for interpretation of moored data.

Finally, for those interested in the salinity-calibrated CTD dataset, please be in touch (lmcraven@whoi.edu). A more detailed summary of the calibration applied can be found in my CTD calibration report here.

BLOGPOST #3 (August 18, 2021)

Irminger 8 science operations are now fully underway, which means the stream of CTD data is coming in hot (actually the ocean temps are very cold)! So far, CTD stations 4 through 11 correspond to work performed near the Irminger OOI array location. I spent the weekend and past couple of days paying close attention to these initial stations. Here’s an update on how things look so far.

One of the concerns this year is that the R/V Neil Armstrong is using a new CTD unit and sensor suite (new to the ship, not purchased new). Any time a ship’s instrumentation setup changes, it’s a very good idea to keep a close eye on things as changes naturally mean there’s more room for human error. What better way to talk about this than to share my own mistakes in a public blog! When I first downloaded and processed the OOI Irmginer 8 (AR60) CTD data from near the Irminger OOI array location, I became very worried…

When I compared the Irminger 8 CTD data with three cruises from the same location last year, I was seeing very confusing and unphysical data in my plots. I was using Seabird CTD processing routines in the “SBE Data Processing” software (see https://www.seabird.com/software) that I had used for previous OOI Irminger cruises as a preliminary set of scripts, so I was confident that something strange with the CTD was going on. I immediately pinged folks on the ship to ask if there was anything that they could tell was strange on their side of things. Keep in mind, this OOI cruise focuses more on mooring work with only a handful of CTDs to support all additional hydrographic work, so any time there is a potential issue with the CTD data we want to address it as soon as possible. I started digging into things a bit more, and realized that I had made a mistake.

Within the SBE processing routines, there is a module called “Align CTD”. As stated in the software manual: “Align CTD aligns parameter data in time, relative to pressure. This ensures that calculations of salinity, dissolved oxygen concentration, and other parameters are made using measurements from the same parcel of water. Typically, Align CTD is used to align temperature, conductivity, and oxygen measurements relative to pressure.” When working in areas where temperature and salinity change rapidly with pressure (depth), this module can be very important (and I encourage you to read through its documentation). As you’ll see below, the OOI Irmginer Sea Array region can see some extremely impressive temperature and salinity gradients. This has to do with the introduction of very cold and very fresh waters from near the coast of Greenland, together with the complect oceanic circulation dynamics of the region. Based on data collected on the old CTD installed on the Armstrong, I had determined that advancing conductivity by 0.5 seconds produced a more physically meaningful trace of calculated salinity.

While 0.5 seconds doesn’t seem large, it’s important to remember that most shipboard CTD packages are lowered at the SBE-recommended speed of 1 meter/second. Depending on how suddenly properties change as the CTD is lowered through the water, this magnitude of adjustment may seriously mess things up if it’s not the correct adjustment. In the case of the CTD system currently installed on the Armstrong, I’m finding that very little adjustment to conductivity is needed. There are many reasons as to why this value will change – from CTD to CTD, cruise to cruise, and even throughout a long cruise. The major factor is the speed at which water flows through the CTD plumbing and sensors and how far the pressure, temperature, and conductivity sensors are from each other in the plumbed line. Water flow is controlled by many things including CTD pump performance, contamination in the CTD plumbing, kinks in the CTD pluming lines, etc. (for more information, start here: https://www.go-ship.org/Manual/McTaggart_et_al_CTD.pdf and here: file:///Users/leah/Downloads/manual-Seassoft_DataProcessing_7.26.8-3.pdf). Note that the SBE data processing manual provides great tips on how to choose values for the Align CTD module.

Below is a figure that summarizes impact on my processed data before and after my mistake. This is a fun figure as it compares CTD data from four cruises that all completed CTDs near the OOI site: the 2020 OSNAP Cape Farewell cruise (AR45), the 2020 OOI Irminger 7 cruise (AR46), a 2020 cruise on R/V Pelagia from the Netherlands Institute for Sea Research, and stations 5-7 of the 2021 OOI Irminger 8 cruise (AR60). I’m plotting the data in what is called temperature-salinity space. This allows scientists to consider water properties while being mindful of ocean density, which as mentioned in the last post, should always increase with depth. I include contours indicating temperature and salinity values that correspond to lines of constant density (in this case I am using potential density referenced to the surface). For data to be physically consistent, we expect that the CTD traces never loop back across any of the density contours. These figures are also incredibly useful as the previous three cruises in the region give us some understanding of what to expect from repeated measurements near the Irminger OOI array.

The plot on the left shows the data processed with a conductivity advance of 0.5 sec. As you can see, the CTD traces appear much noisier than the other datasets, and contain many crossings of the density contours (i.e., density inversions). The plot on the right shows data that are smoother and less problematic in terms of density. You may also note that in the right plot, the AR60 traces are a bit shifted to the left in salinity (i.e. fresher or lower salinity values) when compared to the other datasets. This is because I am plotting bottle-calibrated CTD data from the other three cruises. Just as I type this, I’ve been given word that the shipboard hydrographer has begun analyzing salinity water sample data for Irminger 8. These bottle data are critical for applying a final adjustment to CTD salinity data and I’ll talk more about this in a future post.

For now, I’m happy to report that the data look physically consistent! For completeness, I include the core CTD parameter difference plots from stations 4 through 11 (CTDs completed near the array thus far). CTD difference plots are described in my previous post. All checks out from where I am sitting so far. Thanks to the CTD watch standers and shipboard technicians for working so hard and taking good care of the system while the cruise is underway!

BLOGPOST #2 (August 10, 2021)

For this post I’d like to introduce some of the tools that folks can use to identify CTD issues and sensor health while at sea. Most of what I’ll be discussing here is specific to the SBE911 system that is commonly used on UNOLS vessels; however, a lot of these topics are relevant to other types of profiling CTD systems.

There are several end case users of CTD data within science. These include people who perform CTDs along a track and complete what we call a hydrographic section (useful in studying ocean currents and water masses); those who perform CTDs at the same location year after year to look for changes; people who use CTDs to calibrate instrumentation on other platforms (moorings, gliders, AUVs, etc.); and those who use the CTD to collect seawater for laboratory analysis (collected samples can be used to further analyze physical, chemical, biological, and even geological properties!). For each of these CTD uses, a core set of CTD parameters are needed.

Core CTD parameters include pressure, temperature, and conductivity. Conductivity is used together with pressure and temperature measurements to derive salinity. These three variables are needed to give users the critical information of depth and density in which water samples are collected, and support the calculation of additional variables. For example, ocean pressure, temperature, and salinity together with a voltage from an oxygen sensor are needed to derive a value for dissolved oxygen. In addition to core CTD parameters, it is very common to add dissolved oxygen, fluorescence, turbidity, and photosynthetically active radiation (PAR) sensors to a shipboard CTD unit. Each of these additional measurements have errors that must be propagated from the core CTD measurements – creating a rather complex system to navigate when trying to understand the final accuracy of a given measurement.

For each CTD data application, varying degrees of accuracy are needed from the measured CTD parameters to accomplish the scientific objective at hand… And this is where a lot of folks get into trouble! For a first example, consider someone who would like to calibrate a nitrate sensor that is deployed for a year on a mooring using water samples collected from the CTD. For a second example, consider someone who is interested in the changing dissolved oxygen content of deep Atlantic Meridional Overturning Circulation waters. In both cases, the core CTD parameters are critical. In the first example, this person needs to know the pressure and ocean density at the exact location their water samples are collected during a CTD cast so they can correctly associate analyzed water sample values with the correct position of the sensor on the mooring. However, in the second example, this person may need to use both salinity and oxygen samples to improve the accuracy and precision of CTD measurements so that their final data product will be sensitive enough to resolve small, but potentially critical, changes in the ocean.The most important take away here (CTD soapbox moment!) is that even if end users are not specifically interested in studying physical oceanographic parameters, they still need tools to verify that 1) the core CTD measurements are of high enough quality for use in their application and 2) that there are no unnecessary errors from the core measurements that are impacting their ability to address their scientific objective.

This is the first reason why I heavily encourage all CTD end users to become familiar not only with the accuracy of their particular measured parameter, but also the core CTD parameters. The second reason is that core CTD parameters are particularly useful in diagnosing early warning signs of CTD problems. Most shipboard systems install primary and secondary temperature and conductivity sensors on their CTDs, which provide an opportunity for in-situ sensor comparison. Additionally, calculated seawater density is particularly useful as it is one of the few properties we can make a strong assumption about – it should always increase with pressure. The density of seawater is determined by pressure, temperature, and salinity (conductivity), hence any time one or some of these recorded values is suspect, non-physical density “inversions” or “noise” may appear in the data record. 

Below are two figures that can be very helpful in diagnosing CTD problems. In these examples, I am using the Irminger 8 (AR60-01) deep test cast, which took place late Sunday evening, August 8th. Figure 1 shows difference plots of the two sensor pairs (temperature and conductivity). Each panel includes vertical dashed lines indicating expected manufacturer agreement ranges (see sensor specification sheets datasheet-04-Jun15.pdf and datasheet-03plus-May15.pdf). The values shown are, ±(2 x 0.001 ºC) and ±(2 x 0.003 mS/cm) for temperature and conductivity sensors, respectively (note that 0.003 mS/cm is close to 0.003 psu for reasonable temperature ranges). In general, sensor differences should fall within, or very close to, this range when calibrated by the manufacturer within the past year. The rule can be relaxed in the upper water column, however, differences between sensors deeper than approximately 500 m that consistently fall outside of this range indicate problematic sensor drift or contamination. Figure 2 shows the calculated seawater density profile using the primary sensors. Consistent density inversions larger than ~0.1 kg/m3 also indicate problematic sensor drift or contamination. When creating such figures, always look at the downcast and upcast (skipped here for the sake of brevity). The upcast will look a bit worse than the downcast (I encourage you to read about why), but those data are extremely important to anyone collecting water samples!

Figure 1 

   

 

Figure 2  

 

So, what can these plots tell us about the CTD system implemented on the Irminger 8 cruise so far? Figure 1 demonstrates an overall acceptable level of agreement between the sensor pairs. The particular sensors in use right now have calibrations older than one year, so this level of agreement is actually quite good. Figure 2 is also rather promising in showing a density profile that is continuously increasing. If you’re being picky (like me), you may notice that there are some small density inversions between roughly 200-500 m. After taking a closer look, I noted that the salinity profile indicates that there are some rather impressive salinity intrusions evident in the upper 500 meters (I encourage you to download data from cast 2 and verify!). This is normal for the Labrador Sea region where the cast took place (lots of melting ice nearby) and will naturally create a bit more “noise” in these plots. So, I’m not very concerned by this.

Now what do these plots look like when there’s a problem? There unfortunately isn’t one simple answer for this (I’ve been doing this for over ten years and am still learning subtle ways CTDs show problems!), but I’ll share two examples of when something was clearly wrong. The first example is from the Irminger 7 cruise (AR35-05). Figure 3 and Figure 4 show our two plots for stations 1-13 of the Irminger 7 cruise. Figure 3 shows a suspiciously large offset (well outside of the general threshold we expect in the conductivity differences) and incredibly noisy differences in both conductivity and temperature. Similarly, Figure 5 shows consistent and large density inversions for some of these casts. Several of the casts shown in Figures 4 and 5 were so bad that there are no usable profiles as far as scientific objectives are concerned. Luckily, however, there were a few casts in the set that could be corrected with water sample data (I’ll talk more about this later). Data loss is something that does happen while at sea, and the Irminger Sea in particular is an incredibly harsh environment to work in. However, if folks are diligent in creating these plots while at sea, the hope is that we can minimize time and data loss while striving for the highest quality data possible.

Figure 3   

 

Figure 4  

For my last example, I provide a quick reference guide for how core CTD parameter issues may look on a Seabird CTD Real-Time Data Acquisition Software (Seasave) screen. The reason for this is that a lot of people don’t have time to create fancy plots while at sea, so it’s helpful to know how to approach monitoring while watching the data come in. Follow the link here to download a one-page pdf that can be displayed next to your CTD acquisition computer.

BLOG POST #1 (August 2, 2021)

A CTD is performed near the coast of Greenland during one of the OSNAP 2020 cruises on R/V Armstrong. Photo: Isabela Le Bras©WHOI

Hello folks and welcome to the Irminger 8 CTD blog! As the cruise progresses, tune in here for updates on Irminger 8 CTD data quality as well as tips on how best to approach using OOI CTD data. I plan to keep this information inclusive for folks with varying levels of experience with shipboard CTD data – from beginner to expert! If you have any questions about CTD data, feel free to send me an email (lmcraven@whoi.edu) and I’ll do my best to help. For this first post, I would like to summarize some important resources available to the community that will greatly help with CTD data acquisition and processing.

CTDs have been around for a while, which on the surface makes them a bit less interesting than many of the new exciting technologies used at sea. The fact remains that the CTD produces some of the most accurate and reliable measurements of our ocean’s physical, chemical, and biological parameters. Aside from being very useful on their own, CTD data serve as a standard by which researchers can compare and validate sensor performance from other platforms: gliders, floats, moorings, etc. Sensor comparison is particularly important for instruments that are deployed in the ocean for a long time (as is the case for OOI assets) as it is normal for sensors to drift due to environmental exposure and biological activity. As it turns out, CTD data provide a backbone for all OOI objectives.

Leah McRaven helps to deploy a CTD during one of the OSNAP 2020 cruises on R/V Armstrong. Photo: Astrid Pacini, MIT/WHOI Joint Program

However, just because CTDs have been performed for decades, we can’t always assume that that collection of quality data is straightforward. For example, one of the unique challenges of collecting CTD data near the OOI Irminger site and Greenland region is that there is an elevated level of biological activity throughout the year. While biological activity is exciting for many researchers, it can clog instrument plumbing, build up on sensors, and just be plain annoying to watch out for. CTDs utilized in the Irminger Sea are also subject to extreme conditions such as cold windchills and rough sea state (Cape Farewell is actually the windiest place on the ocean’s surface!), leading to the potential for accelerated sensor drift and the need to send sensors back to manufacturers for more regular servicing and calibration. As one can imagine, there are a lot of potential sources of error when simply considering the environment that OOI Irminger CTD data are collected in.

To help combat some of these potential sources of error, I’ll be picking apart CTD and bottle data cast by cast to look for evidence of CTD problems during the Irminger 8 cruise. But before we can talk about unique sources of CTD data errors, it’s helpful to remember errors that can become systematic throughout the entire data arc: from instrument care, to acquisition, to data processing, and to final data application. Improving our awareness of these issues will allow all CTD data users the opportunity for more meaningful data interpretation. So before I move forward, I thought it would be important to share some of my favorite resources available on community-recommended CTD practices. I encourage folks to comb through these resources and find what might be most appropriate for your respective research objectives.

Recommended CTD resources are provided here.

View this tool

OOI Data Team Coastal and Global Array MATLAB Toolbox (2020)

This MATLAB toolbox is useful for downloading data via the Machine-to-Machine interface.

View this tool

OOI Data Team R M2M Toolbox (2020)

This is a helpful tool for using R for data explorations.

View this tool

OOI Data Team Python Toolbox (2020)

This is a helpful tool for using python for data explorations.

View this tool

OOI Data Team QC Database (2018)

This site provides status and data availability information on an instrument and data stream level, as well as a full list of platforms, nodes, streams, and parameters across all arrays. This site is a non-production prototype tool developed for internal use, so data are not guaranteed to be synced continually. Built by the OOI’s Data Team its purpose is to enable organized quality control testing.

View this tool
OOI Arrays
Front page of the Data Team QC Database

Python scripts made for QA/QC of OOI data that may also be useful to external users for downloading, organizing, and plotting data.

View this tool

Derived Datasets and Collaborations

OOI Data Tools on GitHub

Many in the OOI community use GitHub to work together to host and review code, manage projects, and build software together.  This is a good place to begin to integrate OOI data into your scientific investigations.

View this tool

OOIPY: A Python Toolbox

OOI community members Felix Schwock, John Ragland, Matthew Munson, and Shima Abadi created a Python toolobx design to aid in the scientific analysis of OOI data.  It allows users to access OOI broadband and low frequency hydrophone data, compute spectograms and power spectral density (PSD) estimates using the Bartlett/Welch method, and visualize spectrograms and PSD estimates.

View this tool

Seismometer and Hydrophone Data on IRIS

Data from the OOI broadband and short-period seismometers and low frequency hydrophones at Axial Seamount, Slope Base, and Southern Hydrate Ridge, and bottom pressure sensors in Axial caldera installed between July-October 2014 are available through the Incorporated Research Institutions for Seismology (IRIS). Data may be pulled hourly and are available in a variety of formats. While searching within IRIS for OOI data, use the two-letter IRIS network designator “OO.” Original announcement and more information can be found here.

View this tool

OOI Glider Data in the IOOS Glider DAC

OOI glider data are available through ERDAPP.  There it is easy to search by glider dataset. The site includes the capabilities of graphing and making tables and provides access to metadata.

View these data

OOI glider data also are a part of the Glider Data Assembly Center (DAC) resource collated by the Integrated Ocean Observing System (IOOS). As new gliders are deployed, the near real-time data are added to the DAC, while older glider data are available for download, and glider tracks can be visualized using the map viewer.

View these data

Cabled Array Tilt Meter, Co-located Temperature Plots, and Inflation Forecast

This site, courtesy of Bill Chadwick (Oregon State University/CIMRS), has been updated to add an inflation forecast created by Dr. Chadwick and Andy Lau (Oregon State University/CIMRS). These plots use OOI pressure data to extrapolate the average rate of inflation over the last 12 weeks and calculate the date when level of inflation at Axial Seamount will reach or exceed the pre-2015-eruption level. Note that the average rate of inflation changes with time, and reaching the threshold does not guarantee an eruption, but the volcano is likely to erupt within a year after reaching that threshold. The plots are automatically updated once a day using the latest inflation rate. (edited 05/16/18)

View this tool
Plot of OOI BPR data from the Caldera Center

Plot of OOI BPR data from the Caldera Center (BOTPT-A301-MJ03F; black curve) showing deflation during the 2015 eruption (left) followed by re-inflation. Blue dashed line extrapolates into the future using the average rate of inflation from the last 12 weeks; middle blue dot is date when 2015 inflation threshold is reached, right blue dot is when a threshold 30 cm higher will be reached. Plot courtesy Bill Chadwick (OSU/PMEL)

OOI High Definition Video Camera System (CAMHD) Python Module

This module, courtesy of Timothy Crone (Lamont-Doherty Earth Observatory), provides information about remote CamHD files, or can be used to retrieve individual still frames from these files, without having to download the entire file first. The module is still under development, which should be considered if using it to develop additional code, which also is actively encouraged.

View this tool

Broadband Hydrophone (HYDBB) Python Module

Use this module to convert audio MSEED files from the OOI hydrophones into FLAC or WAV format, filters the data, and creates spectrograms. The module is courtesy of Pete Cable (Raytheon).

View this tool

Axial Seamount Hydrothermal Vent Time-Lapse Videos

A new computer vision routine, developed by Aaron Marburg (University of Washington, Applied Physics Lab), aided by Timothy Crone (Lamont Doherty Earth Observatory), and Friedrich Knuth (Rutgers University), is able to correctly identify and tag scenes of scientific interest in the CAMHD video stream. These scenes were previously being manually identified by students at Rutgers University. A new set of time-lapse videos has been created with this enhanced metadata record, displaying one frame captured every three hours from November 2015 to July 2016. (edited 09/07/17)

View this tool

Axial Seamount and Coastal/Slope Biology Catalogs

Here you can view images and video of the many different organisms observed over the years of Regional Cabled Array expedition cruises. The first catalog relates to Axial Seamount, a deep-sea volcano on the Juan de Fuca spreading ridge, and the Coastal catalog contains animals seen at Hydrate Ridge, Slope Base, and Coastal Endurance cabled sites. These archives, compiled by students at the University of Washington under the guidance of Deborah Kelley (University of Washington) and Leslie Sautter, College of Charleston, are designed to be living documents, and will be continually updated to include information from future cruises and additional details provided by experts. (edited 08/29/18)

View Axial Seamount View Coastal/Slope

Axial Seamount Earthquake Catalog

This website, courtesy of William Wilcock (University of Washington) provides access to a near-real time catalog of earthquake detections and HYPOINVERSE locations for the Ocean Observatories Initiative cabled observatory at Axial Seamount. Support for this work comes from the National Science Foundation. (added 10/20/17)

View this tool

Need Help?

The HelpDesk is here to help you figure out and resolve any issues you may have in accessing and using OOI data.

Our first order of business is making sure that users and potential users of OOI data have their questions answered. Whether you are stymied by how to download pCO2 data, looking to ask about how to add instrumentation to an existing array, or wondering how OOI data undergoes quality control, help is but an email or phone call away.

Contact us at help@oceanobservatories.org. We promise to give you a timely response and will strive to answer any and all questions satisfactorily.