Dissolved Oxygen

Reference Designator
Review Status
Review Complete
2,100 to 4,038m
DOSTA (Dissolved Oxygen Stable Response)
Make / Model
Aanderaa / Optode 4330

Dataset Reviews Last processed: 8/2/19, 3:02 PM

QC Check Info
Dep. Preferred Method Stream DD FD SG EG Gaps GD TS Rate (s) Pressure Comp. Time Order Valid Data Missing Data Data Comp. Missing Coords. Review
1 recovered_wfp 324 323 0 0 0 0 281,320 10 4061 / 4142 1 Complete
2 recovered_wfp 352 288 6 57 0 0 339,846 10 4038 / 4102 2 Complete
3 recovered_wfp 394 393 0 0 1 1 344,321 10 4070 / 4142 Complete
4 recovered_wfp 379 378 1 0 0 0 330,058 10 / 4064 1 Complete
5 recovered_wfp 377 376 0 0 0 0 314,425 10 / 4068 3 3 Complete
Data Ranges Review Images

Test Notes

  1. fail: check ['DO - Pressure Temp Sal Corrected']
  2. missing: ['pressure']
  3. no other streams for comparison

Data Coverage

Deployment: 12345

Lat/Lon Differences (km)

Deployment: 12345
1 0.00
2 0.980.00
5 9.939.099.148.960.00

System Annotations

Metadata Start Date End Date Comment
7/26/13, 11:02 AM 7/16/17, 2:04 AM

There is a substantial change in dissolved oxygen measurements reported by this instrument between deployments 3 and 4. A Subject Matter Expert compared the profiler data to data from the most recent U.S. GO-SHIP occupation of P16N (2015) and suggested that data from deployment 3 are suspect (the external dataset more closely aligns with data from deployment 4). Additionally, profiler data from deployment 1 more closely resemble data from deployment 3, so those data are also suspect. We have not independently verified the analysis, investigation is pending (Redmine 13505).

Id: 1444 By: lgarzio

6/20/14, 11:28 PM 6/21/14, 10:14 PM

Deployment 2: Platform was deployed on 6/16/2014, recovered on 6/21/2014 at 03:28 UTC due to firmware issue and re-deployed with updated firmware on 6/22/2014 at 02:14 UTC

Id: 580 By: lgarzio
Flag: not_operational Exclude: No

4/5/15, 1:46 AM 6/1/15, 8:00 PM

Deployment 2: Profiler failed due to depleted battery.

Id: 715 By: lgarzio

7/15/17, 5:25 PM 7/26/18, 6:15 PM

Deployment 5: Telemetered data are not available for this deployment because gliders were not deployed.

Id: 140 By: lgarzio

12/31/19, 7:00 PM

Deployment 7: Due to a clock rollover issue, all WFPs have ceased sampling on 1/1/2020. No WFP data are being collected after this date. A resolution is being researched by the vendor.

Id: 1887 By: cdobson

Review Notes

Metadata Start Date End Date Comment

I submitted a helpdesk question on 11/12/2018 regarding an offset between recovered and telemetered data for all global HYPMs: "There appears to be a substantial offset between data with the same timestamps from recovered_wfp and telemetered methods for all deployments of all global WFP CTDs, and I have included information from two representative deployments of two different profilers as examples. It looks like the values recorded for the first common timestamp are exactly the same, and as the profiler moves along in time the offset between the values recorded for the same timestamp become increasingly more offset. Then, the profiler reaches the end of the profile (either at its shallowest or deepest point), resets, and the pattern begins again. This is most easily seen in the pressure data, but there is an offset for all science parameters.

GI02HYPM-WFP02-04-CTDPFL000 deployment 1
GP02HYPM-WFP02-04-CTDPFL000 deployment 3

The *_intersect.csv files attached contain data where recovered and telemetered timestamps intersect. For each timestamp and science parameter there are recorded values (from .nc files downloaded from the system) and the difference. For each parameter, the difference between the values at the bottom and top of the profiler's range are exactly zero, and (particularly for pressure) the differences steadily increase until they are reset at zero at the bottom/top of the profile. This pattern continues throughout the deployment. The plots attached are zoomed in to one upcast and one downcast, and highlight the offset in the data between the two methods."

Redmine 13743

By Lori Garzio, on 8/8/19

7/3/16, 2:05 AM 7/26/18, 10:15 PM

Deployments 4 and 5 don't have deployment depths defined in asset management.

By Lori Garzio, on 1/3/19

Deployment: 2

No data expected - profiler failed (annotation ID 715).

By Lori Garzio, on 8/7/19

Deployment: 2
6/16/14, 2:15 AM 6/22/14, 12:00 PM

Excluding data from the beginning of deployment 2 from the final statistics as the mooring was recovered and re-deployed (annotation ID 580)

By Lori Garzio, on 1/3/19

Deployment: 3

The estimated_oxygen_concentration values at the bottom of the WFP02 range and the top of the WFP03 are offset for this deployment. This is consistent with the observation that deployment 3 data for WFP03 could be suspect (see annotation ID 1444).

By Lori Garzio, on 8/7/19

Deployment: 5
7/15/17, 9:25 PM 7/26/18, 10:15 PM

The mooring was deployed 9 - 10 km from the location of the previous 4 deployments of this mooring. If this location is correct, the platform should be annotated to inform the users as to why the deployment location changed.

By Lori Garzio, on 1/2/19

New Note