Coastal Glider 382

Reference Designator
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 PS1501 01/21/2015 04/29/2015 CGVEH-GLDRCE-00382 44.6751 -124.307
2 AT37-03 09/28/2016 01/06/2017 CGVEH-GLDRCE-00382 44.6351 -124.306
3 SKQ201704S 04/10/2017 06/28/2017 CGVEH-GLDRCE-00382 46.9785 -124.541
4 ML20180907 09/07/2018 12/03/2018 CGVEH-GLDRCE-00382 43.382 -124.42
5 SU20190125 01/25/2019 04/26/2019 CGVEH-GLDRCE-00382 44.616 -124.605
6 EK20190515 05/15/2019 08/08/2019 CGVEH-GLDRCE-00382 44.635 -124.304
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: 3

There are several hours on 5/13/2017 where data are available in the telemetered stream and not the recovered_host stream for every instrument. These data should be available in the recoverred_host dataset: 2017-05-13T04:11:19 to 2017-05-13T09:20:47

By Lori Garzio, on 8/29/19

New Note

No annotations yet.