Mobile Asset Controller
- Reference Designator
- CP05MOAS-GL339-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/GL339/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-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  |
| 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 |