3-D Single Point Velocity Meter

Reference Designator
CP02PMCI-WFP01-01-VEL3DK000
Start Depth
15
End Depth
104
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/CP02PMCI/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 KN217 04/16/2014 10/10/2014 CGMCP-02PMCI-00001 CGVEH-CWFPCP-10302 CGINS-VEL3DK-00037 40.2267 -70.8886 104 127
2 Review KN222 10/10/2014 12/15/2014 CGMCP-02PMCI-00002 CGVEH-CWFPCP-99102 CGINS-VEL3DK-00013 40.2265 -70.878 104 127
3 Review AT27 05/01/2015 10/15/2015 CGMCP-02PMCI-00003 CGVEH-CWFPCP-10302 CGINS-VEL3DK-00037 40.2267 -70.8888 105 128
4 Review AT31 10/15/2015 05/20/2016 CGMCP-02PMCI-00004 CGVEH-CWFPCP-10301 CGINS-VEL3DK-00035 40.2267 -70.8779 104 127
5 Review AR4 05/21/2016 05/30/2016 CGMCP-02PMCI-00005 CGVEH-CWFPCP-99102 CGINS-VEL3DK-00013 40.2266 -70.889 105 128
6 Review AR7-01 07/01/2016 10/02/2016 CGMCP-02PMCI-00006 CGVEH-CWFPCP-93601 CGINS-VEL3DK-00022 40.2269 -70.8894 104 127
7 Review AR8 10/03/2016 06/17/2017 CGMCP-02PMCI-00007 CGVEH-CWFPCP-99102 CGINS-VEL3DK-00013 40.2267 -70.8782 103 126
8 Review AR18 06/16/2017 11/07/2017 CGMCP-02PMCI-00008 CGVEH-CWFPCP-10302 CGINS-VEL3DK-00037 40.227 -70.8889 104 127
9 Review AR24 11/07/2017 04/11/2018 CGMCP-02PMCI-00009 CGVEH-CWFPCP-99101 CGINS-VEL3DK-00015 40.2266 -70.8782 102 125
10 Review AR28 04/11/2018 11/05/2018 CGMCP-02PMCI-00010 CGVEH-CWFPCP-10302 CGINS-VEL3DK-00037 40.2265 -70.8889 104 127
11 Review AR31 11/05/2018 04/18/2019 CGMCP-02PMCI-00011 CGVEH-CWFPCP-99101 CGINS-VEL3DK-00015 40.2267 -70.8783 103 126
12 Review AR34 04/17/2019 10/07/2019 CGMCP-02PMCI-00012 CGVEH-CWFPCP-10302 CGINS-VEL3DK-00037 40.2267 -70.8886 103 126
13 Review AR39 10/07/2019 06/12/2020 CGMCP-02PMCI-00013 CGVEH-CWFPCP-99101 CGINS-VEL3DK-00015 40.227 -70.8779 103 126
14 Review AR44 06/12/2020 CGMCP-02PMCI-00014 CGVEH-CWFPCP-10302 CGINS-VEL3DK-00037 40.2267 -70.889 104 127
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

New Note

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
Flag: fail Exclude: Yes

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

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

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
Flag: not_available Exclude: No

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
Flag: fail Exclude: Yes

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

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

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