pCO2 Water

Reference Designator
GI01SUMO-RID16-05-PCO2WB000
Review Status
Review Complete
Note
Depth
12m
Class
PCO2W (pCO2 Water)
Make / Model
Sunburst / SAMI-pCO2

Dataset Reviews Last processed: 6/17/19, 5:05 PM

QC Check Info
Dep. Preferred Method Stream DD FD SG EG Gaps GD TS Rate (s) Pressure Comp. Time Order Valid Data Missing Data Data Comp. Missing Coords. Review
1 recovered_host 347 198 0 148 0 0 2,255 7,501 12 / 1 2 Complete
2 recovered_host / Complete
3 recovered_host 401 8 0 392 0 0 84 7,199 12 / 2 Complete
4 telemetered 314 69 0 245 0 0 792 7,199 12 / 3 3 2 Complete
Data Ranges Review Images

Test Notes

  1. fail: data found in another stream (gaps: [1] days: [21])
  2. missing: ['pressure']
  3. no other streams for comparison

Data Coverage

Deployment: 1234
22%
57%2%

Lat/Lon Differences (km)

Deployment: 1234
1 0.00
3 0.370.00
4 1.391.390.00

Example Composite Data Plot

System Annotations

Metadata Start Date End Date Comment
GI01SUMO-RID16-05-PCO2WB000
Method: telemetered
Stream: pco2w_abc_dcl_instrument
9/10/14, 2:50 PM 1/9/19, 7:00 PM

* UPDATED, 2019-01-25: 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, verified, and uploaded to the OOI system. This update, effective 2019-01-10, applies to all deployments for this sensor. All derived L1
pCO2 data products generated prior to this date should be re-requested in order to ensure utilization of the correct algorithm. The updated algorithm can be viewed at https://github.com/oceanobservatories/ion-functions/blob/master/ion_functions/data/co2_functions.py. * Until further notice, derived L1 pCO2 data products from this sensor are incorrect and should not be used. A significant discrepancy has been uncovered between the pCO2 values from shipboard water samples vs. values calculated by OOI system. The pco2_pco2wat algorithm is under review and can be viewed at https://github.com/ooici/ion-functions/blob/master/ion_functions/data/co2_functions.py. To receive instant notification of updates to the code, add yourself as a watcher to the GitHub repository linked above. For further questions please email help@oceanobservatories.org.

Id: 284 By: friedrich.knuth

GI01SUMO-RID16-05-PCO2WB000
Method: recovered_host
Stream: pco2w_abc_dcl_instrument_recovered
9/10/14, 2:50 PM 1/9/19, 7:00 PM

* UPDATED, 2019-01-25: 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, verified, and uploaded to the OOI system. This update, effective 2019-01-10, applies to all deployments for this sensor. All derived L1
pCO2 data products generated prior to this date should be re-requested in order to ensure utilization of the correct algorithm. The updated algorithm can be viewed at https://github.com/oceanobservatories/ion-functions/blob/master/ion_functions/data/co2_functions.py. * Until further notice, derived L1 pCO2 data products from this sensor are incorrect and should not be used. A significant discrepancy has been uncovered between the pCO2 values from shipboard water samples vs. values calculated by OOI system. The pco2_pco2wat algorithm is under review and can be viewed at https://github.com/ooici/ion-functions/blob/master/ion_functions/data/co2_functions.py. To receive instant notification of updates to the code, add yourself as a watcher to the GitHub repository linked above. For further questions please email help@oceanobservatories.org.

Id: 308 By: friedrich.knuth

GI01SUMO-RID16-05-PCO2WB000
9/10/14, 2:50 PM 8/22/15, 7:00 AM

Deployment 1: Recovered_instrument data not available for this deployment.

Id: 622 By: lgarzio

GI01SUMO
2/14/15, 7:00 PM 8/21/15, 8:00 PM

Deployment 1: Status data sent from the buoy included leak detects in the buoy well, drop in battery voltage, and loss of wind turbine input. Upon recovery, the buoy was primarily intact but several instruments were damaged and/or missing. Ice build-up on the tower is speculated to be the cause for much of the damage. No telemetered or recovered_host data expected. Functional instruments could continue to collect data using internal battery power and storage cards.

