3-D Single Point Velocity Meter

Reference Designator
CE09OSPM-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 540m
Class
VEL3D (3-D Single Point Velocity Meter)
Make / Model
Nortek / Aquadopp II

Dataset Reviews Last processed: 12/13/18, 2:17 AM

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 119 5 1 113 0 0 138,973 536 / 511 1 2 Complete
2 recovered_wfp 180 173 0 0 1 6 4,372,187 542 / 516 3 Complete
3 recovered_wfp 195 157 0 0 8 38 3,854,088 542 / 524 4 Complete
4 recovered_wfp 205 193 0 3 4 8 4,746,157 542 / 514 Complete
5 recovered_wfp 133 133 0 0 0 0 3,308,438 542 / 514 5 Complete
6 telemetered 203 23 0 180 0 0 834,586 540 / 518 6 6 Complete
7 recovered_wfp 175 175 0 0 0 0 7,035,791 533 / 506 7 8 Complete
8 recovered_wfp 174 174 0 0 0 0 5,888,430 533 / 516 Complete
9 recovered_wfp 182 181 0 1 0 0 6,089,522 542 / 509 9 Complete
Data Ranges Review Images

Test Notes

  1. fail: data found in another stream (gaps: [1] days: [5])
  2. no comparison: timestamps do not match
  3. fail: data found in another stream (gaps: [2] days: [7])
  4. fail: data found in another stream (gaps: [8] days: [38])
  5. fail: data found in another stream (gaps: [2] days: [2])
  6. no other streams for comparison
  7. pass unique test - ascending not tested
  8. fail: check ['Upward Mean Point Seawater Velocity']
  9. fail: data found in another stream (gaps: [1] days: [2])

Data Coverage

Deployment: 123456789
4%96%81%94%100%100%100%99%
11%

Lat/Lon Differences (km)

Deployment: 123456789
1 0.00
2 0.410.00
3 0.200.600.00
4 0.380.100.560.00
5 0.841.230.691.220.00
6 0.841.230.701.220.040.00
7 0.470.840.380.840.410.390.00
8 0.110.460.150.410.840.850.500.00
9 0.380.110.570.191.171.170.770.450.00

System Annotations

Metadata Start Date End Date Comment
CE09OSPM-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
4/17/14, 8:00 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: 1631 By: wingardc
Flag: suspect Exclude: No

CE09OSPM-WFP01-01-VEL3DK000
Method: recovered-wfp
Stream: vel3d_k_wfp_instrument
4/17/14, 8:00 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: 1632 By: wingardc
Flag: suspect Exclude: No

CE09OSPM-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
4/17/14, 8:00 PM 3/10/19, 8:00 PM

UPDATED, 2019-03-11: 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: 1400 By: lgarzio

CE09OSPM-WFP01-01-VEL3DK000
Method: recovered-wfp
Stream: vel3d_k_wfp_instrument
4/17/14, 8:00 PM 3/10/19, 8:00 PM

UPDATED, 2019-03-11: 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: 1662 By: wingardc

CE09OSPM-WFP01
Method: telemetered
4/29/14, 10:00 AM 8/14/14, 8:00 PM

The bulkhead connector for the PAR sensor failed and shorted the profiler power system to seawater, draining the profiler battery pack in fairly short order. No data is available for this time period.

Id: 1663 By: wingardc
Flag: not_available Exclude: No

CE09OSPM-WFP01
Method: recovered-wfp
4/29/14, 10:00 AM 8/14/14, 8:00 PM

The bulkhead connector for the PAR sensor failed and shorted the profiler power system to seawater, draining the profiler battery pack in fairly short order. No data is available for this time period.

Id: 1664 By: wingardc
Flag: not_available Exclude: No

CE09OSPM
Method: telemetered
12/6/15, 1:50 AM 5/6/16, 10:00 PM

The surface expression for the profiler mooring broke free during a storm event on December 06, 2015 and ended up drifting north to Vancouver Island where it was recovered. No further telemetered data will be available from this mooring or profiler system for this deployment.

Id: 1665 By: wingardc
Flag: not_available Exclude: No

CE09OSPM-WFP01
Method: recovered-wfp
9/21/16, 10:18 PM 4/12/17, 7:12 PM

