Coastal Glider 339

Reference Designator
CP05MOAS-GL339
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 SI20150110 01/12/2015 04/30/2015 CGVEH-GLDRCP-00339 40.109 -70.1713
2 SI20160122 01/21/2016 04/20/2016 CGVEH-GLDRCP-00339 40.083 -70.375
3 WJ20170115 01/16/2017 04/19/2017 CGVEH-GLDRCP-00339 40.0661 -70.3544
4 AR-18 06/06/2017 07/27/2017 CGVEH-GLDRCP-00339 40.0352 -70.6199
5 AR-24 10/29/2017 10/31/2017 CGVEH-GLDRCP-00339 40.0781 -70.7202
6 SI20180126 01/27/2018 04/23/2018 CGVEH-GLDRCP-00339 39.9895 -70.3671
7 AR-31 10/30/2018 11/02/2018 CGVEH-GLDRCP-00339 40.0248 -70.7
8 TS20181130 11/30/2018 11/30/2018 CGVEH-GLDRCP-00339 40.0824 -70.1885
9 TS20181209 12/09/2018 03/01/2019 CGVEH-GLDRCP-00339 40.0822 -70.1885
10 TS20200301 03/02/2020 05/22/2020 CGVEH-GLDRCP-00339 40.0813 -70.3729
11 TS20200613 06/13/2020 CGVEH-GLDRCP-00339 40.0815 -70.3674
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-GL339
Deployment: 1

The glider looks like it had steering issues. Dataset should be annotated.

By Lori Garzio, on 5/16/19

CP05MOAS-GL339
Deployment: 2

The 5 days missing data at the end of the deployment should be annotated.

By Lori Garzio, on 5/16/19

CP05MOAS-GL339
Deployment: 2

The glider looks like it had steering issues. Dataset should be annotated.

By Lori Garzio, on 5/16/19

CP05MOAS-GL339
Deployment: 5

Short deployment (3 days) should be annotated.

By Lori Garzio, on 5/16/19

CP05MOAS-GL339
Deployment: 6

The 13 days missing data at the end of the deployment should be annotated.

By Lori Garzio, on 5/16/19

CP05MOAS-GL339
Deployment: 6

The glider looks like it had steering issues. Dataset should be annotated.

By Lori Garzio, on 5/16/19

New Note

Metadata Start Date End Date Comment
CP05MOAS-GL339
10/28/17, 8:31 PM 10/31/17, 7:32 PM

Deployment 5: Glider experienced a leak in the digifin and needed to be recovered early.

Id: 2035 By: cdobson

CP05MOAS-GL339
10/30/18, 5:59 PM 11/2/18, 8:00 PM

Deployment 7: Glider was deployed and ran a single mission before it was determined that the ballast needed adjustments for the current ocean conditions. Glider was recovered after 3 days. No data expected for this deployment.

Id: 1575 By: cdobson

CP05MOAS-GL339
Method: recovered-host
10/30/18, 5:59 PM 11/2/18, 8:00 PM

Glider was deployed and ran a single mission and it was determined that the ballast needed adjustments for the current ocean conditions. Glider was recovered after 3 days. No data expected for this deployment.

Id: 1576 By: cdobson

CP05MOAS-GL339
11/30/18, 10:50 AM 11/30/18, 1:26 PM

Deployment 8: Glider had to be recovered immediately after deployment due to a failed attitude sensor; no data are expected for this deployment.

Id: 2036 By: cdobson