There are almost 2 months of data available in the recovered_wfp streams compared to the recovered_inst data streams for deployment 2. These data should be available in the recovered_inst stream or annotated to explain if there was an issue.

By Lori Garzio, on 5/30/19

conductivity_millisiemens (mS cm-1) has the same global ranges in the system as dpc_ctd_seawater_conductivity (S m-1): [0.0, 6.0]. This should be reviewed.

By Lori Garzio, on 5/30/19

Suspect data towards the end of the data record.

By Lori Garzio, on 5/30/19

Deployment 1 should be annotated to indicate why the deployment was so short and why recovered data are not available.

By Lori Garzio, on 5/30/19

There is a limited amount of data from this profiler available for download. This should be annotated so users are aware of the issues with the deep profilers.

By Lori Garzio, on 5/30/19

There are no data from deployment 3 available for download for any instrument. These data need to be ingested or should be annotated.

By Lori Garzio, on 5/30/19

There are no deployment depths for this profiler in asset management.

By Lori Garzio, on 5/30/19

temperature3 data are stuck at 99999.9922. This dataset should be annotated until the issue is fixed.

By Lori Garzio, on 5/30/19

temperature1 data are stuck at 99999.9922. This dataset should be annotated until the issue is fixed.

By Lori Garzio, on 5/30/19

temperature3 doesn't appear to be recording vent fluid temperatures. This should be annotated.

By Lori Garzio, on 5/30/19

temperature3 doesn't appear to be recording vent fluid temperatures. This should be annotated.

By Lori Garzio, on 5/30/19

There is a gap in the data from 7/13 - 7/18, and when the sensor comes back online the data for temperature1 and temperature2 are substantially lower than before. This should be annotated to let users know if something happened to the instrument.

By Lori Garzio, on 5/30/19

There are no global ranges in the system for any of the science parameters.

By Lori Garzio, on 5/30/19

There are no pressure data in any of the .nc files. This should be a coordinate.

By Lori Garzio, on 5/30/19

This deployment should be annotated to indicate why only 1 month of data is available for download.

By Lori Garzio, on 5/30/19

There are no data available for download from deployment 1. These data should be available or the dataset should be annotated.

By Lori Garzio, on 5/30/19

Most of the nitrate data are negative. This dataset should be annotated until the issue is fixed.

By Lori Garzio, on 5/30/19

parad_m_par values are orders of magnitude too low for this deployment (max value = 0.0011). sci_bsipar_par values are reasonable, so the scaling factor should be reviewed.

By Lori Garzio, on 5/30/19

5 science variables are all nans. The provenance.json file is attached with all of the calibration coefficients and collocated data that are missing (in the computed_provenance section). This dataset should be annotated until the issues are fixed.

By Lori Garzio, on 5/30/19

The optical_backscatter data from this instrument looks exactly the same as the backscatter data from the FLORTM instrument - this seems unlikely and should be checked to make sure the same data isn't being ingested for 2 different instruments. Plot links below

https://marine.rutgers.edu/cool/ooi/data-eval/data_review/CP/CP05MOAS/CP05MOAS-PG564/CP05MOAS-PG564-03-FLORTM000/xsection_plots/deployment0002/rm_erroneous_data_CP05MOAS-PG564-03-FLORTM000-recovered_host-optical_backscatter_20170817.png

https://marine.rutgers.edu/cool/ooi/data-eval/data_review/CP/CP05MOAS/CP05MOAS-PG564/CP05MOAS-PG564-04-FLORTO000/xsection_plots/deployment0002/rm_erroneous_data_CP05MOAS-PG564-04-FLORTO000-recovered_host-optical_backscatter_20170817.png

By Lori Garzio, on 5/30/19