Dissolved Oxygen

Reference Designator
Start Depth
End Depth
Current Status
Review Complete
DOSTA (Dissolved Oxygen Stable Response)
Science Discipline
Optode 4831
M2M Example
Method Data Stream Content Type
recovered_host dosta_abcdjm_glider_recovered Data Products Report M2M Stats Science
telemetered dosta_abcdjm_glider_instrument Data Products Report M2M Stats Science
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
2 Review AT-30-01 08/17/2015 08/27/2015 CGVGI-05MOAS-00000 CGVEH-GLDROO-00484 CGINS-DOSTAM-00324 59.86 -39.1317 1000 1000
3 Review AR-07-01 07/09/2016 10/19/2016 CGVGI-05MOAS-00000 CGVEH-GLDROO-00484 CGINS-DOSTAM-00324 59.8592 -39.1321 1000 1000
Metadata Start Date End Date Comment

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/31/19


Comparisons with the shipboard CTD casts were done for D0002 and D0003. The shipboard CTD cast data are corrected for temperature, salinity, and depth (Redmine 14230). The L2 DO data product (corrected for temperature, salinity and depth) is substantially lower for the glider compared to the shipboard data. This could be related to the issue of incorrect default salinity settings on some glider optodes (Redmine 13575). Comparison to the shipboard bottle data is outside the scope of this project. Note: the conversion from ml/l to umol/kg for the shipboard DO = DO (ml/l) * 44.661 / 1.025.

By Lori Garzio, on 3/8/19

Deployment: 2

Recovered data for deployment 2 should be ingested or annotated to explain why no recovered data are available for download. The ingest csv has a note that the glider was lost, but the glider was lost on deployment 3 not deployment 2.

By Lori Garzio, on 6/5/19

New Note

Metadata Start Date End Date Comment
8/17/15, 6:45 AM 8/26/15, 8:00 PM

Deployment 2: Deployed on 8/17/2015, recovered on 8/23/2015 at 12:26 UTC for ballast adjustment. Re-deployed at 12:40 UTC. Was recovered after 10 days due to rudder issues.

Id: 575 By: lgarzio

7/9/16, 6:32 AM 10/18/16, 6:06 PM

Glider went adrift and was not recovered. Only telemetered data are available.

Id: 164 By: lgarzio