Id: 46 By: lgarzio

GI01SUMO
1/26/16, 7:00 PM 7/18/16, 8:00 PM

Deployment 2: A period of violent weather caused power outages on multiple instruments. No telemetered or recovered_host data expected. Functional instruments could continue to collect data using internal battery power and storage cards. Upon recovery, the buoy well was flooded.

Id: 47 By: lgarzio

GI01SUMO-RID16-05-PCO2WB000
7/18/16, 12:00 AM 8/14/17, 5:33 AM

Deployment 3: Instrument failed likely due to depleted batteries.

Id: 706 By: lgarzio
Flag: not_operational Exclude: No

GI01SUMO
12/26/16, 7:00 PM 4/6/17, 8:00 PM

Deployment 3: Wind turbines were disabled due to evidence of ice build-up on the surface buoy tower. The platform's battery charge state declined steadily. As of 2017-01-15, all DCLs were shut down and the telemetry schedule was reduced to conserve power. Battery-powered instruments should continue to collect data. UPDATE 2017-04-07: With increasing daylight at this location, sufficient power was generated by solar panels to re-establish limited high-bandwidth telemetry and data transmission. UPDATE: at recovery, wind turbines were missing their hubs and blades, and one solar panel was missing.

Id: 121 By: lgarzio

GI01SUMO
8/5/17, 2:17 PM 6/14/18, 4:02 AM

Deployment 4: at 10:03 UTC on 12 October 2017 the Irminger Sea Surface Mooring stopped all communications. At recovery, the surface buoy was missing. The subsurface portion of the mooring had fallen to the seafloor and was recovered. CTDMOs, CTDBP-F, DOSTA, and ADCP instrumentation were full ocean depth rated and survived, although any recovered data available after 2017-10-12T10:03:00 are suspect. All other instrumentation imploded or flooded. The cause for the loss of the buoy is inconclusive.

Id: 102 By: lgarzio

GI01SUMO
6/19/19, 8:00 PM

Deployment 5: Battery voltage dropped below 24V. All DCLs were turned off. CPM1 was placed on a wake schedule. Data collection and telemetry will be irregular until voltage rebounds.

Id: 1625 By: cdobson

GI01SUMO
Method: telemetered
10/21/19, 8:00 PM

Deployment 6: *UPDATED 2020-04-27: As of 2020-02-21 data for most instruments are being telemetered again (via Iridium). A gap in telemetered data is expected between 2019-10-22 and 2020-02-21 and will not be backfilled but these data will be available upon recovery.*Both fleet broadband units have failed and no more telemetered data is expected at this time. Instruments are believed to be operating as normal and their data will be available upon recovery.

Id: 1743 By: cdobson

Review Notes

Metadata Start Date End Date Comment
GI01SUMO-RID16-05-PCO2WB000

There is no pressure variable in the .nc files - this should be a coordinate.

By Lori Garzio, on 6/18/19

GI01SUMO-RID16-05-PCO2WB000

There are no recovered_inst data available for download from any deployment. According to the ingest csv, recovered_inst data should be available for deployments 2 and 3.

By Lori Garzio, on 6/18/19

GI01SUMO-RID16-05-PCO2WB000
Deployment: 1
9/10/14, 6:50 PM 8/22/15, 11:00 AM

The majority of the pco2_seawater data for deployment 1 are nans or outside of global ranges. This dataset should be annotated if there was a known issue with the instrument. Excluding from final data ranges.

By Lori Garzio, on 6/18/19

GI01SUMO-RID16-05-PCO2WB000
Deployment: 2

There are no data available for download from deployment 2 - according to the ingest csv, there are recovered_host and recovered_inst raw data files. These should be ingested or the dataset should be annotated to indicate why the data aren't available.

By Lori Garzio, on 6/18/19

GI01SUMO
Deployment: 4
10/12/17, 12:00 AM 6/14/18, 8:02 AM

The surface buoy detached from the mooring and the subsurface portion of the mooring fell to the seafloor (see annotation ID 102). Excluding all mooring data for this time range from final statistics.

By Lori Garzio, on 1/15/19

New Note