3-D Single Point Velocity Meter

Reference Designator
Review Status
Review Complete
Velocity data from profilers were run through the automated QC tests, but were not plotted or reviewed visually.
310 to 2,093m
VEL3D (3-D Single Point Velocity Meter)
Make / Model
Falmouth Scientific / ACM-Plus

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 2,720,259 1 2174 / 2213 Complete
2 recovered_wfp 352 345 6 0 0 0 3,294,765 1 2093 / 2110 Complete
3 recovered_wfp 394 386 0 4 4 4 3,785,770 1 2102 / 2124 1 Complete
4 recovered_wfp 379 191 0 187 0 0 3,250,990 1 / 2098 2 Complete
5 recovered_wfp / Complete
Data Ranges Review Images

Test Notes

  1. fail: data found in another stream (gaps: [3] days: [3])
  2. missing: ['pressure']

Data Coverage

Deployment: 12345

Lat/Lon Differences (km)

Deployment: 12345
1 0.00
2 0.980.00

System Annotations

Metadata Start Date End Date Comment
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

1/10/17, 5:47 AM 7/16/17, 11:20 AM

Deployment 4: Profiler failed.

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

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

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

Deployment 5: Instrument was not functional at deployment.

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

9/25/19, 8:00 PM

Deployment 7: No telemetered data are expected from any instruments on the upper WFP after 2019-09-26. These data should be avaible upon recovery.

Id: 2017 By: cdobson

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: 1886 By: cdobson

Review Notes

Metadata Start Date End Date Comment

Deployment 1: profiler stopped ascending to the minimum depth in the second half of the deployment.

By Lori Garzio, on 8/7/19


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
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: 4

Missing the pressure coordinate for this deployment.

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