Surface Wave Spectra

Reference Designator
GA01SUMO-SBD12-05-WAVSSA000
Review Status
Review Complete
Note
Depth
0m
Class
WAVSS (Surface Wave Spectra)
Make / Model
Axys Technologies / TRIAXYS

Dataset Reviews Last processed: 6/24/19, 6:53 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_host 257 257 0 0 0 0 6,131 0 / 1 1 Complete
1 recovered_host 257 257 0 0 0 0 6,131 0 / 2 Complete
1 recovered_host 257 257 0 0 0 0 6,131 0 / 2 Complete
1 recovered_host 257 257 0 0 0 0 6,131 0 / Complete
2 recovered_host / Complete
2 recovered_host / Complete
2 recovered_host 361 349 0 0 1 12 8,324 0 / 2 Complete
2 recovered_host 361 349 0 0 1 12 8,324 0 / 3 Complete
3 recovered_host / Complete
3 recovered_host / Complete
3 recovered_host 445 445 0 0 0 0 10,665 0 / 2 Complete
3 recovered_host 445 445 0 0 0 0 10,665 0 / Complete
Data Ranges Review Images

Test Notes

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

Data Coverage

Deployment: 123
100%
100%
100%97%100%
100%97%100%

Lat/Lon Differences (km)

Deployment: 123
1 0.00
2 10.690.00
3 1.2511.910.00

Example Composite Data Plot

System Annotations

Metadata Start Date End Date Comment
GA01SUMO
3/15/15, 5:25 PM 11/26/15, 5:08 AM

Deployment 1: Buoy log files showed that seawater was first detected inside the buoy well on 3/26/2015. Both leak detectors showed increasing presence of water over the period of deployment. Upon recovery of the mooring, no external damage was visible and the buoy did not appear to be floating lower than normal.

Id: 653 By: lgarzio

GA01SUMO-SBD12
3/15/15, 5:25 PM 11/26/15, 5:08 AM

Deployment 1: Upon recovery, the bottom of the buoy was heavily biofouled with gooseneck barnacles. The barnacle coverage likely caused imporper sea water flushing at the location of the intakes and sensor faces for the subsurface instruments.

Id: 655 By: lgarzio

GA01SUMO-SBD12-05-WAVSSA000
11/14/15, 4:06 PM 1/14/18, 5:24 AM

The WAVSS instrument should sample at 4 Hz for 20 minutes every hour according to the OOI baseline sampling strategy. However, during deployments 2 and 3, the instrument was erroneously configured with a sampling period of only 5 minutes.

Id: 1390 By: lgarzio
Flag: suspect Exclude: No

GA01SUMO-SBD12
11/14/15, 4:06 PM 11/8/16, 5:10 AM

Deployment 2: Upon recovery, the bottom of the buoy was heavily biofouled with barnacles.

Id: 664 By: lgarzio

GA01SUMO-SBD12
10/26/16, 9:47 PM 1/14/18, 5:24 AM

Deployment 3: Upon recovery, the bottom of the buoy was heavily biofouled.

Id: 386 By: lgarzio

Review Notes

Metadata Start Date End Date Comment
GA01SUMO-SBD12-05-WAVSSA000

The data streams wavss_a_dcl_mean_directional_recovered and wavss_a_dcl_motion_recovered aren't available for download for deployments 2-3. These streams should be available or the dataset should be annotated.

By Lori Garzio, on 6/28/19

GA01SUMO-SBD12-05-WAVSSA000

There are no global ranges in the system for wavss_a_dcl_statistics mean_spread, wavss_a_dcl_mean_directional_recovered wavss_a_directional_frequency, and wavss_a_dcl_non_directional_recovered wavss_a_non_directional_frequency

By Lori Garzio, on 6/28/19

GA01SUMO-SBD12-05-WAVSSA000
11/14/15, 9:06 PM 1/14/18, 10:24 AM

Annotation ID 1390: the instrument was incorrectly configured for deployments 2-3. Excluding from final data ranges.

By Lori Garzio, on 6/28/19

GA01SUMO-SBD12-05-WAVSSA000
Deployment: 1

In the wavss_a_dcl_mean_directional_recovered data stream, 60% of mean_direction_array is either nans or outside of global ranges, wavss_a_directional_frequency is all fill values, and 57% of wavss_a_corrected_directional_wave_direction is fill values.

For the wavss_a_dcl_motion_recovered data stream, ~50% of the data for every parameter is outside of global ranges or outliers (+/- 5 SD).

By Lori Garzio, on 6/28/19

GA01SUMO-SBD12-05-WAVSSA000
Deployment: 2

There are 10 days during deployment 2 where data are available in the telemetered stream and not the recovered_host data stream. These recovered data should be available.

By Lori Garzio, on 6/28/19

New Note