Coastal Glider 340

Reference Designator
CP05MOAS-GL340
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 KN-222 10/06/2014 12/12/2014 CGVEH-GLDRCP-00340 39.8271 -70.5798
2 AT-27 05/07/2015 07/02/2015 CGVEH-GLDRCP-00340 40.0837 -70.3755
3 SI20160122 01/21/2016 02/03/2016 CGVEH-GLDRCP-00340 40.037 -70.6852
4 CT20160808 08/09/2016 08/09/2016 CGVEH-GLDRCP-00340 40.0656 -70.3653
5 AR-08 10/11/2016 10/13/2016 CGVEH-GLDRCP-00340 40.0889 -70.3783
6 SI20170418 04/20/2017 04/23/2017 CGVEH-GLDRCP-00340 40.0286 -70.4844
7 WJ20170815 08/17/2017 10/28/2017 CGVEH-GLDRCP-00340 40.007 -70.8482
8 TS20190205 02/05/2019 05/04/2019 CGVEH-GLDRCP-00340 39.9156 -70.3672
9 AR-39 09/27/2019 11/05/2019 CGVEH-GLDRCP-00340 40.0501 -70.6002
10 TS20191212 12/13/2019 03/03/2020 CGVEH-GLDRCP-00340 40.0817 -70.7481
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-GL340
Deployment: 1

Glider looks like it drifted at the end of the deployment - this should be annotated

By Lori Garzio, on 9/3/19

CP05MOAS-GL340
Deployment: 3

Short deployment should be annotated.

By Lori Garzio, on 9/3/19

CP05MOAS-GL340
Deployment: 4

Short deployment should be annotated.

By Lori Garzio, on 9/3/19

New Note

Metadata Start Date End Date Comment
CP05MOAS-GL340
1/21/16, 12:08 PM 2/2/16, 8:32 PM

Deployment 3: Glider experienced an aft leak shortly after deployment and was drifted until it was recovered; no data are expected from this deployment.

Id: 2037 By: cdobson

CP05MOAS-GL340
8/9/16, 2:21 AM 8/9/16, 7:40 PM

Deployment 4: Glider's altimeter failed upon deployment so it was recovered. No data are expected from this deployment.

Id: 2038 By: cdobson

CP05MOAS-GL340
10/10/16, 9:12 PM 10/13/16, 7:11 AM

Deployment 5: Glider leaked after one day. No data are expected except from the ADCP.

Id: 672 By: cdobson

CP05MOAS-GL340
4/19/17, 8:50 PM 4/21/17, 8:00 PM

Deployment 6: This is a test deployment and was recovered the same day due to leak. No data are expected.

Id: 640 By: cdobson
Flag: not_available Exclude: No

CP05MOAS-GL340
Method: telemetered
5/1/19, 8:00 PM 5/4/19, 10:00 AM

Deployment 8: Glider stopped sampling on 5/3/2019 15:00 UTC due to a failed altimeter. Glider recovered 5/4/2019 at 14:00 UTC.

Id: 1583 By: cdobson

CP05MOAS-GL340
10/25/19, 8:00 AM 11/4/19, 7:00 PM

Deployment 9: Glider experienced GPS failure and forced to drift on 10/26/2019. No telemetered data expected after this date. Glider recovered 11/5/2019.

Id: 1744 By: cdobson

CP05MOAS-GL340
2/22/20, 7:00 AM 3/3/20, 7:00 AM

Deployment 10: Glider experienced a digifin leak on 2/22/2020 and was put into surface drift mode. No data are expected after this date.

Id: 2014 By: cdobson