pCO2 Water

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

Dataset Reviews Last processed: 7/23/19, 5:17 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 122 23 0 98 1 2 187 25 / 1 2 3 Complete
2 telemetered 185 3 0 180 1 1 3 25 / 4 4 3 Complete
3 recovered_host 127 126 0 0 0 0 2,971 25 / 3 Complete
4 recovered_inst pco2w_abc_instrument / Complete
5 recovered_inst pco2w_abc_instrument / Complete
6 recovered_host 200 31 0 169 0 0 693 25 / 3 Complete
7 recovered_host 177 24 0 153 0 0 539 25 / 3 Complete
8 recovered_host 172 172 0 0 0 0 3,946 25 / 3 Complete
9 recovered_host 181 181 0 0 0 0 2,130 25 / 3 Complete
Data Ranges Review Images

Test Notes

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

Data Coverage

Deployment: 123456789
2%
19%99%16%14%100%100%

Lat/Lon Differences (km)

Deployment: 123456789
1 0.00
2 0.000.00
3 0.080.080.00
6 0.180.180.170.00
7 0.240.240.220.390.00
8 0.170.170.160.010.380.00
9 0.170.170.180.340.100.330.00

System Annotations

Metadata Start Date End Date Comment
CE01ISSM-MFD35-05-PCO2WB000
Method: telemetered
Stream: pco2w_abc_dcl_instrument
4/17/14, 4: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: 278 By: friedrich.knuth

CE01ISSM-MFD35-05-PCO2WB000
Method: recovered_host
Stream: pco2w_abc_dcl_instrument_recovered
4/17/14, 4: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: 294 By: friedrich.knuth

CE01ISSM
4/17/14, 4: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: 868 By: michaesm

CE01ISSM
8/7/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.

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

CE01ISSM-MFD35
10/28/16, 8:00 PM 5/14/17, 8:00 PM

The file system on the SD card used by embedded Linux card comprising DCL35 became corrupted on Saturday, October 29, 2016. Affected instruments are: [ADCPT, PCO2W, PHSEN, PRESF, VEL3D]. All instruments are set to log internally. Will not receive telemetered data, but do not anticipate complete loss of data.

Id: 851 By: michaesm
Flag: not_available Exclude: No

CE01ISSM
12/11/16, 7:00 PM 5/30/17, 8:00 PM

On Monday, Mon Dec 12 15:30:00 2016, stopped receiving any data from CTDBP3. No indication as to possible cause.

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

CE01ISSM
2/5/17, 7:00 PM 4/30/17, 8:00 PM

The buoy and mfn battery voltages have been drawn down faster than expected. Have shutdown further power to DCL16, DCL17, CPM3, and DCL37 (DCL35 failed several weeks ago). This takes the following instruments offline:
DCL16
CTDBP + DOSTA (probably internally recording)
FLORTNUTNR (probably internally recording)
PHSEN (probably internally recording)
PCO2W (probably internally recording)
OPTAA
SPKIR
VELPT (probably internally recording)

DCL17
MOPAK
CTDBP + FLORT
VELPT (probably internally recording)
ACOMM
DCL35
ADCPT (probably internally recording)
PCO2W (probably internally recording)
PHSEN (probably internally recording)
PRESF (probably internally recording)
VEL3D (probably internally recording)
DCL37
CTDBP + DOSTA (probably internally recording)
OPTAA
ZPLSC (probably internally recording)

Id: 871 By: michaesm
Flag: not_available Exclude: No

CE01ISSM-MFD35
5/11/17, 8:00 PM 10/30/17, 8:00 PM

Lost communication with DCL35, on the MFN of CE01ISSM sometime after 2017/05/12 04:32:31.744. Reason unknown. Attempted to log into the system and establish both an ssh connection and a minicom session with no success. Minicom session showed zero activity, suggesting the system is completely offline. With the exception of the VEL3D, all instruments hosted by DCL35 are autonomous. No further data should be expected from: [ADCPT (recording internally), PRESF (recording internally), PC02W (recording internally), PHSEN (recording internally), VEL3D (status unknown)]

Id: 852 By: michaesm
Flag: not_available Exclude: No

CE01ISSM-MFD35-05-PCO2WB000
4/2/18, 8:00 PM

Suspect that the fluid path is either blocked or the pump is not working correctly. It appears that the system is not fully pumping either the blank (nanopure water) or reagent equilibrated with seawater through the sample volume. This is evident in how long it takes for the blank signal to flush out from the measurement signal. It's possible there is a clog that will clear out.

Id: 1456 By: michaesm
Flag: suspect Exclude: No

CE01ISSM-MFD35
Method: telemetered
1/11/20, 1:45 PM

During a large storm event on 2020-01-11, the surface buoy and NSIF broke free and went adrift. As a result, telemetry from the data loggers and instrumentation on the seafloor platform has ceased. We expect the system to continue autonomous operations and hope to download data from the data loggers and instruments after the seafloor platform is recoverd in the spring of 2020.

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

Review Notes

Metadata Start Date End Date Comment
CE01ISSM-MFD35-05-PCO2WB000

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

By Lori Garzio, on 7/24/19

CE01ISSM-MFD35-05-PCO2WB000

There are no data available for download for deployments 4 and 5. According to the ingest csvs, the recovered_inst raw data files are available for both deployments. These should be ingested or the dataset should be annotated to explain why the data aren't available.

By Lori Garzio, on 7/24/19

CE01ISSM-MFD35-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

CE01ISSM-MFD35-05-PCO2WB000

Data generally look suspect for all deployments 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

CE01ISSM-MFD35-05-PCO2WB000
Deployment: 1
4/17/14, 8:45 PM 8/16/14, 10:30 PM

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

By Lori Garzio, on 7/24/19

CE01ISSM-MFD35-05-PCO2WB000
Deployment: 2

There are no data available for this deployment. This should be annotated or the recovered files should be ingested.

By Lori Garzio, on 7/24/19

CE01ISSM-MFD35-05-PCO2WB000
Deployment: 3
6/3/15, 5:15 PM 10/7/15, 12:00 AM

Suspect data - 84% of the values for pco2_seawater are outside of global ranges.

By Lori Garzio, on 7/24/19

CE01ISSM-MFD35-05-PCO2WB000
Deployment: 6
9/30/16, 4:45 PM 4/17/17, 7:45 PM

Suspect data - 54% of the values for pco2_seawater are outside of global ranges.

By Lori Garzio, on 7/24/19

CE01ISSM-MFD35-05-PCO2WB000
Deployment: 7

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

By Lori Garzio, on 7/24/19

CE01ISSM-MFD35-05-PCO2WB000
Deployment: 8

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

By Lori Garzio, on 7/24/19

CE01ISSM-MFD35-05-PCO2WB000
Deployment: 9

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

By Lori Garzio, on 7/24/19

New Note