Mobile Asset Controller
- Reference Designator
- CP05MOAS-GL340-00-ENG000000
- Start Depth
- 0
- End Depth
- 1,000
- Location
- Current Status
- Engineering
- M2M Example
- https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/CP05MOAS/GL340/00-ENG000000/metadata
| Method | Data Stream | Content | Type | |
|---|---|---|---|---|
| recovered_host | glider_eng_metadata_recovered | Metadata | Report M2M | Engineering |
| recovered_host | glider_eng_recovered | Engineering Data | Report M2M | Engineering |
| recovered_host | glider_eng_sci_recovered | Status Data | Report M2M | Engineering |
| recovered_host | glider_gps_position | GPS Position Data | Report M2M | Engineering |
| telemetered | glider_eng_metadata | Metadata | Report M2M | Engineering |
| telemetered | glider_eng_sci_telemetered | Status Data | Report M2M | Engineering |
| telemetered | glider_eng_telemetered | Engineering Data | Report M2M | Engineering |
| telemetered | glider_gps_position | GPS Position Data | Report M2M | Engineering |
| 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 |
| 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
|
|
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 |