1. Arrays
  2. Coastal Pioneer
  3. Mobile Assets
  4. Coastal Glider 387

Coastal Glider 387

Reference Designator
CP05MOAS-GL387
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 KN-217 04/16/2014 05/02/2014 CGVEH-GLDRCP-00387 39.9617 -70.9058
2 SI20150110 01/11/2015 03/04/2015 CGVEH-GLDRCP-00387 40.0098 -70.3986
3 AT-31 10/14/2015 11/30/2015 CGVEH-GLDRCP-00387 40.07 -70.4152
4 AR1-07 04/04/2016 07/29/2016 CGVEH-GLDRCP-00387 39.9685 -70.5384
5 SI20170418 04/19/2017 07/02/2017 CGVEH-GLDRCP-00387 39.7836 -70.4657
6 AR-24 10/28/2017 01/03/2018 CGVEH-GLDRCP-00387 40.0318 -70.6204
7 AR-34 04/08/2019 06/18/2019 CGVEH-GLDRCP-00387 39.9681 -71
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

Review Images

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-GL387
Deployment: 1

Glider doesn't look like it sampled according to plan. This should be annotated.

By Lori Garzio, on 9/5/19

New Note

Metadata Start Date End Date Comment
CP05MOAS-GL387
 		7/13/16, 9:00 PM 7/28/16, 8:00 AM

The glider altimeter may have failed.

Id: 644 By: leila
Flag: not_available Exclude: No

CP05MOAS-GL387
 		5/26/19, 8:00 PM

Deployment 7: Glider's altimeter failed on 5/27/2019 so it will be limited to sampling the bottom line of the FZ box and to 500m until the end of the deployment.

Id: 1620 By: cdobson