The data gap at the end of deployment 8 should be annotated.

By Lori Garzio, on 3/26/19

There are recovered_host and telemetered data available for the second half of deployment 2 (2015-01-02T08:00:00 to 2015-04-12T00:00:00), and the same data are not available in the recovered_inst data stream. These data should be available in the recovered_inst data stream (or annotated if there was an issue with internally recording data).

By Lori Garzio, on 3/26/19

Annotation ID 763: pressure is incorrect for deployment 1. This annotation should also say that conductivity, density and salinity values are wrong. Issue should be investigated.

By Lori Garzio, on 3/26/19

The deployment 4 data gap at the end of the data record should be annotated.

By Lori Garzio, on 3/26/19

Deployments 3 and 6 - the deployment depths from asset management are 454 and 443, respectively, however the pressure values recorded by the sensor are closer to 465. The deployment depths should be double checked.

By Lori Garzio, on 3/26/19

Annotation ID 748: spike in data record. Excluding from summary data ranges.

By Lori Garzio, on 3/26/19

The sampling rate for deployment 6 is 900 seconds (for every other deployment the sampling rate is 10 seconds). This deviation from the sampling plan should be annotated.

By Lori Garzio, on 3/26/19

Deployment 5 data gaps (13 gaps spanning 19 days) should be annotated: [['2017-04-11T08:55:14', '2017-04-13T17:06:00'], ['2017-04-14T22:53:53', '2017-04-16T08:15:53'], ['2017-04-16T11:54:23', '2017-04-17T15:17:43'], ['2017-04-17T18:54:52', '2017-04-20T00:01:40'], ['2017-04-20T09:07:23', '2017-04-22T00:15:30'], ['2017-04-23T00:36:19', '2017-04-24T06:20:39'], ['2017-04-29T22:52:40', '2017-05-02T07:43:13'], ['2017-05-03T13:53:47', '2017-05-06T23:44:38'], ['2017-05-08T13:52:48', '2017-05-10T01:26:22'], ['2017-05-11T21:55:27', '2017-05-14T20:54:00'], ['2017-05-15T20:52:59', '2017-05-17T12:41:30'], ['2017-05-21T11:53:43', '2017-05-22T17:33:56'], ['2017-05-24T18:52:46', '2017-05-25T21:57:21']]

By Lori Garzio, on 3/26/19

Recovered_inst data don't match with the recovered_host and telemetered data. It looks like the timestamps are substantially offset. This should be investigated and resolved and/or annotated.

By Lori Garzio, on 3/26/19

Deployment 3 data gaps should be annotated (3 gaps spanning 20 days): ['2015-11-30T03:02:20', '2015-12-05T00:14:29'], ['2015-12-10T21:02:20', '2015-12-23T15:14:26'], ['2016-01-07T15:02:17', '2016-01-11T15:14:26']

By Lori Garzio, on 3/26/19

data are suspect below 70 dbar

By Leila Belabbassi, on 3/25/19

Missing annotation in the system: the instruments on the profiler quit long before the deployment end date.

By Leila Belabbassi, on 3/25/19

Annotation ID 741 should be updated to indicate that there are also no recovered_inst data available for this time frame. It looks like the instrument started to fail shortly after 8-15-2016. See attached plot - the sampling frequency appears to decline (data points are sparser).

By Lori Garzio, on 3/25/19

For deployments 1, 6, 7 and 8 telemetered and recovered data have different timestamps and so data comparison could not be performed.

By Leila Belabbassi, on 3/25/19

Annotation ID 742 should be updated to indicate that there are no data available for this time frame. Did the instrument fail?

By Lori Garzio, on 3/25/19

suspect data profiles

By Leila Belabbassi, on 3/25/19

suspect data profiles

By Leila Belabbassi, on 3/25/19

suspect data profiles

By Leila Belabbassi, on 3/25/19

suspect data profiles

By Leila Belabbassi, on 3/25/19

suspect data profiles

By Leila Belabbassi, on 3/25/19