pCO2 Water

Reference Designator
CE06ISSM-MFD35-05-PCO2WB000
Start Depth
29
End Depth
29
Location
Multi-Function Node
Current Status
Review Complete
Class
PCO2W (pCO2 Water)
Series
PCO2W-B
Science Discipline
Chemical
Make
Sunburst
Model
SAMI-pCO2
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/CE06ISSM/MFD35/05-PCO2WB000/metadata
Method Data Stream Content Type
recovered_host pco2w_abc_dcl_instrument_blank_recovered Data Products Report M2M Stats Science
recovered_host pco2w_abc_dcl_instrument_recovered Data Products Report M2M Stats Science
recovered_host pco2w_abc_dcl_metadata_recovered Metadata Report M2M Engineering
recovered_host pco2w_abc_dcl_power_recovered Power Data Report M2M Engineering
recovered_inst pco2w_abc_instrument Data Products Report M2M Stats Science
recovered_inst pco2w_abc_instrument_blank Data Products Report M2M Stats Science
recovered_inst pco2w_abc_metadata Metadata Report M2M Engineering
recovered_inst pco2w_abc_power Power Data Report M2M Engineering
telemetered pco2w_abc_dcl_instrument Data Products Report M2M Stats Science
telemetered pco2w_abc_dcl_instrument_blank Data Products Report M2M Stats Science
telemetered pco2w_abc_dcl_metadata Metadata Report M2M Engineering
telemetered pco2w_abc_dcl_power Power Data Report M2M Engineering
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 Review OC1410A 10/07/2014 04/10/2015 CGMCE-06ISSM-00001 CGINS-PCO2WB-C0062 47.1334 -124.268 30 30
2 Review OC1503D 04/10/2015 10/13/2015 CGMCE-06ISSM-00002 CGINS-PCO2WB-C0085 47.1311 -124.272 29 29
3 Review OC1510A 10/13/2015 05/06/2016 CGMCE-06ISSM-00003 CGINS-PCO2WB-C0062 47.1333 -124.271 29 29
4 Review TN-342 05/06/2016 09/24/2016 CGMCE-06ISSM-00004 CGINS-PCO2WB-C0063 47.135 -124.273 29 29
5 Review AT37-03 09/27/2016 04/15/2017 CGMCE-06ISSM-00005 CGINS-PCO2WB-C0081 47.1336 -124.272 29 29
6 Review SKQ201704S 04/13/2017 10/05/2017 CGMCE-06ISSM-00006 CGINS-PCO2WB-C0119 47.1341 -124.272 29 29
7 Review SKQ201715S 10/05/2017 03/28/2018 CGMCE-06ISSM-00007 CGINS-PCO2WB-C0063 47.1346 -124.272 29 29
8 Review SKQ201808S 03/28/2018 09/20/2018 CGMCE-06ISSM-00008 CGINS-PCO2WB-C0119 47.1336 -124.269 29 29
9 Review SR1813 09/24/2018 04/25/2019 CGMCE-06ISSM-00009 CGINS-PCO2WB-C0084 47.1348 -124.271 29 29
10 Review SKQ201910S 04/25/2019 10/12/2019 CGMCE-06ISSM-00010 CGINS-PCO2WB-C0147 47.1347 -124.271 29 29
11 Review SKQ201921S 10/12/2019 CGMCE-06ISSM-00011 CGINS-PCO2WB-C0053 47.1344 -124.271 29 29
Metadata Start Date End Date Comment
CE06ISSM-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

CE06ISSM-MFD35-05-PCO2WB000

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

By Lori Garzio, on 7/24/19

CE06ISSM-MFD35-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-MFD35-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-MFD35-05-PCO2WB000
Deployment: 2

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

By Lori Garzio, on 7/24/19

CE06ISSM-MFD35-05-PCO2WB000
Deployment: 4

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

By Lori Garzio, on 7/24/19

CE06ISSM-MFD35-05-PCO2WB000
Deployment: 5

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

By Lori Garzio, on 7/24/19

CE06ISSM-MFD35-05-PCO2WB000
Deployment: 6

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

By Lori Garzio, on 7/24/19

CE06ISSM-MFD35-05-PCO2WB000
Deployment: 7

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

By Lori Garzio, on 7/24/19

New Note

Metadata Start Date End Date Comment
CE06ISSM-MFD35-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: 271 By: friedrich.knuth

CE06ISSM-MFD35-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: 295 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-MFD35
5/10/17, 8:00 PM 10/30/17, 8:00 PM

Lost communication with DCL35, on the MFN of CE06ISSM sometime after 2017/05/11 12:32:17.552. Suspect failed/corrupted SD card based on results of minicom session with DCL35 (see attached). 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 (offline)

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

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-MFD35
Method: telemetered
10/17/19, 12:45 AM 5/23/20, 8:00 PM

Updated, 2020-05-24: Between 2019-10-17 and 2020-05-24, the clock on CPM3 was off by approximately 27 minutes. Communications between the buoy and the MFN were out of sync during this time period. The clock was automatically updated during routine operations on May 24, 2020 to the correct time, allowing communications and normal operations on the MFN to resume. *Communications to the seafloor sensors failed. Status of the instrumentation and data loggers is unknown. With the exception of the VEL3D and OPTAA, the sensors on the seafloor platform should continue to autonomously sample for the remainder of deployment. Until we recover and redeploy the mooring in the spring of 2020, no further telemetered data will be available from the seafloor sensors.

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