Single Point Velocity Meter

Reference Designator
Review Status
Review Complete
VELPT (Single Point Velocity Meter)
Make / Model
Nortek / Aquadopp 300m

Dataset Reviews Last processed: 8/6/19, 7:54 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 186 185 0 0 0 0 8,840 1,800 2 / 2 Complete
2 recovered_inst 187 187 0 0 0 0 8,967 1,800 2 / 2 Complete
3 recovered_inst 207 207 0 0 0 0 19,744 900 2 / 2 Complete
4 recovered_inst 142 142 0 0 0 0 13,589 900 2 / 2 Complete
5 recovered_inst 201 201 0 0 0 0 19,189 900 2 / 2 Complete
6 recovered_inst 176 172 3 0 0 0 16,424 900 2 / 2 Complete
7 recovered_inst 175 175 0 0 0 0 16,681 900 2 / 2 Complete
8 recovered_host 177 176 0 0 0 0 2,109 7,200 2 / 2 1 Complete
Data Ranges Review Images

Test Notes

  1. fail: data found in another stream (gaps: [1] days: [1])

Data Coverage

Deployment: 12345678

Lat/Lon Differences (km)

Deployment: 12345678
1 0.00
2 1.630.00
3 1.860.260.00
4 2.070.440.240.00
5 1.900.
6 1.960.330.
7 2.010.390.
8 1.880.360.160.340.

Example Composite Data Plot

System Annotations

Metadata Start Date End Date Comment
10/7/14, 3:45 PM

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

Id: 806 By: lgarzio

10/7/14, 3:45 PM 9/30/16, 8:00 PM

All of the inshore surface moorings suffer from an issue called the 'top of the day problem.' A race condition exists in the CPM firmware when transferring daily log files harvested from the various sub-components in a buoy system (e.g. DCL16, CPM3, DCL35, etc) over the Iridium RUDICS connection. The primary CPM rsync's data files from the various sub-components to a central data directory. The first time a daily file is created/copied into that directory (usually shortly after midnight), a compressed copy of the file is created and that compressed file is queued up in a separate text file for transmission to shore. The transfer routine reads that text file and processes the files from that list in order from top to bottom. Once that compressed file is transferred to shore, no further updates for that file are sent to shore. Meanwhile, the CPM continues to rsync data from the different sub-components, updating the original daily log file. The net result is that data is accumulating in the daily log file for an instrument, but we may see only one record (or none) depending on when the rsync job occurred and the compressed file was created and staged for transfer to shore. This affects telemetered data only.

Id: 897 By: michaesm

7/26/16, 8:00 PM 10/3/16, 8:00 PM

Correcting the iridium data telemetry issues, permitting full telemetry of data files, resulting in greater power consumption than anticipated. Result is power level of the battery pack has dropped below operational limits and subsystems can no longer power instruments. Shutting the mooring down, and placing in a low power maintenance mode. 11 instruments offline.

Id: 898 By: michaesm
Flag: not_operational Exclude: No

12/31/16, 7:00 PM 4/22/17, 8:00 PM

The buoy main battery voltage is being drawn down faster than expected. Have shutdown further power to DCL17 and to the OPTAA on DCL16. This takes the following instruments offline:
CTDBP (with attached FLORT)
Have had to power off DCL17 and DCL16 and reduce call in frequency to 12 hours. Will still (at least should) receive data from MFN. Instruments affected are:
DCL17 (Buoy)
CTDBP1 (with DOSTA) (should internally log)
PCO2W1 (should internally log)
PHSEN1 (should internally log)
NUTNR (should internally log)
VELPT2 (should internally log)

Id: 899 By: michaesm

10/2/17, 8:00 PM 3/2/18, 3:44 AM

CAMDS not serviced by vendor in time for deployment

Id: 1236 By: michaesm
Flag: not_operational Exclude: No

Method: telemetered
5/23/20, 8:00 PM

Reduced battery power on the mooring (unforeseen delay of mooring recovery well past the originally scheduled date) has resulted in the decision to power off the data logger port for this sensor for the remainder of the deployment. No further data will be telemetered from this instrument, though recovered instrument data should be available after the mooring is recovered.

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

Review Notes

Metadata Start Date End Date Comment
Deployment: 1
10/7/14, 12:00 AM 4/10/15, 12:00 AM

eastward_velocity values for deployment 1 look like they are shifted low compared to the rest of the deployments. This should be investigated.

By Lori Garzio, on 8/14/19

Deployment: 2
7/15/15, 12:00 AM 10/13/15, 11:45 PM

Suspect upward_velocity values for the second half of deployment 2 (middle panel in attached plot) - values exceed northward and eastward values.

By Lori Garzio, on 8/13/19

Deployment: 6
4/13/17, 7:53 PM 10/5/17, 1:53 PM

Suspect upward_velocity values for this deployment.

By Lori Garzio, on 8/14/19

Deployment: 8

There are no recovered_inst data available for download for deployment 8. According to the ingest csv, raw recovered_inst data files are available. These files should be ingested or the dataset should be annotated to explain why the recovered_inst dataset is not available.

By Lori Garzio, on 8/13/19

Deployment: 8
7/1/18, 12:00 AM 9/20/18, 3:26 PM

Suspect data towards the end of deployment 8 (bottom panel in attached plot).

By Lori Garzio, on 8/13/19

New Note