pCO2 Water

Reference Designator
CE06ISSM-RID16-05-PCO2WB000
Review Status
Review Complete
Note
Data generally look suspect for many deployments because of the high percentage of values outside of global ranges - did not calculate final data ranges.
Depth
7m
Class
PCO2W (pCO2 Water)
Make / Model
Sunburst / SAMI-pCO2

Dataset Reviews Last processed: 7/23/19, 5:18 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 186 185 0 0 0 0 4,368 7 / 1 2 3 Complete
2 recovered_host 187 62 0 0 18 134 650 7 / 2 3 Complete
3 recovered_host 207 134 0 73 0 0 3,096 7 / 2 3 Complete
4 recovered_host 142 16 0 125 0 0 352 7 / 3 Complete
5 recovered_host 201 119 0 81 0 0 2,778 7 / 3 Complete
6 recovered_host 176 162 0 13 0 0 3,810 7 / 3 Complete
7 recovered_host 175 153 0 20 12 13 2,100 7 / 3 Complete
8 recovered_host 177 176 0 0 0 0 2,068 7 / 4 3 Complete
Data Ranges Review Images

Test Notes

  1. fail: data found in another stream (gaps: [4] days: [4])
  2. fail: check ['pCO2 Seawater']
  3. missing: ['pressure']
  4. fail: data found in another stream (gaps: [1] days: [1])

Data Coverage

Deployment: 12345678
99%33%65%11%59%92%87%99%

Lat/Lon Differences (km)

Deployment: 12345678
1 0.00
2 1.630.00
3 1.860.260.00
4 2.070.440.240.00
5 1.900.280.080.170.00
6 1.960.330.120.130.060.00
7 2.010.390.160.090.110.060.00
8 1.880.360.160.340.230.230.250.00

System Annotations

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

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, 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, and the algorithms are under review: 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: 273 By: friedrich.knuth

CE06ISSM-RID16-05-PCO2WB000
Method: recovered_host
Stream: pco2w_abc_dcl_instrument_recovered
10/7/14, 3:45 PM 1/9/19, 7:00 PM

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, 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, and the algorithms are under review: 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: 287 By: friedrich.knuth

CE06ISSM
10/7/14, 3:45 PM 9/30/16, 8:00 PM

All of the inshore surface moorings suffer from an issue called the 'top of the day problem.' A race condition exists in the CPM firmware when transferring daily log files harvested from the various sub-components in a buoy system (e.g. DCL16, CPM3, DCL35, etc) over the Iridium RUDICS connection. The primary CPM rsync's data files from the various sub-components to a central data directory. The first time a daily file is created/copied into that directory (usually shortly after midnight), a compressed copy of the file is created and that compressed file is queued up in a separate text file for transmission to shore. The transfer routine reads that text file and processes the files from that list in order from top to bottom. Once that compressed file is transferred to shore, no further updates for that file are sent to shore. Meanwhile, the CPM continues to rsync data from the different sub-components, updating the original daily log file. The net result is that data is accumulating in the daily log file for an instrument, but we may see only one record (or none) depending on when the rsync job occurred and the compressed file was created and staged for transfer to shore. This affects telemetered data only.

Id: 897 By: michaesm

CE06ISSM
7/26/16, 8:00 PM 10/3/16, 8:00 PM

Correcting the iridium data telemetry issues, permitting full telemetry of data files, resulting in greater power consumption than anticipated. Result is power level of the battery pack has dropped below operational limits and subsystems can no longer power instruments. Shutting the mooring down, and placing in a low power maintenance mode. 11 instruments offline.

Id: 898 By: michaesm
Flag: not_operational Exclude: No

CE06ISSM
12/31/16, 7:00 PM 4/22/17, 8:00 PM

The buoy main battery voltage is being drawn down faster than expected. Have shutdown further power to DCL17 and to the OPTAA on DCL16. This takes the following instruments offline:
DCL17
MOPAK
CTDBP (with attached FLORT)
VELPT
ACOMM
OPTAA
Have had to power off DCL17 and DCL16 and reduce call in frequency to 12 hours. Will still (at least should) receive data from MFN. Instruments affected are:
DCL17 (Buoy)
MOPAK
CTDBP3 (with FLORT)
VELPT1
UCSPP (aka ACOMM)
DCL16 (NSIF)
CTDBP1 (with DOSTA) (should internally log)
FLORT
PCO2W1 (should internally log)
PHSEN1 (should internally log)
OPTAA1
NUTNR (should internally log)
SPKIR
VELPT2 (should internally log)

Id: 899 By: michaesm

CE06ISSM
10/2/17, 8:00 PM 3/2/18, 3:44 AM

CAMDS not serviced by vendor in time for deployment

Id: 1236 By: michaesm
Flag: not_operational Exclude: No

CE06ISSM-RID16-05-PCO2WB000
Method: telemetered
5/23/20, 8:00 PM

Reduced battery power on the mooring (unforeseen delay of mooring recovery well past the originally scheduled date) has resulted in the decision to power off the data logger port for this sensor for the remainder of the deployment. No further data will be telemetered from this instrument, though recovered instrument data should be available after the mooring is recovered.

Id: 2194 By: wingardc
Flag: not_available Exclude: No

Review Notes

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

There are no recovered_inst data available for download for any deployment. According to the ingest csvs, the recovered_inst raw data files are available for all deployments. These files should be ingested or the datasets should be annotated to explain why the recovered_inst data aren't available.

By Lori Garzio, on 7/24/19

CE06ISSM-RID16-05-PCO2WB000

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

By Lori Garzio, on 7/24/19

CE06ISSM-RID16-05-PCO2WB000

Data generally look suspect for many deployments of this instrument because of the high percentage of values outside of global ranges. The dataset should be annotated if there is a known issue with this instrument to inform users if all or some data should be considered suspect.

By Lori Garzio, on 7/24/19

CE06ISSM-RID16-05-PCO2WB000
Deployment: 1

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

By Lori Garzio, on 7/24/19

CE06ISSM-RID16-05-PCO2WB000
Deployment: 2

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

By Lori Garzio, on 7/24/19

CE06ISSM-RID16-05-PCO2WB000
Deployment: 5
9/27/16, 4:43 PM 10/5/16, 12:00 AM

Suspect data at the beginning of the deployment - values outside of global ranges.

By Lori Garzio, on 7/24/19

CE06ISSM-RID16-05-PCO2WB000
Deployment: 6

81% of the values for pco2_seawater are fill values.

By Lori Garzio, on 7/24/19

CE06ISSM-RID16-05-PCO2WB000
Deployment: 7

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

By Lori Garzio, on 7/24/19

CE06ISSM-RID16-05-PCO2WB000
Deployment: 8

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

By Lori Garzio, on 7/24/19

New Note