3-D Single Point Velocity Meter

Reference Designator
CP01CNPM-WFP01-01-VEL3DK000
Review Status
Review Complete
Note
Incorrect data: waiting on the correct algorithm from vendor. (see Annotation ID 1401)
Depth
15 to 70m
Class
VEL3D (3-D Single Point Velocity Meter)
Make / Model
Nortek / Aquadopp II

Dataset Reviews Last processed: 12/18/18, 1:53 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 158 158 0 0 0 0 3,147,444 104 / 116 Complete
Data Ranges Review Images

Test Notes

All good!

Data Coverage

Deployment: 1
100%

Lat/Lon Differences (km)

Deployment: 1
1 0.00

System Annotations

Metadata Start Date End Date Comment
CP01CNPM-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
11/6/17, 9:55 AM

During descending profiles, the vertical velocity estimates may be incorrect due to interference with beam 3 measurements arising from the nearby CTD sensor. Users should cross-compare these vertical velocity estimates with those derived from the CTD pressure record to determine profiles of possible concern. Good vertical velocity estimates will closely align with the CTD derived estimates. Regardless, there should be minimal impact on the estimates of the horizontal velocities. However, care should be taken with these estimates to confirm this conclusion.

Id: 1647 By: swhite
Flag: suspect Exclude: No

CP01CNPM-WFP01-01-VEL3DK000
Method: recovered_wfp
Stream: vel3d_k_wfp_instrument
11/6/17, 9:55 AM

During descending profiles, the vertical velocity estimates may be incorrect due to interference with beam 3 measurements arising from the nearby CTD sensor. Users should cross-compare these vertical velocity estimates with those derived from the CTD pressure record to determine profiles of possible concern. Good vertical velocity estimates will closely align with the CTD derived estimates. Regardless, there should be minimal impact on the estimates of the horizontal velocities. However, care should be taken with these estimates to confirm this conclusion.

Id: 1648 By: swhite
Flag: suspect Exclude: No

CP01CNPM-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
11/6/17, 9:55 AM 4/12/18, 8:53 AM

Deployment 1; During the times indicated by the start and end times of this annotation, the VEL3D instrument on the Profiler contained a firmware bug which caused beam 3 (downward-facing) to be on during ascents, and beam 1 (upward-facing) to be on during descents, instead of vice versa. Therefore the issue of incorrect vertical velocity estimates due to interference with the CTD noted in a previous annotation will affect the ascending profiles rather than the descending profiles.

Id: 1717 By: areed
Flag: suspect Exclude: No

CP01CNPM-WFP01-01-VEL3DK000
Method: recovered_wfp
Stream: vel3d_k_wfp_instrument
11/6/17, 9:55 AM 4/12/18, 8:53 AM

Deployment 1; During the times indicated by the start and end times of this annotation, the VEL3D instrument on the Profiler contained a firmware bug which caused beam 3 (downward-facing) to be on during ascents, and beam 1 (upward-facing) to be on during descents, instead of vice versa. Therefore the issue of incorrect vertical velocity estimates due to interference with the CTD noted in a previous annotation will affect the ascending profiles rather than the descending profiles.

Id: 1718 By: areed
Flag: suspect Exclude: No

CP01CNPM-WFP01-01-VEL3DK000
11/6/17, 2:00 PM 2/14/19, 7:00 PM

UPDATED, 2020-04-15: Corrected algorithm has been uploaded to the system and is active. * The algorithm supplied by the vendor to calculate water velocities is incorrect. Corrected code is currently in review.

Id: 1401 By: swhite

CP01CNPM-WFP01
12/31/18, 7:00 PM 2/6/19, 7:00 PM

Deployment 2: The WFP slid up the wire between profiles on various dates including 2019-01-01, 2019-01-29, and from 2019-02-05 through 2019-02-07.

Id: 1623 By: cdobson

CP01CNPM-WFP01
2/10/19, 7:00 PM 2/17/19, 7:00 PM

Deployment 2: The WFP becamestuck at 25m from 2019-02-11 through 2019-02-18.

Id: 1622 By: cdobson

CP01CNPM-WFP01
2/20/19, 7:00 PM 4/4/19, 8:07 AM

Deployment 2: Telemetry of data from the WFP ceased on 2019-02-21.

Id: 1621 By: cdobson

CP01CNPM-WFP01
12/2/19, 7:00 PM 6/14/20, 8:23 AM

Deployment 3: Starting 12/03/2019 WFP01 was unable to complete full range descending profiles.

Id: 1842 By: cdobson
Flag: not_operational Exclude: No

CP01CNPM-WFP01
12/31/19, 7:00 PM

Deployment 3: 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: 1879 By: cdobson

Review Notes

Metadata Start Date End Date Comment
CP01CNPM-WFP01-01-VEL3DK000

Annotation ID 1401 needs to be updated when the corrected code is provided.

By Lori Garzio, on 8/8/19

CP01CNPM

system missing global ranges for all parameters because the platform is not listed in the data_qc_global_range_values.csv

By Leila Belabbassi, on 3/15/19

New Note