Here is a list of changes and improvements made to OOI datasets. The listings indicate how data may or may not have been affected by any actions taken and the time frame involved. Posts cover a range of data improvements, from correction of discovered errors to tweaking of instrument calibrations to changes in algorithms.

We share this information to be totally transparent, so data users are able to make any needed adjustments to the use of OOI data. This information also can be found in annotations in the Data Portal. If you have any questions about how or if your data might be affected, please do not hesitate to contact the Help Desk.


Renaming Data Stream Parameters

UPDATED 2020-06-08: We are in the process of changing the names of data stream parameters to be more user-friendly and make the data you are looking for easier to find.  For example, the parameter “pressure_depth” has been renamed to simply “pressure.” This renaming process has started with pressure_depth, and will be ongoing in our attempt to improve access to OOI data for all users.  We will post data stream name changes as they occur here on the Data Updates page, as well as on the Data Portal.  Note that the renaming process only applies to data requests, and for now, only applies to “pressure_depth.


Axial HD Video Camera Issues (Updated 9/21)

There was an issue right after deployment of the HD Video Camera at Axial Seamount (2020-08-06 14:11 UTC) that prevented one of the lights from turning on during recording periods. That was resolved on 2020-08-07 at 02:12 UTC and both lights were working properly from then on. There was another post-deployment issue that caused frames to be dropped from the video feed. That was resolved by reinstalling the drivers and rebooting the Elemental server on 2020-08-19 at 22:59 UTC. Finally, a software issue beginning at 00:00 UTC on 2020-09-08 was preventing new runs from starting, although the recorder was still running independently of the camera scheduling script (creating blank videos). At 00:00 UTC on 2020-09-11 the camera started a new 15-minute run, and it began recording video normally. Blank videos will be removed from the raw data archive.

Updated 9/21: The video feed began showing distortions in part of the frame, indicating there may be a graphics card or other hardware issue. Work is ongoing to correct the issue and upgrade the hardware to prevent this from recurring.

Regional Cabled Array Notice: South Line Outage

UPDATED 2020-08-25: On 17 August 2020, at ~1824 hours PDT, the south cable line went offline due to an over-current event. Investigations into the source of the outage were initiated immediately. Following initial tests, on 20 August 2020, at ~1200 hours PDT, power was restored to Primary Node PN1A – the Slope Base site and all infrastructure at Slope Base is now operational, including the shallow and deep profilers.

On 22 August 2020, an inspection of ~10 km of the primary cable between Primary Nodes PN1B (~ 10 km south of Southern Hydrate Ridge) and PN1A was conducted to search for potential external aggression. The inspection identified no indications of external aggression.

On 25 August 2020, beginning ~ 0900 hours PDT, an ~ 1-day test of the south cable line began to help refine the fault localization. This required stopping data collection for the duration of the test at the Slope Base site. Data collection will begin again as soon as this test is completed.

Based on testing and troubleshooting to date, the entire south cable line will not be able to be restored past the Slope Base (PN1A) site without a system repair.

Corrections and Updates Issued for ADCP Bin Depths

UPDATED 2020-06-08:  Prior to mid-2019, bin depth information, i.e. the velocity measurement depths, contained in some Endurance Array (EA) processed ADCP data files were incorrect and bin depths were missing in inductively telemetered Pioneer and Global Array ADCP data files.

Problems existed on EA ADCPs installed on all shelf and offshore Near-Surface Instrument Frame (an instrumented cage suspended below a surface mooring) as well as the ADCPs installed on the Washington Shelf Surface Mooring (CE07SHSM) Multi-Function Node and the Oregon Shelf (CE02SHBP) Cabled Benthic Experiment Package. The bin depths were incorrectly calculated because no pressure sensor was installed on these sensors resulting in a pressure value of zero being passed to the bin depth algorithm. OOI corrected this issue by obtaining pressure data from a co-located CTD if the ADCP pressure data are zero. In addition, over the past year, pressure sensors have been installed on the above ADCPs as part of regular six-month sensor maintenance and refurbishment cycles.

ADCP sensors that use inductive modems to telemeter data to shore in near real-time do so using a reduced data output format called PD12. The PD12 format does not contain all the information required to calculate bin depths. This resulted in bin depths being omitted from processed data files. OOI has added the necessary metadata to these telemetered Pioneer and Global Array inductive ADCP data streams such that processed data files now contain bin depth data.

RCA Data Collection Restored

UPDATED 2020-06-01: The Regional Cable Array system is powered and data are being collected.

Temporary RCA Shutdown

UPDATED 2020-05-29: On 8 May 2020 at approximately 10:15 pm PDT, the Power Feed Equipment (PFE) at the shore station in Pacific City, OR shut down due to a critical alarm in the chill water system that provides cooling to the PFE. This resulted in the automatic protective shutdown of the primary power source for the Regional Cabled Array. As the cable lines are not powered, the RCA system is not currently collecting data. Repair and testing of the chill water system is currently in process to resolve the issue. Full restoration of the Primary and Secondary Nodes, instruments, and data loggers is anticipated to commence the week of 1 June 2020.

In-Water pCO2 (PCO2W) Data Interpolation Issue

Blank values (e.g. optical absorbance ratios in stream pco2w_b_sami_data_record_cal) are used to calculate the data product “pCO2 Seawater (µatm)” at a specific timestamp. A fix was applied on 2020-02-04 to ensure that any pCO2 data request will use a linearly interpolated value from the closest blanks if no blank value is found within the requested time range. This prevents the system from returning NaNs or empty datasets in those cases. Restrictions were also put in place to prevent interpolation across deployments, which could pull blanks from different instrument serial numbers, potentially creating bad data. These fixes apply to all pCO2 data, so all derived L1 pCO2 data products generated prior to this notification date should be re-requested in order to ensure utilization of the correct interpolation code.


