Coastal Glider 336

Reference Designator
CP05MOAS-GL336
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 SI20150110 01/11/2015 03/27/2015 CGVEH-GLDRCP-00336 40.0204 -70.3854
2 CT20160808 08/09/2016 08/18/2016 CGVEH-GLDRCP-00336 39.8425 -70.3405
3 AR-08 10/11/2016 12/19/2016 CGVEH-GLDRCP-00336 40.0854 -70.3778
4 WJ20170115 01/16/2017 04/19/2017 CGVEH-GLDRCP-00336 39.9182 -70.3995
5 WJ20170815 08/17/2017 10/28/2017 CGVEH-GLDRCP-00336 39.92 -70.8676
6 SI20180126 01/27/2018 04/03/2018 CGVEH-GLDRCP-00336 39.8596 -70.3822
7 CT20180724 07/24/2018 10/25/2018 CGVEH-GLDRCP-00336 39.9488 -70.6729
8 AR-34 04/08/2019 04/08/2019 CGVEH-GLDRCP-00336 39.9581 -71.0004
9 TS20190516 05/16/2019 07/28/2019 CGVEH-GLDRCP-00336 40.0368 -70.7816
Metadata Start Date End Date Comment
CP05MOAS

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

CP05MOAS

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/15/19

CP05MOAS-GL336
Deployment: 1

There are 42 days between the last data point and the deployment end date. This should be annotated.

By Lori Garzio, on 5/15/19

CP05MOAS-GL336
Deployment: 2

Short deployment (5 days) should be annotated.

By Lori Garzio, on 5/15/19

CP05MOAS-GL336
Deployment: 6

recovered_host data aren't available for download for any instruments for deployment 6. These data should be available for download.

By Lori Garzio, on 5/15/19

New Note

Metadata Start Date End Date Comment
CP05MOAS-GL336
2/11/15, 7:00 PM 3/27/15, 7:59 PM

Deployment 1: Glider experienced a leak on 2015-02-12 and went adrift. No science data expected after this date.

Id: 1814 By: cdobson
Flag: not_operational Exclude: No

CP05MOAS-GL336
8/13/16, 8:00 PM 8/18/16, 8:45 AM

Deployment 2: Glider experienced a leak on 2016-08-14 and went adrift. No science data expected after this date.

Id: 1815 By: cdobson
Flag: not_operational Exclude: No

CP05MOAS-GL336
3/19/18, 3:00 PM 4/3/18, 7:59 PM

Deployment 6: Glider lost ability to steer and went adrift 2018-03-19 and was recovered 2018-04-03.

Id: 1366 By: cdobson
Flag: not_operational Exclude: No

CP05MOAS-GL336
4/7/18, 8:14 PM 4/8/18, 6:56 AM

Deployment 8: Glider experienced pump issues upon deployment and needed to be recovered.

Id: 1819 By: cdobson
Flag: not_operational Exclude: No

CP05MOAS-GL336
5/15/19, 7:37 PM 7/27/19, 8:03 PM

Deployment 9: Glider mysteriously disappeared when staged for recovery. Believed to be a vessel strike or fouled in fishing gear. No recovered dataset expected.

Id: 1782 By: cdobson