This page contains notification of changes to dataset creation (e.g. error corrections, calibration issues, and algorithm changes), and the impacted platform/instrument instances. The majority of this information can be found within the annotations entered into the Data Portal (OOINet) which can also be accessed via the API. If you have any questions, please contact the HelpDesk.
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.
* 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.
* 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.
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.
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).
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.
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.
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.
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.