3-D Single Point Velocity Meter

Reference Designator
CP02PMUO-WFP01-01-VEL3DK000
Review Status
Review Complete
Note
Velocity data from profilers were run through the automated QC tests, but were not plotted or reviewed visually.
Depth
15 to 425m
Class
VEL3D (3-D Single Point Velocity Meter)
Make / Model
Nortek / Aquadopp II

Dataset Reviews Last processed: 8/21/19, 7:26 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 telemetered 3 2 0 0 0 0 21,160 425 / 86 1 1 Complete
2 recovered_wfp / Complete
3 recovered_wfp 175 174 0 0 1 1 1,973,431 425 / 428 2 Complete
4 recovered_wfp 208 123 0 79 1 6 2,478,033 425 / 425 Complete
5 recovered_wfp 167 155 0 0 2 12 2,818,223 425 / 427 3 Complete
6 telemetered 219 3 0 215 0 0 39,284 425 / 423 1 1 Complete
7 recovered_wfp 137 136 0 0 0 0 4,800,916 425 / 428 2 Complete
8 recovered_wfp 249 249 0 0 0 0 11,528,692 425 / 223 4 2 Complete
9 recovered_wfp 158 158 0 0 0 0 3,333,514 425 / 428 2 Complete
10 recovered_wfp 151 150 0 0 0 0 1,873,925 425 / 428 Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison
  2. no comparison: timestamps do not match
  3. fail: data found in another stream (gaps: [2] days: [12])
  4. pass unique test - ascending not tested

Data Coverage

Deployment: 12345678910
99%59%93%99%100%100%99%
67%1%

Lat/Lon Differences (km)

Deployment: 12345678910
1 0.00
3 0.100.00
4 0.840.870.00
5 0.100.110.940.00
6 0.820.840.060.920.00
7 0.060.030.860.090.830.00
8 0.800.860.410.900.450.840.00
9 0.070.140.910.060.890.110.840.00
10 0.00

System Annotations

Metadata Start Date End Date Comment
CP02PMUO-WFP01-01-VEL3DK000
Method: telemetered
11/23/13, 10:50 AM 4/14/14, 5:31 PM

Deployemt 1-2: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.

Id: 2088 By: swhite
Flag: fail Exclude: Yes

CP02PMUO-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
11/23/13, 10:50 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: 1655 By: swhite
Flag: suspect Exclude: No

CP02PMUO-WFP01-01-VEL3DK000
Method: recovered_wfp
Stream: vel3d_k_wfp_instrument
11/23/13, 10:50 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: 1656 By: swhite
Flag: suspect Exclude: No

CP02PMUO-WFP01-01-VEL3DK000
11/23/13, 11:00 AM 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: 1405 By: swhite

CP02PMUO-WFP01
11/23/13, 11:00 AM 11/24/13, 3:28 PM

Only few records available. The Wire-Following Profiler failed after few days and had to be recovered.

Id: 732 By: leila

CP02PMUO-WFP01
11/24/13, 3:28 PM 11/24/13, 7:00 PM

The Wire-Following Profiler was not performing correctly because of visible damage observed when recovered.

Id: 239 By: leila
Flag: not_operational Exclude: No

CP02PMUO-WFP01
11/25/13, 3:00 PM 4/14/14, 5:31 PM

All communication to the Wire-Following Profiler were lost and no data are expected.

Id: 678 By: leila
Flag: not_operational Exclude: No

CP02PMUO-WFP01-01-VEL3DK000
11/25/13, 3:58 PM 4/14/14, 5:31 PM

Data not recoverable.

Id: 554 By: leila

CP02PMUO-WFP01
1/27/15, 4:00 AM 4/29/15, 8:00 PM

Telemetered data end on 27 Jan 2015.

Id: 733 By: leila

CP02PMUO-WFP01
2/3/15, 7:34 AM 2/12/15, 1:00 AM

Surface buoy mal functioning.

Id: 735 By: leila

CP02PMUO-WFP01
2/12/15, 4:12 PM 4/29/15, 8:00 PM

