Coastal Glider 383

Reference Designator
CE05MOAS-GL383
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 PS1501 01/21/2015 03/13/2015 CGVEH-GLDRCE-00383 44.6759 -124.302
2 PS1508 08/13/2015 11/25/2015 CGVEH-GLDRCE-00383 44.678 -124.17
3 TN-342 05/06/2016 05/12/2016 CGVEH-GLDRCE-00383 47.0913 -124.367
4 EK-1701 01/31/2017 05/10/2017 CGVEH-GLDRCE-00383 44.6578 -124.187
5 ML-1707 07/19/2017 10/09/2017 CGVEH-GLDRCE-00383 44.705 -124.382
6 EK201807B 07/16/2018 10/17/2018 CGVEH-GLDRCE-00383 44.625 -124.188
7 SU20181101 11/01/2018 01/14/2019 CGVEH-GLDRCE-00383 44.655 -124.166
8 SU20190125 01/25/2019 03/24/2019 CGVEH-GLDRCE-00383 44.64 -124.606
9 SU20200220 02/20/2020 04/10/2020 CGVEH-GLDRCE-00383 44.556 -124.219
Metadata Start Date End Date Comment
CE05MOAS

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

CE05MOAS

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

CE05MOAS-GL383
Deployment: 3

Data should be annotated to explain why the deployment was so short.

By Lori Garzio, on 5/1/19

CE05MOAS-GL383
Deployment: 4
3/1/17, 12:00 AM 4/10/17, 12:00 AM

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 5/1/19

New Note

No annotations yet.