Daily DO spikes starting in December 2016 for this deployment suggest biofouling. Excluding from summary data ranges.

By Lori Garzio, on 3/29/19

18 days of data at the end of the deployment are missing from the recovered_inst data stream, but available in the recovered_host and telemetered data streams. These data should be available in the recovered_inst data stream (or annotated if there was an issue with internally recording data).

By Lori Garzio, on 3/29/19

The missing data at the end of deployment 1 should be annotated.

By Lori Garzio, on 3/29/19

The DO values at the end of deployment 3 are <50 umol kg-1 and jump to ~250 umol kg-1 at the beginning of deployment 4. Further analysis should be done using shipboard bottle data, which is outside the scope of this project.

By Lori Garzio, on 3/29/19

121 days of data at the end of the deployment are missing from the recovered_inst data stream, but available in the recovered_host and telemetered data streams. These data should be available in the recovered_inst data stream (or annotated if there was an issue with internally recording data). It appears that the instrument was having issues (values <0) so the data from that time range are potentially suspect.

By Lori Garzio, on 3/29/19

Deployment 7 recovered_inst data should be ingested, or the dataset should be annotated to indicate why no recovered_inst data are available. The ingest csv indicates that the recovered_inst data are available, but the line is commented out.

By Lori Garzio, on 3/29/19

Deployment 5 should be annotated to indicate why no recovered_inst data are available. According to the ingest csv, "No Data on instrument. Did not start logging."

By Lori Garzio, on 3/29/19

The range of upward_velocity values for this deployment is substantially higher compared to the range for deployments 2-9.

By Lori Garzio, on 8/14/19

a change in pressure is visible at the end of July

By Leila Belabbassi, on 6/20/19

recovered instrument data are missing in the system

By Leila Belabbassi, on 5/31/19

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

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

By Lori Garzio, on 7/24/19

According to the ingest csv, the instrument failed at deployment and the recovered_inst line is commented out. However, recovered_host data are available for download (plot attached). Either the recovered_inst data should be ingested, or the dataset should be annotated if the instrument wasn't functional (and the recovered_host data are bad).

By Lori Garzio, on 7/24/19

According to the ingest csv, the instrument failed at deployment. This should be annotated in the system.

By Lori Garzio, on 7/24/19

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

By Lori Garzio, on 7/24/19

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

By Lori Garzio, on 7/24/19

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

By Lori Garzio, on 7/24/19

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

By Lori Garzio, on 7/24/19

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 deployments 1-5 and 9. 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

There are no data available for download for this deployment. According to the ingest csv, the instrument failed at deployment. This should be annotated in the system.

By Lori Garzio, on 7/24/19