Coastal Glider 381

Reference Designator
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 OC1410A 10/08/2014 01/03/2015 CGVEH-GLDRCE-00381 44.3704 -124.95
2 TN-342 05/06/2016 06/21/2016 CGVEH-GLDRCE-00381 47.0916 -124.368
3 PS1702A 02/13/2017 03/31/2017 CGVEH-GLDRCE-00381 44.6428 -124.309
4 SKQ201715S 10/04/2017 10/05/2017 CGVEH-GLDRCE-00381 46.857 -124.975
5 PS1712A 12/08/2017 02/03/2018 CGVEH-GLDRCE-00381 47.007 -124.587
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

Deployment: 2

This glider looks like it had a sampling change (similar to glider 319, see annotation ID 1371). This dataset should be annotated.

By Lori Garzio, on 8/28/19

Deployment: 4

Short (2 day) deployment should be annotated

By Lori Garzio, on 8/28/19

Deployment: 5

Glider looks like it drifted - should be annotated

By Lori Garzio, on 8/28/19

New Note

No annotations yet.