3-D Single Point Velocity Meter

Reference Designator
CP02PMUO-WFP01-01-VEL3DK000
Start Depth
15
End Depth
425
Location
Wire Following Profiler Body
Current Status
Review Complete
Class
VEL3D (3-D Single Point Velocity Meter)
Series
VEL3D-K
Science Discipline
Physical
Make
Nortek
Model
Aquadopp II
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/CP02PMUO/WFP01/01-VEL3DK000/metadata
Method Data Stream Content Type
recovered_wfp vel3d_k_wfp_instrument Data Products Report M2M Stats Science
recovered_wfp vel3d_k_wfp_metadata Metadata Report M2M Engineering
recovered_wfp vel3d_k_wfp_string String Data Report M2M Engineering
telemetered vel3d_k_wfp_stc_instrument Data Products Report M2M Stats Science
telemetered vel3d_k_wfp_stc_metadata Metadata Report M2M Engineering
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 Review KN214 11/23/2013 11/25/2013 CGMCP-02PMUO-00001 CGVEH-CWFPCP-93601 CGINS-VEL3DK-00022 39.9416 -70.7797 421 445
2 Review KN214 11/25/2013 04/14/2014 CGMCP-02PMUO-00002 CGVEH-CWFPCP-99102 CGINS-VEL3DK-00013 39.938 -70.7691 426 450
3 Review KN217 04/14/2014 10/05/2014 CGMCP-02PMUO-00003 CGVEH-CWFPCP-10304 CGINS-VEL3DK-00033 39.9424 -70.7801 428 452
4 Review KN222 10/05/2014 04/30/2015 CGMCP-02PMUO-00004 CGVEH-CWFPCP-99105 CGINS-VEL3DK-00011 39.943 -70.77 426 450
5 Review AT27 04/30/2015 10/13/2015 CGMCP-02PMUO-00005 CGVEH-CWFPCP-10304 CGINS-VEL3DK-00033 39.9416 -70.7809 428 452
6 Review AT31 10/13/2015 05/18/2016 CGMCP-02PMUO-00006 CGVEH-CWFPCP-99105 CGINS-VEL3DK-00011 39.9434 -70.7704 420 444
7 Review AR4 05/18/2016 10/01/2016 CGMCP-02PMUO-00007 CGVEH-CWFPCP-10304 CGINS-VEL3DK-00033 39.9421 -70.78 426 450
8 Review AR8 10/02/2016 06/07/2017 CGMCP-02PMUO-00008 CGVEH-CWFPCP-99105 CGINS-VEL3DK-00212 39.9394 -70.7708 423 447
9 Review AR18 06/07/2017 11/11/2017 CGMCP-02PMUO-00009 CGVEH-CWFPCP-10304 CGINS-VEL3DK-00033 39.9412 -70.7804 425 449
10 Review AR24 11/11/2017 04/10/2018 CGMCP-02PMUO-00010 CGVEH-CWFPCP-10301 CGINS-VEL3DK-00035 39.9387 -70.7701 423 447
11 Review AR28 04/09/2018 11/07/2018 CGMCP-02PMUO-00011 CGVEH-CWFPCP-10304 CGINS-VEL3DK-00033 39.9419 -70.779 426 450
12 Review AR31 11/07/2018 04/22/2019 CGMCP-02PMUO-00012 CGVEH-CWFPCP-10301 CGINS-VEL3DK-00035 39.9416 -70.7796 427 451
13 Review AR34 04/23/2019 10/14/2019 CGMCP-02PMUO-00013 CGVEH-CWFPCP-10304 CGINS-VEL3DK-00033 39.9417 -70.7804 425 449
14 Review AR39 10/14/2019 06/09/2020 CGMCP-02PMUO-00014 CGVEH-CWFPCP-10301 CGINS-VEL3DK-00035 39.9419 -70.7796 425 449
15 Review AR44 06/09/2020 CGMCP-02PMUO-00015 CGVEH-CWFPCP-10304 CGINS-VEL3DK-00033 39.9429 -70.7709 419 443
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

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