Dissolved Oxygen

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

Dataset Reviews Last processed: 8/1/19, 1:07 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 245 243 0 0 0 0 283,362 10 2571 / 2629 Complete
2 recovered_wfp 356 354 0 0 0 0 229,825 10 2573 / 2657 1 1 Complete
3 recovered_wfp 440 339 0 99 0 0 401,898 10 2573 / 2589 1 1 Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison

Data Coverage

Deployment: 123

Lat/Lon Differences (km)

Deployment: 123
1 0.00
2 3.540.00
3 0.463.780.00

System Annotations

Metadata Start Date End Date Comment
11/16/15, 1:36 PM 1/11/18, 10:09 AM

Deployments 2 and 3: Data were not transmitted via satellite telemetry.

Id: 374 By: lgarzio

11/16/15, 1:36 PM 11/4/16, 8:00 PM

Deployment 2: At the initial recovery attempt of this mooring in Nov 2016, it was determined that the mooring had fallen and was not recovered. During the following cruise in Jan 2018, the mooring was successfully recovered on 2018-01-15T09:30:00.

Id: 130 By: lgarzio

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


Missing 3 months of data at the end of deployment 3 should be annotated.

By Lori Garzio, on 8/2/19

Deployment: 2

The estimated_oxygen_concentration values at the bottom of the WFP02 range and the top of the WFP03 are slightly offset for this deployment.

By Lori Garzio, on 8/5/19

Deployment: 2
5/23/16, 12:00 AM 11/5/16, 12:00 AM

Modify annotation ID 130 to indicate the time the mooring fell. According to the pressure data from the CTDMO, the mooring began to fall around 5/23/2016. Excluding data from final statistics.

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 slightly offset for this deployment.

By Lori Garzio, on 8/5/19

New Note