3-D Single Point Velocity Meter
- Reference Designator
- CP02PMCI-WFP01-01-VEL3DK000
- Review Status
- Review Complete
- Note
- Incorrect data: waiting on the correct algorithm from vendor. (see Annotation ID 1402)
- Depth
- 15 to 104m
- Class
- VEL3D (3-D Single Point Velocity Meter)
- Make / Model
- Nortek / Aquadopp II
Dataset Reviews Last processed: 6/24/19, 3:07 PM
| 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 | 147 | 0 | 0 | 4 | 30 | 2,497,524 | 104 / 106 | 1 | 2 | Complete | |||||
| 2 | telemetered | 66 | 49 | 0 | 16 | 0 | 0 | 768,980 | 104 / 104 | 3 | 3 | Complete | |||||
| 3 | recovered_wfp | 169 | 156 | 1 | 0 | 2 | 12 | 2,529,678 | 104 / 105 | 4 | Complete | ||||||
| 4 | recovered_wfp | 219 | 82 | 0 | 136 | 0 | 0 | 1,302,544 | 104 / 105 | 5 | 2 | Complete | |||||
| 5 | telemetered | 10 | 10 | 0 | 0 | 0 | 0 | 350,128 | 104 / 107 | 3 | 3 | Complete | |||||
| 6 | recovered_wfp | 94 | 93 | 0 | 0 | 0 | 0 | 1,634,316 | 104 / 103 | 2 | Complete | ||||||
| 7 | recovered_wfp | 258 | 257 | 0 | 0 | 0 | 0 | 8,889,713 | 104 / 105 | 6 | 2 | Complete | |||||
| 8 | recovered_wfp | 145 | 132 | 0 | 11 | 0 | 0 | 2,233,455 | 104 / 105 | 2 | Complete | ||||||
| 9 | recovered_wfp | 156 | 156 | 0 | 0 | 0 | 0 | 2,592,661 | 104 / 106 | 2 | Complete |
Test Notes
- fail: data found in another stream (gaps: [4] days: [30])
- no comparison: timestamps do not match
- no other streams for comparison
- fail: data found in another stream (gaps: [3] days: [13])
- fail: data found in another stream (gaps: [1] days: [137])
- pass unique test - ascending not tested
Data Coverage
| Deployment: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
|---|---|---|---|---|---|---|---|---|---|
| 83% | 92% | 37% | 99% | 100% | 91% | 100% | |||
| 74% | 100% |
Lat/Lon Differences (km)
| Deployment: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 0.00 | ||||||||
| 2 | 0.90 | 0.00 | |||||||
| 3 | 0.02 | 0.92 | 0.00 | ||||||
| 4 | 0.91 | 0.02 | 0.93 | 0.00 | |||||
| 5 | 0.04 | 0.94 | 0.02 | 0.94 | 0.00 | ||||
| 6 | 0.07 | 0.97 | 0.06 | 0.98 | 0.05 | 0.00 | |||
| 7 | 0.89 | 0.03 | 0.90 | 0.03 | 0.92 | 0.95 | 0.00 | ||
| 8 | 0.04 | 0.93 | 0.03 | 0.94 | 0.05 | 0.04 | 0.91 | 0.00 | |
| 9 | 0.89 | 0.02 | 0.90 | 0.03 | 0.92 | 0.95 | 0.01 | 0.91 | 0.00 |
System Annotations Show
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
CP02PMCI-WFP01-01-VEL3DK000 Method: telemetered |
4/16/14, 7:28 PM | 10/10/14, 8:02 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: 2080
By: swhite
|
|
CP02PMCI-WFP01-01-VEL3DK000 Method: telemetered Stream: vel3d_k_wfp_stc_instrument |
4/16/14, 7:32 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: 1649
By: swhite
|
|
|
CP02PMCI-WFP01-01-VEL3DK000 Method: recovered_wfp Stream: vel3d_k_wfp_instrument |
4/16/14, 7:32 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: 1650
By: swhite
|
|
|
CP02PMCI-WFP01-01-VEL3DK000 |
4/16/14, 9: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: 1402 By: swhite |
|
CP02PMCI-WFP01-01-VEL3DK000 Method: recovered_wfp |
10/11/14, 2:11 PM | 12/14/14, 7:00 PM |
Missing.
Id: 397
By: leila
|
|
CP02PMCI-WFP01-01-VEL3DK000 Method: telemetered |
10/15/15, 2:11 PM | 4/11/18, 9:46 AM |
Deployment 4-9: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.
Id: 2081
By: swhite
|
|
CP02PMCI-WFP01 |
12/15/15, 10:08 PM | 1/29/16, 7:00 PM |
The Wire-Following Profiler was intentionally converted into a fixed-depth instrument to prolong the battery endurance. Id: 230 By: leila |
|
CP02PMCI |
5/20/16, 8:18 PM | 5/30/16, 8:05 AM |
Recovered data are not available because the Wire-Following Profiler motor and PAR cables were swapped and the data are thus unreliable. Id: 228 By: leila |
|
CP02PMCI |
10/2/16, 1:30 PM | 10/2/16, 2:30 PM |
Telemetered data are sparse because telemetry schedule was irregular during this deployment. Id: 232 By: leila |
|
CP02PMCI-WFP01 |
2/7/17, 7:00 AM | 6/16/17, 11:00 PM |
Data transmission interrupted. Id: 605 By: leila |
|
CP02PMCI-WFP01-01-VEL3DK000 Method: telemetered Stream: vel3d_k_wfp_stc_instrument |
6/16/17, 3:55 PM | 4/11/18, 9:46 AM |
Deployments 8&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: 1719
By: areed
|
|
CP02PMCI-WFP01-01-VEL3DK000 Method: recovered_wfp Stream: vel3d_k_wfp_instrument |
6/16/17, 3:55 PM | 4/11/18, 9:46 AM |
Deployments 8&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: 1720
By: areed
|
|
CP02PMCI-WFP01 |
12/31/19, 7:00 PM | 6/12/20, 12:01 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: 1881 By: cdobson |
Review Notes
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
CP02PMCI-WFP01-01-VEL3DK000 |
Annotation ID 1402 needs to be updated when the algorithm is fixed. By Lori Garzio, on 6/24/19 |
||
|
CP02PMCI-WFP01-01-VEL3DK000 |
vel3d_k_pressure (dbar) is an array of all fill values for every deployment. By Lori Garzio, on 6/24/19 |
||
|
CP02PMCI-WFP01 |
12/15/15, 12:00 AM | 5/20/16, 7:14 PM |
Annotation ID 230: Deployment 4: WFP stopped profiling. Excluding from final data ranges. By Lori Garzio, on 6/24/19  |
|
CP02PMCI-WFP01-01-VEL3DK000 Deployment: 1 |
There are telemetered data available for several time ranges listed here where recovered_wfp aren't available. The data should be available in the recovered data stream: [['2014-05-09T00:00:00', '2014-05-14T23:00:00'], ['2014-05-27T00:00:00', '2014-06-01T23:00:00'], ['2014-06-14T00:00:00', '2014-06-25T23:00:00'], ['2014-07-14T00:00:00', '2014-07-19T23:00:00']] By Lori Garzio, on 6/24/19 |
||
|
CP02PMCI-WFP01-01-VEL3DK000 Deployment: 2 |
According to annotation ID 397, recovered data are missing. These data should be ingested or the annotation should be updated to indicate why the recovered data aren't available. By Lori Garzio, on 6/24/19 |
||
|
CP02PMCI-WFP01-01-VEL3DK000 Deployment: 3 |
There are telemetered data available for several time ranges listed here where recovered_wfp aren't available. The data should be available in the recovered data stream: [['2015-06-03T00:00:02', '2015-06-08T22:38:03'], ['2015-07-21T00:00:02', '2015-07-26T22:39:36'], ['2015-08-21T09:06:04', '2015-08-21T09:07:41']] By Lori Garzio, on 6/24/19 |
||
|
CP02PMCI-WFP01-01-VEL3DK000 Deployment: 4 |
There are telemetered data available for several time ranges listed here where recovered_wfp aren't available. The data should be available in the recovered data stream: [['2016-01-05T12:00:00', '2016-05-20T17:00:00']] By Lori Garzio, on 6/24/19 |
||
|
CP02PMCI-WFP01-01-VEL3DK000 Deployment: 5 |
The seawater velocity variables for this deployment are all arrays of fill values. There are several computed_provenance errors in the provenance_json file attached. By Lori Garzio, on 6/24/19 |