The 6 day data gap at the beginning of the deployment should be annotated, and the 193 missing days at the end of the deployment should be annotated (the CTD to which this instrument was connected failed).

By Lori Garzio, on 2/19/19

Annotation ID 785 should be removed - Redmine issue 13228 has been resolved.

By Lori Garzio, on 2/19/19

Annotation ID 784 should be removed - Redmine issue 13228 has been resolved.

By Lori Garzio, on 2/19/19

Annotation ID 783 should be removed - Redmine issue 13228 has been resolved.

By Lori Garzio, on 2/19/19

The deployment 3 netCDF file contains the variable int_ctd_pressure and that variable contains valid pressure data, however it does not have any attributes (e.g. standard_name, units) and this variable is not listed as a coordinate for any of the variables in the file. There is pressure data from the collocated CTD (GA01SUMO-RID16-03-CTDBPF000) for the beginning of deployment 3, and these CTD files are included in the thredds server when I downloaded the DOSTA data (https://opendap.oceanobservatories.org/thredds/catalog/ooi/lgarzio@marine.rutgers.edu/20190111T235754-GA01SUMO-RID16-06-DOSTAD000-recovered_host-dosta_abcdjm_dcl_instrument_recovered/catalog.html). int_ctd_pressure is a coordinate in the deployment 1 and 2 files. It should also be a coordinate for deployment 3.

By Lori Garzio, on 2/11/19

Temperature and salinity corrected dissolved oxygen (umol kg-1) ends on 1-4-2017 because the collocated CTD data are not available after this time period (the CTD was damaged).

By Lori Garzio, on 2/14/19

Deployment 2: The recovered_host data from the following instruments have the same 4 data gaps [['2015-12-04', '2015-12-14'], ['2016-01-06', '2016-01-11'], ['2016-02-05', '2016-02-10'], ['2016-03-11', '2016-03-14']]. These gaps should be annotated to explain why the data are missing, or gaps should be filled in if the data are available. [02-FLORDG031, 02-FLORDG032, 02-FLORDG033, 02-DOSTAD031, 02-DOSTAD032, 02-DOSTAD033]

By Lori Garzio, on 2/11/19

Annotation ID 390 should be updated to indicate that it looks like the cables look like they were severed on/near 2017-03-04 (according to the data). Excluding data after this time from final stats.

By Lori Garzio, on 2/11/19

Deployments 2 and 3: there is no pressure variable in the netCDF files. This should be a coordinate.

By Lori Garzio, on 2/8/19

Deployments 2 and 3: there is no pressure variable in the netCDF files. This should be a coordinate.

By Lori Garzio, on 2/8/19

Deployments 2 and 3: there is no pressure variable in the netCDF files. This should be a coordinate.

By Lori Garzio, on 2/8/19

Deployments 2 and 3: there is no pressure variable in the netCDF files. This should be a coordinate.

By Lori Garzio, on 2/8/19

Deployments 2 and 3: there is no pressure variable in the netCDF files. This should be a coordinate.

By Lori Garzio, on 2/8/19

Deployments 2 and 3: there is no pressure variable in the netCDF files. This should be a coordinate.

By Lori Garzio, on 2/8/19

The sudden and sustained high variability in optical_backscatter seems suspect and should be investigated. Excluding from final statistics.

By Lori Garzio, on 2/8/19

seawater_scattering_coefficient and optical backscatter data arrays contain a high percentage of fill values (71%).

By Lori Garzio, on 2/8/19

There are 16 gaps in the data totaling 168 days of missing data (from 2017-06-21 to 2018-01-10). This should be investigated and the data should be filled in (if available) or annotated to explain why these data are missing.

By Lori Garzio, on 2/8/19

The pressure coordinate 'pressure_depth' is all fill values for deployments 1-3. This variable should contain valid pressure data.

By Lori Garzio, on 2/8/19

Deployments 2 and 3: the heavy biofouling of the surface buoy appears to have negatively affected this instrument. The datasets should be annotated to indicate that the data are unreasonable/suspect.

By Lori Garzio, on 2/8/19

There are only 7 days of data for this deployment. This dataset should be annotated to explain why the majority of the deployment is missing (if known).

By Lori Garzio, on 2/8/19