The surface buoy departed and had to be recovered.

Id: 736 By: leila

CP02PMUO-WFP01
10/2/15, 2:00 AM 10/13/15, 9:04 AM

Telemetered data end on 2 Oct 2015.

Id: 734 By: leila

CP02PMUO-WFP01
10/13/15, 3:12 PM 5/18/16, 8:20 AM

The Wire-Following Profiler failed.

Id: 428 By: leila
Flag: not_available Exclude: No

CP02PMUO-WFP01-01-VEL3DK000
Method: telemetered
5/18/16, 5:17 PM 11/11/17, 7:45 AM

Deployment 7-9: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.

Id: 2089 By: swhite
Flag: fail Exclude: Yes

CP02PMUO-WFP01
8/18/16, 5:11 AM 8/23/16, 5:00 AM

The Wire-Following Profiler is stuck at the top of its range. The problem is assumed to be related to fouling of the line.

Id: 43

CP02PMUO-WFP01
9/6/16, 5:13 AM 10/1/16, 5:05 AM

The Wire-Following Profiler is stuck at the top of its range. The problem is assumed to be related to fouling of the line.

Id: 44

CP02PMUO-WFP01
10/23/16, 8:06 AM 6/7/17, 5:05 AM

The Wire-Following Profiler is stuck at the top of its range. The problem is assumed to be related to fouling of the line.

Id: 45 By: leila

CP02PMUO-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
11/11/17, 3:42 PM 4/10/18, 6:15 AM

Deployment 10; 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: 1727 By: areed
Flag: suspect Exclude: No

CP02PMUO-WFP01-01-VEL3DK000
Method: recovered_wfp
Stream: vel3d_k_wfp_instrument
11/11/17, 3:42 PM 4/10/18, 6:15 AM

Deployment 10; 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: 1728 By: areed
Flag: suspect Exclude: No

CP02PMUO-WFP01
1/5/18, 10:00 AM 4/10/18, 6:15 AM

Deployment 10: The Wire-Following Profiler is stuck at the top of its range.

Id: 939 By: leila

CP02PMUO-WFP01-01-VEL3DK000
Method: telemetered
4/9/18, 7:28 PM 11/7/18, 8:00 AM

Deployment 11: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.

Id: 2090 By: swhite
Flag: fail Exclude: Yes

CP02PMUO-WFP01
6/17/19, 8:00 PM 10/14/19, 8:01 AM

Deployment 13: WFP is likely stuck and profiles became erratic starting 2019-06-18.

Id: 1626 By: cdobson

CP02PMUO-WFP01
12/31/19, 7:00 PM 6/9/20, 12:09 PM

Deployment 14: 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: 1884 By: cdobson

Review Notes

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

vel3d_k_pressure (dbar) is an array of all fill values for every deployment.

By Lori Garzio, on 8/23/19

CP02PMUO-WFP01
11/23/13, 3:50 PM 11/25/13, 12:00 AM

Deployment 1: suspect data - see annotation IDs 239 and 732

By Lori Garzio, on 8/23/19

CP02PMUO-WFP01
2/3/15, 12:00 AM 4/30/15, 1:00 AM

Deployment 4: surface buoy malfunctioned and then detached from the mooring at the end of the deployment (annotation IDs 735 and 736) - suspect data.

By Lori Garzio, on 8/23/19

CP02PMUO-WFP01
8/20/15, 12:00 AM 10/13/15, 1:04 PM

Deployment 5: Suspect data

By Lori Garzio, on 8/23/19

CP02PMUO-WFP01-01-VEL3DK000
Deployment: 1

Seawater velocities are all fill values for this deployment

By Lori Garzio, on 8/23/19

CP02PMUO-WFP01-01-VEL3DK000
Deployment: 5

Data were found in the telemetered data stream but were not in the recovered data stream for 2 time periods: 2015-06-06T00:00:02 to 2015-06-11T21:32:41 and 2015-08-17T00:00:02 t0 2015-08-22T21:05:29.

By Lori Garzio, on 8/23/19

New Note