3-D Single Point Velocity Meter

Reference Designator
CP04OSPM-WFP01-01-VEL3DK000
Start Depth
15
End Depth
427
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/CP04OSPM/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/15/2014 10/04/2014 CGMCP-04OSPM-00001 CGVEH-CWFPCP-10303 CGINS-VEL3DK-00036 39.9379 -70.8869 431 453
2 Review KN222 10/04/2014 04/29/2015 CGMCP-04OSPM-00002 CGVEH-CWFPCP-93601 CGINS-VEL3DK-00003 39.9415 -70.8784 428 450
3 Review AT27 04/29/2015 10/12/2015 CGMCP-04OSPM-00003 CGVEH-CWFPCP-10303 CGINS-VEL3DK-00036 39.943 -70.8854 415 436
4 Review AT31 10/12/2015 05/19/2016 CGMCP-04OSPM-00004 CGVEH-CWFPCP-93601 CGINS-VEL3DK-00022 39.9356 -70.88 412 458
5 Review AR4 05/19/2016 09/28/2016 CGMCP-04OSPM-00005 CGVEH-CWFPCP-10303 CGINS-VEL3DK-00036 39.9432 -70.8867 417 438
6 Review AR8 10/01/2016 06/01/2017 CGMCP-04OSPM-00006 CGVEH-CWFPCP-10301 CGINS-VEL3DK-00035 39.9365 -70.8802 412 458
7 Review AR18 06/06/2017 11/09/2017 CGMCP-04OSPM-00007 CGVEH-CWFPCP-10303 CGINS-VEL3DK-00036 39.9431 -70.8867 415 436
8 Review AR24 11/09/2017 04/09/2018 CGMCP-04OSPM-00008 CGVEH-CWFPCP-99105 CGINS-VEL3DK-00212 39.9347 -70.8802 409 455
9 Review AR28 04/09/2018 11/08/2018 CGMCP-04OSPM-00009 CGVEH-CWFPCP-10303 CGINS-VEL3DK-00036 39.9429 -70.8855 414 435
10 Review AR31 11/06/2018 04/22/2019 CGMCP-04OSPM-00010 CGVEH-CWFPCP-99105 CGINS-VEL3DK-00212 39.9366 -70.8793 407 453
11 Review AR34 04/22/2019 10/13/2019 CGMCP-04OSPM-00011 CGVEH-CWFPCP-10303 CGINS-VEL3DK-00036 39.9435 -70.8862 414 435
12 Review AR39 10/13/2019 06/08/2020 CGMCP-04OSPM-00012 CGVEH-CWFPCP-99105 CGINS-VEL3DK-00212 39.9356 -70.8803 405 451
13 Review AR44 06/08/2020 CGMCP-04OSPM-00013 CGVEH-CWFPCP-10303 CGINS-VEL3DK-00036 39.9431 -70.886 417 438
Metadata Start Date End Date Comment
CP04OSPM-WFP01-01-VEL3DK000

Annotation ID 1407 needs to be updated when the code is fixed

By Lori Garzio, on 8/26/19

CP04OSPM-WFP01-01-VEL3DK000

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

By Lori Garzio, on 8/26/19

CP04OSPM-WFP01
9/26/16, 12:00 AM 9/28/16, 1:25 PM

Deployment 5: suspect data at 0 dbar at the very end of the deployment

By Lori Garzio, on 8/26/19

CP04OSPM-WFP01-01-VEL3DK000
Deployment: 1

Data were found in the telemetered data stream but were not in the recovered data stream for 2 time periods: 2014-04-15T20:00:00 to 2014-04-20T21:00:00 and 2014-07-14T00:00:00 to 2014-07-19T22:00:00.

By Lori Garzio, on 8/26/19

CP04OSPM-WFP01-01-VEL3DK000
Deployment: 4

According to annotation ID 569, recovered_wfp data are missing for this deployment. The raw data files should be loaded to the raw data server and ingested, or the dataset should be annotated to explain why recovered data aren't available.

By Lori Garzio, on 8/26/19

CP04OSPM-WFP01-01-VEL3DK000
Deployment: 8

Data were found in the telemetered data stream but were not in the recovered data stream from 2017-12-25T00:00:02 to 2017-12-30T21:31:11.

By Lori Garzio, on 8/26/19

New Note

Metadata Start Date End Date Comment
CP04OSPM-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
4/15/14, 2:24 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: 1659 By: swhite
Flag: suspect Exclude: No

CP04OSPM-WFP01-01-VEL3DK000
Method: telemetered
4/15/14, 2:48 PM 10/4/14, 8:30 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: 2091 By: swhite
Flag: fail Exclude: Yes

CP04OSPM-WFP01-01-VEL3DK000
Method: recovered_wfp
Stream: vel3d_k_wfp_instrument
4/15/14, 2:48 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: 1660 By: swhite
Flag: suspect Exclude: No

CP04OSPM-WFP01-01-VEL3DK000
4/15/14, 4: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: 1407 By: swhite

CP04OSPM-WFP01
11/2/14, 10:12 AM 4/28/15, 11:13 AM

Wire Following Profiler is stuck around 55 dbar.

Id: 1393 By: leila

CP04OSPM-WFP01
8/5/15, 8:14 AM 10/12/15, 5:05 AM

Wire Following Profiler is stuck at the bottom of its range.

Id: 1394 By: leila

CP04OSPM-WFP01-01-VEL3DK000
Method: recovered_wfp
10/12/15, 3:11 PM 5/19/16, 8:09 AM

Missing

Id: 569 By: leila
Flag: not_available Exclude: No

CP04OSPM-WFP01-01-VEL3DK000
Method: telemetered
5/19/16, 6:35 PM 11/9/17, 6:29 PM

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

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

CP04OSPM-WFP01
6/2/16, 11:00 AM 9/28/16, 9:25 AM

Wire Following Profiler is stuck at the top of its range.

Id: 613 By: leila

CP04OSPM
10/12/16, 2:00 AM 6/1/17, 7:22 PM

Failed

Id: 354 By: leila
Flag: not_operational Exclude: No

CP04OSPM-WFP01-01-VEL3DK000
Method: telemetered
Stream: vel3d_k_wfp_stc_instrument
11/9/17, 5:08 PM 4/9/18, 12:25 PM

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

CP04OSPM-WFP01-01-VEL3DK000
Method: recovered_wfp
Stream: vel3d_k_wfp_instrument
11/9/17, 5:08 PM 4/9/18, 12:25 PM

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

CP04OSPM-WFP01
1/2/18, 7:00 PM 4/9/18, 12:25 PM

Deployment 8: Wire-Following Profiler stopped transmitting data. Issue identified as a software problem.

Id: 227 By: leila
Flag: not_available Exclude: No

CP04OSPM-WFP01-01-VEL3DK000
Method: telemetered
4/9/18, 10:09 AM 11/8/18, 11:43 AM

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

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

CP04OSPM-WFP01
12/31/19, 7:00 PM 6/8/20, 12:19 PM

Deployment 12: 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: 1885 By: cdobson