Suspect drop in conductivity. Excluding from summary data ranges.

By Lori Garzio, on 3/28/19

Dissolved oxygen data are suspect (annotation ID 202). Excluding from data range summary. When a correction is applied this annotation should be updated. Annotation ID 15 is a duplicate and should be deleted.

By Lori Garzio, on 3/28/19

The deployment depth in asset management is 2903 for each deployment, however the actual pressure data recorded by the CTD is around 2947 dbar.

By Lori Garzio, on 3/28/19

Annotation ID 211: "Due to errors during vendor calibration, a calibration offset (CC_offset) of -120.6 is being applied during the on-demand creation of the L1 Seawater Pressure (dbar) data product from this instrument." - it doesn't look like this offset is actually being applied as the pressure is still 120 dbar deeper than the other deployments and the deployment depth from asset management. This issue needs to be investigated. Excluding from summary data ranges. Annotation ID 24 should be deleted (it's a duplicate of ID 211, but 211 has more info)

By Lori Garzio, on 3/28/19

There are no data available for download for deployments 1-4 because the data were delivered via the CTD data stream (Redmine 8662). Now that the DO instrument has been separated from the CTD, the old DO data should be ingested in the DO data stream. Users currently have to go to the collocated CTD reference designator to get the DO data prior to 2018-11-07.

By Lori Garzio, on 8/29/19

The deployment depth from asset management is 2908 but the depth recorded by the instrument is closer to 2960 dbar.

By Lori Garzio, on 6/13/19

Suspect data - the abrupt change in seawater velocities should be investigated and the dataset should be annotated.

By Lori Garzio, on 8/26/19

The .nc files are missing the pressure coordinate.

By Lori Garzio, on 8/26/19

15% of seawater velocities are outside of global ranges. For eastward_turbulent_velocity there are periodic readings of >12 m/s, northward_turbulent_velocity periodic readings of 7 m/s, and upward_turbulent_velocity periodic readings of 10 m/s.

By Lori Garzio, on 8/26/19

The deployment depth from asset management for both deployments is 2908 but the depth recorded by the instrument is closer to 793 dbar.

By Lori Garzio, on 6/14/19

Seawater velocities look suspect for this deployment and don't follow the same pattern as the velocities for deployment 1. This should be investigated and the dataset should be annotated if there was an issue.

By Lori Garzio, on 8/26/19

3% of seawater velocities are outside of global ranges. For eastward_turbulent_velocity there are periodic readings of >12 m/s, northward_turbulent_velocity periodic readings of 7 m/s, and upward_turbulent_velocity periodic readings of 10 m/s.

By Lori Garzio, on 8/26/19

No valid seawater velocity data for this deployment - see annotation ID 84

By Lori Garzio, on 8/26/19

The .nc files are missing the pressure coordinate.

By Lori Garzio, on 8/26/19

It looks like the bin_depths changed in March 2015, after which there is a lot of noise in the upper 300m of the water column.

By Lori Garzio, on 12/18/19

Approximately 50% of the seawater velocities for deployment 1 are NaNs, outside of global ranges, or outliers (+/- 5 SD)

By Lori Garzio, on 12/18/19

The .nc files for deployment 1 are missing the coordinates pressure, lat and lon.

By Lori Garzio, on 12/18/19

Suspect data for temperature06 (see annotation ID 198). Excluding from summary data ranges.

By Lori Garzio, on 5/31/19

The position of each thermistor in the 3D array is available in the provenance.json file as a calibration coefficient (e.g., CC_t15_position). While the information is available, it would be more convenient for the user if the positions are given as variable attributes in the netcdf files.

By Lori Garzio, on 5/31/19

Substantial change in temperature13 after the unexplained data gap in July 2015 (see annotation ID 197). This should be annotated.

By Lori Garzio, on 5/31/19