pCO2 Water

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

Dataset Reviews Last processed: 7/23/19, 5:29 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 313 126 0 0 4 190 1,407 7,200 12 / 1 Complete
2 recovered_host 365 347 0 15 1 2 4,039 7,200 12 / 2 1 Complete
Data Ranges Review Images

Test Notes

  1. missing: ['pressure']
  2. fail: data found in another stream (gaps: [1] days: [0])

Data Coverage

Deployment: 12
40%95%

Lat/Lon Differences (km)

Deployment: 12
1 0.00
2 9.790.00

System Annotations

Metadata Start Date End Date Comment
GS01SUMO-RID16-05-PCO2WB000
Method: telemetered
Stream: pco2w_abc_dcl_instrument
2/18/15, 4:06 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: 298 By: friedrich.knuth

GS01SUMO-RID16-05-PCO2WB000
Method: recovered_host
Stream: pco2w_abc_dcl_instrument_recovered
2/18/15, 4:06 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: 299 By: friedrich.knuth

GS01SUMO-RID16-05-PCO2WB000
2/18/15, 4:06 PM 12/27/15, 6:20 AM

Deployment 1: Recovered_instrument data not available for this deployment.

Id: 630 By: lgarzio

GS01SUMO
12/8/17, 7:00 PM 12/8/18, 11:42 PM

Deployment 3: *UPDATED 2020-04-28: This mooring was recovered 2018-12-09 which was a year later than originally intended. Some instruments were able to continue sampling for the extended deployment.* Recovery of the mooring was planned during the NBP 17-09 cruise (Nov - Dec 2017) but not completed due to adverse weather conditions. Recovery options are pending. Instruments that are still operational are likely reaching (or have surpassed) their deployment lifespan.

Id: 834 By: lgarzio

GS01SUMO-RID16-05-PCO2WB000
12/30/17, 7:00 PM 12/8/18, 11:42 PM

Deployment 3: The PCO2WB000 is known to have ceased sampling on 2017-12-31. No data are expected after this date. Root cause unknown.

Id: 2157 By: cdobson
Flag: not_operational Exclude: No

GS01SUMO-RID16
2/3/19, 1:00 PM 2/11/19, 7:00 AM

Deployment 4: The NSIF experienced power failure on 2/3/19 1800UTC and power was restored on 2/11/19 1200UTC. All NSIF instruments will have this gap in their telemetered data.

Id: 1577 By: cdobson

GS01SUMO-RID16-05-PCO2WB000
Method: telemetered
3/14/19, 8:00 PM 1/20/20, 5:01 AM

Deployment 4: Large data gap between 3/15/2019 and 5/16/2019 due to instrument failure. The instrument was switched to polling mode on 5/16/2019 which has resulted in successful logging.

Id: 1592 By: cdobson

Review Notes

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

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

By Lori Garzio, on 7/25/19

GS01SUMO-RID16-05-PCO2WB000
Deployment: 1

Recovered data from the instrument were not archived and are not available for this deployment.

By Lori Garzio, on 3/16/17
Redmine Issue #10635

GS01SUMO-RID16-05-PCO2WB000
Deployment: 1

Suspect data - 97% of the values for pco2_seawater are nans, fill values or outside of global ranges.

By Lori Garzio, on 7/25/19

GS01SUMO-RID16-05-PCO2WB000
Deployment: 2

There are no recovered_inst data available for download for this deployment. According to the ingest csv, the recovered_inst raw data files are available. These files should be ingested or the dataset should be annotated to explain why the recovered_inst data aren't available.

By Lori Garzio, on 7/25/19

GS01SUMO
Deployment: 3

Annotation ID 834 needs to be updated: "Deployment 3: Recovery of the mooring was planned during the NBP 17-09 cruise (Nov - Dec 2017) but not completed due to adverse weather conditions. Recovery options are pending. Instruments that are still operational are likely reaching (or have surpassed) their deployment lifespan."

By Lori Garzio, on 1/14/19

New Note