The missing 110 days of data for this deployment should be annotated.

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

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

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 missing. 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

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

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

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

recovered_host data aren't available for this deployment. According to the ingest csv, the data aren't expected because the SD card was corrupted. This should be annotated in the system.

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 5 days at the beginning of the deployment where data are available in the telemetered stream but not the recovered - recovered data should be available for download or the dataset should be annotated.

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

Suspect data - number of zero crossings is substantially lower than other deployments, and other WAVSS variables are suspect. 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 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 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

For deployment 7, only recovered_host data from the presf_abc_dcl_tide_measurement_recovered data stream are available for download. According to the ingest csv, recovered_inst raw data files are available. These data should be ingested or the dataset should be annotated to explain why recovered_inst data aren't available. The missing 145 days of data at the end of the deployment should also be annotated.

By Lori Garzio, on 6/26/19

There are no recovered data available for download from this instrument. According to the ingest csv, the recovered raw data files are missing. These data should be loaded on the raw data server and ingested, or annotated to indicate why they aren't available.

By Lori Garzio, on 6/26/19

Suspect presf_wave_burst_pressure (dbar) data at the beginning of the deployment. 89% of the data for this deployment are either fill values or outside of global ranges.

By Lori Garzio, on 6/26/19

The pressure shifted substantially in Oct 2016 - this should be investigated and annotated.

By Lori Garzio, on 6/26/19

A couple of suspect presf_wave_burst_pressure (dbar) data points.

By Lori Garzio, on 6/26/19