There are no adcp_velocity_glider data available for deployments 7-9. According to the ingest csvs, the raw data files are available. These data should be ingested or annotated to indicate why they are missing.

By Lori Garzio, on 8/30/19

Looks like the glider started drifting - this should be annotated

By Lori Garzio, on 8/30/19

Looks like the glider started drifting - this should be annotated

By Lori Garzio, on 8/30/19

Data are in the telemetered data stream but are not in the recovered data stream from 2017-02-02T18:04:46 to 2017-02-02T20:43:17. These data should be in the recovered stream.

By Lori Garzio, on 8/30/19

The deployment 7 .nc files are missing coordinates lat, lon, and pressure.

By Lori Garzio, on 8/30/19

Short 2-3 day deployments for deployments 6-9 should be annotated.

By Lori Garzio, on 8/30/19

99% of the sci_bsipar_par values for deployments 1 and 2 are outside of global ranges. sci_bsipar_par is the unscaled L0 PAR data product. The global ranges for this parameter are the same as for the scaled L1 PAR data product [0.0, 2500.0]. The global range for sci_bsipar_par should be reviewed.

By Lori Garzio, on 8/30/19

Suspect DO data - high DO outliers. This seems to occur particularly when the glider is close to the seafloor.

By Lori Garzio, on 8/30/19

The majority (89-93%) of the seawater velocity data are NaNs, outside of global ranges, or outliers (+/- 5 SD). See the science variable output for details: https://github.com/ooi-data-lab/data-review-tools/blob/master/data_review/output/CE05MOAS/CE05MOAS-GL384-03-ADCPAM000/CE05MOAS-GL384-03-ADCPAM000_sciencevar_summary.csv

By Lori Garzio, on 8/30/19

There are no adcp_velocity_glider data available for deployments 2 and 5. According to the ingest csvs, the raw data files are available. These data should be ingested or annotated to indicate why they are missing.

By Lori Garzio, on 8/30/19

Several suspect portions of profiles in Dec 2017 and towards the end of the deployment.

By Lori Garzio, on 8/30/19

Several suspect portions of profiles throughout the deployment.

By Lori Garzio, on 8/30/19

Several suspect portions of profiles in the 2nd half of the deployment.

By Lori Garzio, on 8/30/19

99% of the sci_bsipar_par values for this deployment are outside of global ranges. sci_bsipar_par is the unscaled L0 PAR data product. The global ranges for this parameter are the same as for the scaled L1 PAR data product [0.0, 2500.0]. The global range for sci_bsipar_par should be reviewed.

By Lori Garzio, on 8/29/19

Suspect DO data - high DO outliers. This seems to occur particularly when the glider is close to the seafloor. Also suspect profile in March 2015

By Lori Garzio, on 8/29/19

Suspect DO data - high DO outliers. This seems to occur particularly when the glider is close to the seafloor.

By Lori Garzio, on 8/29/19

Suspect DO data - high DO outliers. This seems to occur particularly when the glider is close to the seafloor.

By Lori Garzio, on 8/29/19

Several suspect CDOM profiles in late Feb 2015

By Lori Garzio, on 8/29/19

There are several hours on 5/13/2017 where data are available in the telemetered stream and not the recovered_host stream for every instrument. These data should be available in the recoverred_host dataset: 2017-05-13T04:11:19 to 2017-05-13T09:20:47

By Lori Garzio, on 8/29/19

There are no data available for download for deployments 1-4 because the data were delivered via the CTD data stream (Redmine 8662). Now that the DO instrument has been separated from the CTD, the old DO data should be ingested in the DO data stream. Users currently have to go to the collocated CTD reference designator to get the DO data for these deployments.

By Lori Garzio, on 8/29/19