parad_m_par data for deployment 5 is a record of NaNs. According to the provenance.json file, the calibration factor 'CC_bsipar_par_scaling' is missing.

By Lori Garzio, on 5/15/19

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 5/15/19

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 5/15/19

Glider optodes typically exhibit a sensor lag of 20-25 seconds. Example attached of several segments with consecutive down and up casts for CP05MOAS-GL335-04-DOSTAM000 on 10/26/2015 showing a typical measurement time lag. Profiles should be analyzed for individual time lags and data should be adjusted. OOI doesn't necessarily need to make the adjustment but users should be aware of the issue.

By Lori Garzio, on 5/15/19

Artificial band around 10 dbar (seen in the xsection plots) throughout the entire deployment where the glider doesn't reach the surface. Profile plots attached are zoomed to 2 days showing the shift in data from the subsurface profiles compared to the profiles that reach the surface.

By Lori Garzio, on 5/15/19

The glider appeared to stay at the surface for several days at the beginning of deployment 4 - this should be annotated.

By Lori Garzio, on 5/15/19

pressure coordinate missing in data files

By Leila Belabbassi, on 5/15/19

suspect data

By Leila Belabbassi, on 5/15/19

Data are missing for every parameter from the recovered_host data stream for 3 days at the beginning of the deployment. These data are available in the telemetered stream, and should be available in the recovered_host data stream.

By Lori Garzio, on 5/15/19

The gaps in the data file are not annotated in the system.

By Leila Belabbassi, on 5/15/19

3 days missing at the start of the deployment are not annotated in the system. Also, gaps in the data files may be explained by annotation ID#s 986 through 991. Please confirm.

By Leila Belabbassi, on 5/15/19

A gap of 10 days missing at the start of deployment is not annotated in the system. Also, a large gap before the end of deployment and other gaps in the data file may be associated with annotation ID#s 971 through 975. Please confirm.

By Leila Belabbassi, on 5/15/19

The large gap before the end of deployment may be associated with annotation ID# 981 through 985. Please confirm

By Leila Belabbassi, on 5/15/19

Suspect data at the end of the deployment.

By Lori Garzio, on 5/15/19

Data are missing for every parameter from the recovered_host data stream at the beginning of the deployment. These data are available in the telemetered stream, and should be available in the recovered_host data stream.

By Lori Garzio, on 5/15/19

Suspect profile on/around 1/25/2017.

By Lori Garzio, on 5/15/19

Short deployment (15 days) should be annotated.

By Lori Garzio, on 5/15/19

Data gaps close to the surface during the second half of the deployment. Dataset should be annotated if there was an issue.

By Lori Garzio, on 5/15/19

The glider looks like it had steering issues. The dataset should be annotated if the glider didn't sample according to plan.

By Lori Garzio, on 5/15/19

Data are missing for every parameter from the recovered_host data stream for 3 days at the beginning of the deployment. These data are available in the telemetered stream, and should be available in the recovered_host data stream.

By Lori Garzio, on 5/15/19