The surface expression for the profiler mooring broke free during a storm event in October 2016. On March 13, 2017, the subsurface sphere came to the surface and drifted north towards Vancouver Island where it was recovered from the shore. The mooring wire was severed near the base and showed signs of abrasion and other damage consistent with a ship strike. The profiler was no longer on the wire and is presumed lost at sea. No recovered profiler data is available for this deployment.

Id: 1661 By: wingardc
Flag: not_available Exclude: No

CE09OSPM
Method: telemetered
10/14/16, 3:01 PM 4/12/17, 7:12 PM

UPDATED, 2017-03-13: The subsurface float came to the surface at 06:16 UTC and drifted north towards Vancouver Island where it was recovered. The mooring wire was severed and showed signs of abrasion and other damage consistent with a ship strike. The profiler was no longer attached to the wire and is presumed lost at sea. * The buoy of the offshore Washington profiler went adrift at sometime around noon local time October 14, 2016. The subsurface beacons have not reported, so it is likely that the stretch hose between the buoy and the subsurface float parted, just as it did last year. If this is the case, the profiler is continuing to collect data, but it is no longer able to telemeter data to shore.

Id: 925 By: michaesm
Flag: not_available Exclude: No

CE09OSPM-WFP01
Method: telemetered
7/10/17, 8:00 AM 10/3/17, 4:13 PM

At noon on July 10, 2017, the IMM port of the profiler mooring was turned off due to the incorrect configuration of the VEL3D-K. The instrument's sample rate was set too high, resulting in unusually large data files which caused a significant increase in the IMM telemetry time and an unsustainable power draw from the profiler battery pack. To insure the profiler continues to collect data over the course of the deployment, the IMM will remain off for the duration of the Spring/Summer 2017 deployment.

Id: 96 By: m.vardaro
Flag: not_available Exclude: No

CE09OSPM-WFP01
Method: telemetered
4/7/19, 10:23 PM 5/4/19, 5:22 AM

Battery pack on the profiler is getting low. To conserve power for profiling, data telemetry has been disabled.

Id: 1666 By: wingardc
Flag: not_available Exclude: No

CE09OSPM-WFP01
Method: recovered-wfp
4/10/19, 4:00 AM 5/4/19, 5:22 AM

Battery pack on the profiler was getting low. Sensors did not have enough power to fully operate (most noticeable in the VEL3D-K data streams), and the profiler did not have enough power to descend to the full operating depth. Stopped operating altogether on 2019-04-26 after completing 1728 profiles over the course of the deployment.

Id: 1667 By: wingardc
Flag: not_available Exclude: No

CE09OSPM-WFP01
Method: telemetered
10/11/19, 12:00 AM 12/31/19, 7:00 PM

Data indicates that profiler travel up the wire is periodically blocked near 150 m, keeping it from fully ascending during a profile. Suspect fouling on the wire is impeding travel.

Id: 1830 By: wingardc

CE09OSPM-WFP01
Method: telemetered
12/31/19, 7:00 PM

Due to a clock rollover issue, all WFPs ceased sampling on 2020-01-01. No further WFP data are being collected from this system. A resolution is being researched by the vendor.

Id: 1905 By: wingardc
Flag: not_operational Exclude: No

Review Notes

Metadata Start Date End Date Comment
CE09OSPM-WFP01

Deployment 6 for all instruments:
Update annotation ID # 925 to indicate that the profiler was lost at sea and no recovered data are expected.
Two other issues with telemetered data need to be mentioned:
(1) the gaps in the data.
(2) the change in the sampling rate.

Are the gaps in the data as a result of a change in the sampling rate?

By Leila Belabbassi, on 3/26/19

CE09OSPM-WFP01

Deployment 9 for all instruments except FLORT (instrument was not deployed):
The data missing at the end of the deployment in recovered_host are found in the telemetered stream. Are recovered_host data incomplete?

By Leila Belabbassi, on 3/26/19

CE09OSPM-WFP01

Deployment 1 for all instruments:
The data record ended long before the deployment end date. There is no annotation to explain what happened.

By Leila Belabbassi, on 3/28/19

CE09OSPM-WFP01-01-VEL3DK000

Data missing from the recovered_host stream are available in the telemetered stream for deployments 1-3, 5 and 9. This should be investigated and fixed.

By Lori Garzio, on 8/22/19

CE09OSPM-WFP01-01-VEL3DK000

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

By Lori Garzio, on 8/22/19

New Note