3-D Single Point Velocity Meter

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

Dataset Reviews Last processed: 12/18/18, 2:05 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 178 172 0 0 1 6 3,441,356 125 / 128 1 2 Complete
2 recovered_wfp 206 194 0 0 2 12 3,372,862 125 / 128 3 Complete
3 recovered_wfp 167 161 5 0 0 0 3,079,326 125 / 125 1 Complete
5 recovered_wfp 217 217 0 0 0 0 4,232,258 125 / 128 Complete
6 recovered_wfp 136 135 0 0 0 0 5,389,328 125 / 127 2 Complete
7 recovered_wfp 258 257 0 0 0 0 4,858,742 125 / 128 2 Complete
8 recovered_wfp 144 144 0 0 0 0 5,689,408 125 / 131 2 Complete
9 recovered_wfp 155 155 0 0 0 0 6,057,127 125 / 128 Complete
Data Ranges Review Images

Test Notes

  1. fail: data found in another stream (gaps: [1] days: [6])
  2. no comparison: timestamps do not match
  3. fail: data found in another stream (gaps: [2] days: [12])

Data Coverage

Deployment: 12356789
97%94%96%100%99%100%100%100%

Lat/Lon Differences (km)

Deployment: 12356789
1 0.00
2 0.890.00
3 0.070.870.00
5 0.070.900.030.00
6 0.890.070.870.910.00
7 0.070.930.060.030.930.00
8 14.5513.9714.4914.5114.0214.540.00
9 0.040.860.030.050.860.0714.510.00

System Annotations

Metadata Start Date End Date Comment
CP02PMCO-WFP01-01-VEL3DK000
Method: telemetered
4/13/14, 1:29 PM 10/7/14, 8:01 AM

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

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

CP02PMCO-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
4/13/14, 1:50 PM

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: 1651 By: swhite
Flag: suspect Exclude: No

CP02PMCO-WFP01-01-VEL3DK000
Method: recovered_wfp
Stream: vel3d_k_wfp_instrument
4/13/14, 1:50 PM

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: 1652 By: swhite
Flag: suspect Exclude: No

CP02PMCO-WFP01-01-VEL3DK000
4/13/14, 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: 1403 By: swhite

CP02PMCO-WFP01
Method: telemetered
7/21/14, 2:10 PM 10/6/14, 8:00 PM

Telemetry was interrupted and no data are available via telemetry due to a time out error. The data files were too large to write and the system run out of time before it could get them through the inductive modem.

Id: 711 By: leila

CP02PMCO-WFP01
12/6/14, 10:00 PM 4/30/15, 6:35 PM

The profiler is stuck at the bottom of its range.

Id: 712 By: leila

CP02PMCO
3/3/16, 5:40 AM 5/20/16, 8:09 AM

No telemetered data expected because communications were suspended after the battery was depleted.

Id: 233 By: leila

CP02PMCO-WFP01-01-VEL3DK000
Method: telemetered
5/20/16, 1:43 PM 11/6/17, 12:04 PM

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

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

CP02PMCO
9/5/16, 5:05 AM 10/2/16, 7:59 AM

No telemetered data expected because communication were lost after the passge of tropical storm Hermine.

Id: 234 By: leila

CP02PMCO-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
11/6/17, 8:11 PM 4/10/18, 3:11 PM

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

CP02PMCO-WFP01-01-VEL3DK000
Method: recovered_wfp
Stream: vel3d_k_wfp_instrument
11/6/17, 8:11 PM 4/10/18, 3:11 PM

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

CP02PMCO-WFP01-01-VEL3DK000
Method: telemetered
11/2/18, 4:28 PM 4/23/19, 12:12 PM

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

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

CP02PMCO-WFP01-01-VEL3DK000
1/31/19, 7:00 PM 4/23/19, 12:12 PM

Deployment 11: No telemetered data from WFP instruments expected from 2019-02-01 onward.

Id: 1615 By: cdobson

CP02PMCO
4/23/19, 5:00 PM 10/8/19, 8:02 AM

UPDATED 2020-02-18: WFP and ADCP data were collected during the deployment and are available as recovered datasets; Deployment 12: No telemetered data expected after 4/24/19. Pesumed to be profiling and WFP data should be available after recovery.

Id: 1578 By: cdobson

CP02PMCO-WFP01
12/31/19, 7:00 PM 6/10/20, 12:07 PM

Deployment 13: 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: 1882 By: cdobson

Review Notes

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

For deployments 1, 6, 7 and 8 telemetered and recovered data have different timestamps and so data comparison could not be performed.

By Leila Belabbassi, on 3/25/19

CP02PMCO-WFP01-01-VEL3DK000

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

By Lori Garzio, on 8/8/19

CP02PMCO-WFP01-01-VEL3DK000

Annotation ID 1403 needs to be updated when the algorithm is fixed.

By Lori Garzio, on 8/8/19

CP02PMCO-WFP01-01-VEL3DK000

There are several days during deployments 1, 2, and 3 where recovered_wfp data are not available but telemetered data are available. These data should be available in the recovered_wfp data streams.

By Lori Garzio, on 8/8/19

CP02PMCO-WFP01
12/6/14, 12:00 AM 5/2/15, 12:00 AM

annotation ID 712 should be updated by adding that data quality is bad for this time range.

By Leila Belabbassi, on 3/20/19

CP02PMCO-WFP01
12/6/14, 12:00 AM 5/2/15, 12:00 AM

bad data for CTD, DO, FLORT, VEL3D and PAR seen after 15 December 2014 to the end of the deployment.

example plot from CTD shown.

By Leila Belabbassi, on 3/21/19

CP02PMCO
Deployment: 8

Lat and Lon for deployment 8 are very far for what is the platform standard location. Please check?

see redmine help desk ticket # 13757 (https://redmine.oceanobservatories.org/issues/13757)

By Leila Belabbassi, on 3/19/19

New Note