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/27/19

For each deployment: in the wavss_a_dcl_mean_directional_recovered data stream, ~50% of mean_direction_array is either nans or outside of global ranges, wavss_a_directional_frequency is all fill values, ~40-50% 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/27/19

For deployment 1, only the wavss_a_dcl_statistics_recovered stream is available for download. The other data streams should be available or the dataset should be annotated.

By Lori Garzio, on 6/27/19

There are 3 gaps in the recovered_host dataset where telemetered data are available. These data should be available in the recovered data stream: time ranges: ['2016-10-02T00:23:00', '2016-10-02T23:23:01'], ['2016-11-29T00:23:00', '2016-11-29T23:23:00'], ['2016-12-02T00:23:01', '2016-12-02T23:23:03']

By Lori Garzio, on 6/27/19

Suspect data - number of zero crossings is substantially lower than other deployments. This looks similar to the issue on global/Pioneer instruments where the instrument was configured incorrectly (see annotation ID 1389 for an example). This should be investigated and annotated.

By Lori Garzio, on 6/27/19

There are no recovered_host data available for download for this deployment. According to the ingest csv, the raw data files are available. These files should be ingested or the dataset should be annotated if recovered_host data are not available.

By Lori Garzio, on 6/27/19