Bad altimeter pings are apparent in many deployments of the coastal gliders. A few example plots are attached - m_water_depth plotted as semi-transparent bathymetry.

By Lori Garzio, on 5/10/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

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

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

61% of the parad_m_par data for deployment 1 are outside of global ranges [0.0, 2500.0]. The majority of the values outside of global ranges are negative (plot zoomed to axis limits [-0.5, 0.5] attached).

By Lori Garzio, on 5/15/19

58% of the parad_m_par data for deployment 2 are outside of global ranges [0.0, 2500.0]. The majority of the values outside of global ranges are negative (plot zoomed to axis limits [-0.5, 0.5] attached).

By Lori Garzio, on 5/15/19

Short deployment (15 days) should be annotated.

By Lori Garzio, on 5/15/19

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

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

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

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