Endurance Array Oregon Shelf Benthic Experiment Package CTD Conductivity Anomaly

* UPDATED, 2020-02-10: We observed an anomalous drop in conductivity values from this sensor (CE02SHBP-LJ01D-06-CTDBPN106) beginning in Dec. 2018. Scientific and technical analysis determined that it was likely related to a clogged conductivity cell. Power to the CTD pump was cycled on 2019-01-14, which appeared to resolve the issue and bring conductivity back into a reasonable range. A subsequent drop in conductivity values on 2019-01-18 resolved on 2019-01-23, and no further drops were not observed for the remainder of the deployment. Conductivity, salinity, density, and salinity-corrected DO data products from this sensor should be considered suspect between 2018-12-17 and 2019-01-23.

In-Water pCO2 (PCO2W) Data Quality issue (all Sunburst sensors):

* UPDATED, 2019-01-15: After careful review, the original data product algorithm (pco2_pco2wat) for this sensor was found to contain an error that resulted in calculation of incorrect derived L1 pCO2 values. In consultation with the vendor, the algorithm has been corrected, and is in the process of being verified. Once complete, this notification will be updated, and all derived L1 pCO2 data products generated prior to the notification date should be re-requested in order to ensure utilization of the correct algorithm. The updated algorithm can be viewed here.


Cabled Array outages (2018-08-22 to 2018-08-24, and up to 2018-09-05 in some cases)

The entire Cabled Array was offline due to the automatic protective shutdown of primary power to the OOI Cabled Array during installation of a new chiller system on August 22nd, 2018. The chiller installation was completed on September 5th. Both new units are fully functional, and the deployed infrastructure is now powered and collecting data. During the installation, data could not be collected.

In a separate issue, there was a Low Voltage Node (LV01A) communication issue that prevented connecting to the node, and the connected Shallow and Deep Profilers. However, communications were successfully established on September 5th in coordination with the cable vendor. The DP vehicle has been confirmed to be in the dock, is currently in the process of charging, and will be released to resume sampling upon full charge.

Telemetered Direct Covariance Flux (FDCHP) Data Quality issue (2015-02-18 16:06:00 to Present):

The telemetered FDCHP data contains an onboard processing error that makes the motion-corrected wind speed and flux data unusable. The instrument subject matter expert is being consulted, and the algorithms are under review. Only the processed, recovered data should be used. This impacts instruments on the Endurance Oregon Shelf Surface Mooring (CE02SHSM), the Pioneer Central Surface Mooring (CP01CNSM), the Global Irminger Sea Surface Mooring (GI01SUMO), and the Global Southern Ocean Surface Mooring (GS01SUMO).


Data Ingest Issue

View info

Friday 8 December 2017 at 1:30 PM ET an error occurred that prevented the OOI Cyberinfrastructure (CI) system from loading new live data. On Monday 11 December 2017 the issue was fixed; no data were lost.

Endurance Array Oregon Offshore Cabled Shallow Profiler Mooring Disabled:

View Info

On 16 September 2017 the  Endurance Array Oregon Offshore Cabled Shallow Profiler Mooring was accidentally pulled off position and apparently damaged by fishing trawler gear. Communications to shore ceased. Subsequent survey efforts located the damaged infrastructure and the mooring’s science pod has been recovered. Planning is underway to recover the mooring. Portions of the damaged mooring remain suspended. The USCG has been notified and a navigation hazard warning is included in the weekly USCG District 13 Local Notice to Mariners. The Cabled Shallow Profiler Mooring at the Oregon Offshore site will be replaced during the Cabled Array maintenance cruise in Summer 2018. We will post additional updates if there are any significant changes to this status. The co-located Surface Mooring, Cabled Deep Profiler Mooring, Benthic Experiment Package, and CAMDS at the Oregon Offshore site continue to transmit data.

Irminger Sea Surface Mooring Stopped Communications:

View info

At 1003 UTC, Thursday morning, 12 October, 2017, the Surface Buoy on the OOI Global Irminger Sea Array Surface Mooring stopped all communications. There is no indication as to what may have caused the outage, and the current state of the buoy and mooring infrastructure is not known. All systems were operating normally prior to the event with no indications of a problem aboard the Buoy. Sea conditions during that time were light to moderate seas with some swell and cloudy skies. Visual survey of the area by a ship of opportunity in the vicinity did not discover any new information.


Oxygen Sensor Calibration Issue:

View info

A data anomaly came to our attention regarding some of the OOI oxygen data (DOSTA). After investigating this anomaly, the OOI Data and MIO Teams were able to diagnose a data issue and establish key action steps. Many of the currently deployed Aanderaa optode oxygen sensors (see specific list at link above) had an error during the manufacturer’s calibration of the instruments. Incorrect offset values are causing the OOI algorithm to report processed O2 values an order of magnitude higher than expected. Note that due to the source of the error, the raw data reported from these sensors has not been affected. As such, correct O2 values can likely still be calculated from raw phase & temperature data, and this error should not ultimately lead to a gap in overall O2 data. The OOI Data Team informed users of the issue, and removed the erroneous calibration values to keep the system from continuing to produce incorrectly derived O2 products. In the medium term, the Data Team will use a back-calculation from the phase data to try to replace the calibration values. The data team will keep a careful record of what was done and add that information to the annotations and the website.