|recovered_host||ctdgv_m_glider_instrument_recovered||Data Products||Report M2M Stats||Science|
|telemetered||ctdgv_m_glider_instrument||Data Products||Report M2M Stats||Science|
|Deployment||Cruise||Start Date||Stop Date||Mooring Asset||Node Asset||Sensor Asset||Latitude||Longitude||Deployment Depth||Water Depth|
|Metadata||Start Date||End Date||Comment|
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/31/19
97% of sci_seawater_density values are NaNs. Lat and lon are parameters used in the data product algorithm, so I think this got messed up with the re-organization of the glider lat/lon parameters. See Redmine ticket #14486
By Lori Garzio, on 1/23/20
recovered_host data aren't available for this deployment. According to the ingest csv, the glider failed and recovered data aren't expected. This dataset should be annotated.
By Lori Garzio, on 1/22/20
No annotations yet.