1. Arrays
  2. Coastal Endurance
  3. Washington Offshore Surface Mooring
  4. Near Surface Instrument Frame
  5. Velocity Profiler (300kHz)

Velocity Profiler (300kHz)

Reference Designator
CE09OSSM-RID26-01-ADCPTC000
Review Status
Review Complete
Note
Depth
7m
Class
ADCPT (Velocity Profiler (short range))
Make / Model
Teledyne RDI / WorkHorse Sentinel 300khz

Dataset Reviews Last processed: 8/14/19, 7:31 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 170 47 0 122 0 0 4,424 900 7 / 1 2 Complete
2 recovered_inst adcp_velocity_earth 206 206 0 0 0 0 19,649 900 7 / 2 Complete
3 recovered_inst adcp_velocity_earth 134 134 0 0 0 0 12,760 900 7 / 2 Complete
4 recovered_inst adcp_velocity_earth 206 206 0 0 0 0 19,736 900 7 / 2 Complete
5 recovered_inst adcp_velocity_earth 178 178 0 0 0 0 17,085 900 7 / 2 Complete
6 recovered_inst adcp_velocity_earth 178 4 0 173 0 0 331 899 7 / 2 Complete
7 recovered_host adcp_velocity_earth 178 18 0 156 5 5 1,157 7 / Complete
Data Ranges Review Images

Test Notes

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

Data Coverage

Deployment: 1234567
adcp_velocity_earth 28%100%100%100%100%2%10%

Lat/Lon Differences (km)

Deployment: 1234567
1 0.00
2 0.320.00
3 0.230.540.00
4 1.121.400.900.00
5 0.130.380.181.020.00
6 2.102.361.870.971.990.00
7 0.100.310.241.100.082.070.00

System Annotations

Metadata Start Date End Date Comment
CE09OSSM-RID26-01-ADCPTC000
 		9/5/16, 8:00 PM 10/21/16, 8:00 PM

At roughly 10:30 on Tuesday, the ADCP on the NSIF started to include garbage characters in the data file. It is intermittent, and there are periods where data is still coming through. This could be a low battery, or something else. In an attempt to remedy it, the voltage supplied to the ADCP has been increased to 24V. Update: The garbage continued to come through after the voltage was changed. It could be a suspect cable, or loose connection, rather than a battery issue.

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

CE09OSSM-RID26-01-ADCPTC000
 		10/5/17, 8:00 PM 10/5/17, 8:01 PM

ADCPT started receiving/generating random break commands right after deployment. Interventions at the time were unable to resolve, but the system should still be collecting data. The problem could have been caused by the DCL sending erroneous commands. Telemetered data no longer flowing to the system. Data should be available upon recovery.

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

CE09OSSM-RID26-01-ADCPTC000
Method: telemetered
Stream: adcp_engineering
2/9/19, 7:00 PM

Started to see evidence of random binary encoded data in the ADCP record. In the past, this has been evidence of electronic noise on the serial lines connecting the instrument to the data logger adversely affecting the behavior of the instrument. We have disabled the data logger port for the remainder of the deployment to minimize the chance of any further disruptions to the ADCP.

Id: 1553 By: wingardc
Flag: not_operational Exclude: No

CE09OSSM-RID26-01-ADCPTC000
Method: telemetered
Stream: adcp_velocity_earth
2/9/19, 7:00 PM

Started to see evidence of random binary encoded data in the ADCP record. In the past, this has been evidence of electronic noise on the serial lines connecting the instrument to the data logger adversely affecting the behavior of the instrument. We have disabled the data logger port for the remainder of the deployment to minimize the chance of any further disruptions to the ADCP.

Id: 1554 By: wingardc
Flag: not_operational Exclude: No

CE09OSSM-RID26-01-ADCPTC000
Method: telemetered
Stream: adcp_config
2/9/19, 7:00 PM

Started to see evidence of random binary encoded data in the ADCP record. In the past, this has been evidence of electronic noise on the serial lines connecting the instrument to the data logger adversely affecting the behavior of the instrument. We have disabled the data logger port for the remainder of the deployment to minimize the chance of any further disruptions to the ADCP.

Id: 1555 By: wingardc
Flag: not_operational Exclude: No

CE09OSSM-RID26
Method: telemetered
4/27/20, 3:40 PM

We are experiencing an intermittent failure of communication between the systems on the NSIF and the buoy. While the systems on the NSIF are operating, due to a change in the telemetry system, only a finite backlog of data is telemetered to shore. As a result, when communications are restored, some of the data backlog may be missing and there may be gaps in the record.

Id: 2183 By: wingardc

CE09OSSM
Method: telemetered
5/9/20, 8:40 PM 5/10/20, 8:00 PM

Due to a bug in the mooring telemetry system, data during this time range was not telemetered to shore. It was recorded on the mooring and instruments and will be available in the recovered data streams.

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

Review Notes

Metadata Start Date End Date Comment
CE09OSSM-RID26-01-ADCPTC000

The pressure variable (daPa) is an array of fill values for every deployment.

By Lori Garzio, on 8/20/19

CE09OSSM-RID26-01-ADCPTC000
Deployment: 4

Suspect data - the instrument was deployed at 7m depth so there shouldn't be data from 0-7m

By Lori Garzio, on 8/20/19

CE09OSSM-RID26-01-ADCPTC000
Deployment: 6

Annotation ID 1239 should be updated - only 3 days of recovered_inst data are available, so the full data record wasn't available upon recovery.

By Lori Garzio, on 8/20/19

CE09OSSM-RID26-01-ADCPTC000
Deployment: 7

There are no recovered_inst adcp_velocity_earth data available for download for this deployment. According to the ingest csv, raw recovered_inst data files are available. These should be ingested or the dataset should be annotated to explain why recovered_inst data aren't available.

By Lori Garzio, on 8/20/19

New Note