Coastal Glider 320

Reference Designator
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 OC1410A 10/07/2014 12/29/2014 CGVEH-GLDRCE-00320 44.3733 -124.95
2 PS1606 06/16/2016 09/27/2016 CGVEH-GLDRCE-00320 44.6449 -124.289
3 SKQ201704S 04/10/2017 05/22/2017 CGVEH-GLDRCE-00320 46.98 -124.561
4 PS201805A 05/03/2018 08/02/2018 CGVEH-GLDRCE-00320 44.6441 -124.181
5 SKQ201921S 10/12/2019 01/17/2020 CGVEH-GLDRCE-00320 46.984 -124.563
Metadata Start Date End Date Comment

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 3 consecutive down and up casts for CE05MOAS-GL312-04-DOSTAM000 on 7/8/2014 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/14/19

New Note

Metadata Start Date End Date Comment
10/5/14, 8:00 PM 12/28/14, 7:00 PM

Deployment 1 - Power consumption was greater than 1% per day and battery ran down to 10% before the end of the deployment. Glider was drifting before it was recovered.

Id: 890 By: michaesm
Flag: not_operational Exclude: No