Single Point Velocity Meter

Reference Designator
CP04OSSM-MFD35-04-VELPTB000
Review Status
Review Complete
Note
Depth
450m
Class
VELPT (Single Point Velocity Meter)
Make / Model
Nortek / Aquadopp 3000m

Dataset Reviews Last processed: 8/8/19, 3:09 PM

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_inst 150 149 0 0 0 0 5,381 3,600 455 / 314 1 1 Complete
2 recovered_inst 168 167 0 0 0 0 8,013 1,800 442 / 458 Complete
3 recovered_host 205 94 0 100 8 16 654,205 1 454 / 451 Complete
4 recovered_host 139 136 0 0 13 13 1,537 446 / 459 Complete
5 recovered_host 240 5 0 234 0 0 97 450 / 447 Complete
6 recovered_inst 150 150 0 0 0 0 7,151 1,800 443 / 462 Complete
7 recovered_inst 153 153 0 0 0 0 7,293 1,800 452 / 461 Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison

Data Coverage

Deployment: 1234567
46%98%2%
99%99%100%100%

Lat/Lon Differences (km)

Deployment: 1234567
1 0.00
2 0.510.00
3 0.560.790.00
4 0.490.120.850.00
5 0.580.820.030.880.00
6 0.460.200.880.080.910.00
7 0.540.750.050.810.080.840.00

Example Composite Data Plot

System Annotations

Metadata Start Date End Date Comment
CP04OSSM-MFD35-04-VELPTB000
12/12/14, 4:47 PM

According to the manufacturer, data are suspect when the instrument is tilted more than 20 degrees (measured by pitch and roll).

Id: 819 By: lgarzio

CP04OSSM
Method: telemetered
10/22/15, 3:38 PM 5/13/16, 1:18 PM

Fuel cell impacted available instrument power, so telemetered data are not available or reliable. Recovered data are available for instruments that could record internally.

Id: 1362 By: leila

CP04OSSM-MFD35-04-VELPTB000
10/22/15, 3:38 PM 5/13/16, 1:18 PM

Deployment 3: The VELPT instrument deployed was a Series A which has a 300 m rated head rather than a Series B which has a 3000 m rated head. The VELPT was deployed outside of operational range; treat data as suspect.

Id: 1911 By: cdobson
Flag: suspect Exclude: No

CP04OSSM-MFD35
10/16/16, 8:00 PM 4/2/17, 9:00 PM

No telemetered data are expected because of ground faults on the seafloor Multi-Function Node. Recovered data are available from instruments recording internally.

Id: 355 By: leila

CP04OSSM-MFD35
Method: telemetered
2/9/18, 1:00 PM 3/29/18, 8:42 AM

Deployment 7: Communication with the MFN instruments was disabled due to intermittent communications over the DSL line.

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

CP04OSSM-MFD35
Method: telemetered
5/9/18, 11:00 PM 10/30/18, 10:30 AM

Instruments are presently disabled. Note: Instruments may continue to sample using internal batteries and storage cards.

Id: 1517 By: leila

CP04OSSM
Method: telemetered
1/30/19, 10:00 AM 4/8/19, 7:39 AM

CP04OSSM D00009 buoy broke free and went adrift on 1/30/2019, 1500UTC. All instruments on the MFN ceased telemetry on 1/30/2019 and instruments on the buoy/NSIF continued to sample through 2/1/2019. No more telemetered data expected for this deployment.

Id: 1557 By: cdobson

CP04OSSM-MFD35
5/11/19, 8:00 PM

Deployment 10: Telemetered data from all MFN instruments could be delayed up to 3 days due to a limitation in communications with the MFN.

Id: 1628 By: cdobson

CP04OSSM-MFD35
11/14/19, 7:00 PM

Deployment 11: MFN offline due to high voltage short on 2019-11-15. No telemetered data expected from instruments on the MFN; instruments with external batteries will continue to log internally.

Id: 1821 By: cdobson
Flag: not_operational Exclude: No

Review Notes

Metadata Start Date End Date Comment
CP04OSSM-MFD35-04-VELPTB000

recovered_inst data are not available for download from deployments 3 - 5: the raw data files are available according to the ingest csv. The data should be ingested or annotated to indicate why they are not available.

By Lori Garzio, on 8/14/19

CP04OSSM-MFD35-04-VELPTB000
5/27/16, 3:50 PM 11/2/17, 2:15 PM

Suspect upward_velocity values for deployments 4 - 6: values exceed northward and eastward values. 31%, 86%, and 15% of the values for upward_velocity are outside of global ranges for deployments 4, 5, and 6, respectively.

By Lori Garzio, on 8/14/19

CP04OSSM-MFD35-04-VELPTB000
Deployment: 1
12/12/14, 12:00 AM 1/2/15, 12:00 AM

Suspect data at the beginning of the deployment.

By Lori Garzio, on 8/14/19

CP04OSSM-MFD35-04-VELPTB000
Deployment: 2
5/9/15, 1:04 AM 5/15/15, 12:00 AM

Suspect data at the beginning of the deployment.

By Lori Garzio, on 8/14/19

CP04OSSM-MFD35-04-VELPTB000
Deployment: 3
10/22/15, 7:38 PM 5/13/16, 5:18 PM

The sampling rate for deployment 3 is 1 Hz, where for every other deployment there is 1 sample taken every 30 or 60 minutes. This should be annotated to explain why the sampling rates are so different. 52% of the upward_velocity values for this deployment are outside of global ranges.

By Lori Garzio, on 8/14/19

CP04OSSM-MFD35-04-VELPTB000
Deployment: 7
10/28/17, 2:24 PM 3/29/18, 12:42 PM

Suspect data: 37% of upward_velocity values are outside of global ranges.

By Lori Garzio, on 8/14/19

New Note