The global ranges for pressure_mbar (units=0.001 dbar) are 0.0 to 1100000.0. This instrument is deployed at 2300m so the pressure values are flagged as outside global ranges: the global ranges should be reviewed.

By Lori Garzio, on 8/15/19

The global ranges for pressure_mbar (units=0.001 dbar) are 0.0 to 1100000.0. This instrument is deployed at 2000m so the pressure values are flagged as outside global ranges: the global ranges should be reviewed.

By Lori Garzio, on 8/15/19

The global ranges for pressure_mbar (units=0.001 dbar) are 0.0 to 1100000.0. This instrument is deployed at 1700m so the pressure values are flagged as outside global ranges: the global ranges should be reviewed.

By Lori Garzio, on 8/15/19

12% of upward_velocity values for deployment 2 are outside of global ranges.

By Lori Garzio, on 8/15/19

The data range for deployment 2 is substantially higher compared to deployment 1.

By Lori Garzio, on 8/15/19

The velocity range for deployment 2 is substantially higher compared to deployment 3.

By Lori Garzio, on 8/15/19

The velocity range for deployment 2 is substantially higher compared to the other 3 deployments.

By Lori Garzio, on 8/15/19

There is about 1 month during deployment 1 where telemetered data are available and recovered_host data are not available. This should be investigated. 2015-06-03T18:35:56 to 2015-07-06T18:07:03

By Lori Garzio, on 8/15/19

The sampling rate for deployment 2 is 1 Hz, where for every other deployment there is 1 sample taken every 15 minutes. This should be annotated to explain why the sampling rates are so different.

By Lori Garzio, on 8/15/19

Suspect data: 75% of upward_velocity values are outside of global ranges.

By Lori Garzio, on 8/15/19

Suspect upward_velocity values for deployments 2 (top panel in attached plot) - values often exceed northward and eastward values.

By Lori Garzio, on 8/15/19

There are no recovered_inst data available for download for deployment 3. According to the ingest csv, recovered_inst raw data files are available but there were parsing issues. This should be investigated.

By Lori Garzio, on 8/15/19

Suspect upward_velocity values for deployments 2 (middle panel in attached plot) - values periodically exceed northward and eastward values.

By Lori Garzio, on 8/14/19

The sampling rate for deployment 3 is 1 Hz, where for every other deployment there is 1 sample taken every 15 minutes. This should be annotated to explain why the sampling rates are so different.

By Lori Garzio, on 8/14/19

There are 13 days in deployment 3 where telemetered and recovered_host data are available for a time range where recovered_host data aren't available. This should be investigated.

By Lori Garzio, on 8/14/19

recovered_inst data aren't available for download for deployments 1, 3, 4, and 5. According to the ingest csvs, recovered_inst data aren't expected for deployments 1 and 4 (these dataset should be annotated). recovered_inst raw data files are available for deployments 3 and 5. These data should be ingested or the datasets should be annotated.

By Lori Garzio, on 8/14/19

Suspect data at the beginning of the deployment.

By Lori Garzio, on 8/14/19

Suspect data at the beginning of the deployment.

By Lori Garzio, on 8/14/19

Suspect data: 37% of upward_velocity values are outside of global ranges.

By Lori Garzio, on 8/14/19

Suspect upward_velocity values for deployments 4 - 6: values exceed northward and eastward values. 31%, 86%, and 15% of the values for upward_velocity are outside of global ranges for deployments 4, 5, and 6, respectively.

By Lori Garzio, on 8/14/19