Velocity Profiler (600kHz)

Reference Designator
Review Status
Review Complete
ADCPT (Velocity Profiler (short range))
Make / Model
Teledyne RDI / WorkHorse Sentinel 600khz

Dataset Reviews Last processed: 8/14/19, 7:27 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 adcp_velocity_earth 186 184 0 0 0 0 26,461 600 30 / 29 1 Complete
2 recovered_host adcp_velocity_earth 187 187 0 0 0 0 4,481 3,600 29 / 30 Complete
3 recovered_inst adcp_velocity_earth / Complete
4 recovered_inst adcp_velocity_earth 142 142 0 0 0 0 6,795 1,800 29 / 30 1 Complete
5 recovered_inst adcp_velocity_earth 201 1 0 199 0 0 2 1,800 29 / 29 2 1 Complete
6 recovered_inst adcp_velocity_earth 176 176 0 0 0 0 8,388 1,800 29 / 29 1 Complete
7 recovered_inst adcp_velocity_earth 175 174 0 0 0 0 8,340 1,800 29 / 30 1 Complete
8 recovered_host adcp_velocity_earth 177 176 0 0 0 0 2,102 7,200 29 / 29 3 Complete
Data Ranges Review Images

Test Notes

  1. no comparison: timestamps do not match
  2. fail: data found in another stream (gaps: [1] days: [192])
  3. fail: data found in another stream (gaps: [1] days: [1])

Data Coverage

Deployment: 12345678
adcp_velocity_earth 99%100%100%0%100%99%99%

Lat/Lon Differences (km)

Deployment: 12345678
1 0.00
2 1.630.00
4 2.070.440.00
5 1.900.280.170.00
6 1.960.330.130.060.00
7 2.010.390.
8 1.880.360.340.

System Annotations

Metadata Start Date End Date Comment
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

5/10/17, 8:00 PM 10/30/17, 8:00 PM

Lost communication with DCL35, on the MFN of CE06ISSM sometime after 2017/05/11 12:32:17.552. Suspect failed/corrupted SD card based on results of minicom session with DCL35 (see attached). With the exception of the VEL3D, all instruments hosted by DCL35 are autonomous. No further data should be expected from: ADCPT (recording internally), PRESF (recording internally), PC02W (recording internally), PHSEN (recording internally), VEL3D (offline)

Id: 900 By: michaesm
Flag: not_available Exclude: No

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
10/17/19, 12:45 AM 5/23/20, 8:00 PM

Updated, 2020-05-24: Between 2019-10-17 and 2020-05-24, the clock on CPM3 was off by approximately 27 minutes. Communications between the buoy and the MFN were out of sync during this time period. The clock was automatically updated during routine operations on May 24, 2020 to the correct time, allowing communications and normal operations on the MFN to resume. *Communications to the seafloor sensors failed. Status of the instrumentation and data loggers is unknown. With the exception of the VEL3D and OPTAA, the sensors on the seafloor platform should continue to autonomously sample for the remainder of deployment. Until we recover and redeploy the mooring in the spring of 2020, no further telemetered data will be available from the seafloor sensors.

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

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

For reasons unknown, data from this instrument is not being telemetered at this time.

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

Review Notes

Metadata Start Date End Date Comment

There are no recovered_inst adcp_velocity_earth data available for download for deployments 2, 3 and 8. According to the ingest csvs, raw recovered_inst data files are available. These should be ingested or the datasets should be annotated to explain why they aren't available.

By Lori Garzio, on 8/20/19

Deployment: 5

There is only 1 day's worth of recovered_inst data for deployment 5, but the entire data record is available in the recovered_host dataset. These recovered_inst data should be available or the dataset should be annotated to explain why they aren't available.

By Lori Garzio, on 8/20/19

New Note