CTD
- Reference Designator
- CP05MOAS-GL376-03-CTDGVM000
- Start Depth
- 0
- End Depth
- 1,000
- Location
- Current Status
- Review Complete
- M2M Example
- https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/CP05MOAS/GL376/03-CTDGVM000/metadata
| Method | Data Stream | Content | Type | |
|---|---|---|---|---|
| recovered_host | ctdgv_m_glider_instrument_recovered | Data Products | Report M2M Stats | Science |
| telemetered | ctdgv_m_glider_instrument | Data Products | Report M2M Stats | Science |
| 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-GL376-03-CTDGVM000 |
Comparisons with the shipboard CTD casts were done for D0001, D0003, D0005, D0007, and D0008. The available science parameter values and patterns are comparable between the glider and CTD cast, however further analysis using the shipboard bottle data should be conducted. This is outside the scope of this project. By Lori Garzio, on 3/13/19 |
||
|
CP05MOAS-GL376 Deployment: 1 |
11/15/14, 12:00 AM | 12/13/14, 12:00 AM |
The data at the end of the deployment (when the glider was drifting/stuck at the surface?) should be annotated as suspect. By Lori Garzio, on 5/7/19  |
|
CP05MOAS-GL376 Deployment: 3 |
11/15/15, 12:00 AM | 11/30/15, 12:00 AM |
The sampling pattern for all instruments changed on 11/15/2015. This should be annotated. By Lori Garzio, on 5/7/19  |
|
CP05MOAS-GL376 Deployment: 4 |
Glider doesn't look like it sampled according to plan. This dataset should be annotated. By Lori Garzio, on 5/7/19  |
||
|
CP05MOAS-GL376-03-CTDGVM000 Deployment: 8 |
Suspect profile in the middle of the deployment. By Lori Garzio, on 5/7/19  |
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
CP05MOAS-GL376 |
5/6/15, 7:57 AM | 5/13/15, 9:55 PM |
Deployment 2: Glider experienced an air bladder leak shortly after deployment and needed to be recovered; no data are expected for this deployment. Id: 2039 By: cdobson |
|
CP05MOAS-GL376 |
1/21/16, 10:15 AM | 2/2/16, 9:06 AM |
Deployment 4: Glider lost its rudder in a storm and could no longer steer properly so it was recovered early. Id: 2040 By: cdobson |
|
CP05MOAS-GL376 |
4/19/17, 4:43 PM | 4/19/17, 11:30 PM |
Deployment 6: Glider was deployed for a test deployment and recovered shortly after. No data are expected for this deployment. Id: 2041 By: cdobson |
|
CP05MOAS-GL376 Method: telemetered |
9/25/18, 6:00 PM | 10/1/18, 9:00 AM |
Deployment 9: Glider was recovered early on 2018-10-01 1300 UTC. The glider sustained damage to the rudder during a routine surface interval on 2018-09-26 and subsequently lost steering control. The root cause is not yet known. Id: 1532 By: cdobson |
|
CP05MOAS-GL376 |
6/18/19, 7:36 PM | 6/26/19, 2:45 PM |
Deployment 10: Glider was experiencing telemetry issues and needed to be recovered early. Id: 2042 By: cdobson |