3-D Single Point Velocity Meter

Reference Designator
GI02HYPM-WFP02-05-VEL3DL000
Review Status
Review Complete
Note
Velocity data from profilers were run through the automated QC tests, but were not plotted or reviewed visually.
Depth
240 to 2,592m
Class
VEL3D (3-D Single Point Velocity Meter)
Make / Model
Falmouth Scientific / ACM-Plus

Dataset Reviews Last processed: 8/1/19, 5:49 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 340 335 0 4 0 0 4,097,809 1 2573 / 2614 Complete
2 recovered_wfp 336 314 0 17 2 3 3,769,698 1 2592 / 2585 1 1 Complete
3 recovered_wfp 396 366 0 29 0 0 4,293,884 1 2573 / 2540 Complete
4 recovered_wfp 315 255 0 57 1 2 2,922,261 1 2573 / 2565 Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison

Data Coverage

Deployment: 1234
99%93%92%81%

Lat/Lon Differences (km)

Deployment: 1234
1 0.00
2 2.350.00
3 0.751.980.00
4 2.790.442.400.00

System Annotations

Metadata Start Date End Date Comment
GI02HYPM-WFP02-05-VEL3DL000
9/11/14, 8:01 PM 8/16/15, 6:54 AM

Deployment 1: At recovery, the instrument was found mounted 90 degrees clockwise from how it should have been mounted.

Id: 682 By: lgarzio

GI02HYPM-WFP02
6/28/16, 2:10 AM 7/15/16, 8:00 PM

Deployment 2: Profiler failed.

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

GI02HYPM-WFP02
7/12/17, 3:30 AM 8/10/17, 6:18 AM

Deployment 3: Profiler failed.

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

GI02HYPM-WFP02
12/31/19, 7:00 PM

Deployment 6: 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: 1888 By: cdobson

Review Notes

Metadata Start Date End Date Comment
GI02HYPM-WFP02

Missing data at the end of deployment 4 should be annotated.

By Lori Garzio, on 8/5/19

GI02HYPM

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.

Examples:
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/5/19

New Note