Comparisons with the shipboard CTD casts were done for D0002 and D0003. The shipboard CTD cast data are corrected for temperature, salinity, and depth (Redmine 14230). The L2 DO data product (corrected for temperature, salinity and depth) is substantially lower for the glider compared to the shipboard data. This could be related to the issue of incorrect default salinity settings on some glider optodes (Redmine 13575). Comparison to the shipboard bottle data is outside the scope of this project. Note: the conversion from ml/l to umol/kg for the shipboard DO = DO (ml/l) * 44.661 / 1.025.

By Lori Garzio, on 3/8/19

There are 2 days at the end of deployment 3 for which data are available in the telemetered stream and not the recovered_host stream. These data should be available in the recovered_host stream.

By Lori Garzio, on 3/22/19

Data look suspect shortly after annotation ID 47 indicates violent weather caused multiple power outages. This time period should be investigated and annotated. Excluding from data range summary.

By Lori Garzio, on 3/22/19

The automated valid data tests were triggered for all deployments because of the high percentage of fill values for seawater_scattering_coefficient and optical_backscatter.

By Lori Garzio, on 3/22/19

pressure_depth (dbar) is an array of fill values in all files. This variable should contain valid pressure data from the collocated CTD.

By Lori Garzio, on 3/22/19

pressure_depth (dbar) is an array of fill values in all files. It's unclear if this variable should contain valid data, or if it's assumed that the pressure is 1 because this instrument is on the surface buoy.

By Lori Garzio, on 3/21/19

Annotation ID 1521 indicates that the instrument flooded and there is no valid data from this deployment. Excluding from data range summary.

By Lori Garzio, on 3/22/19

suspect data profile

By Leila Belabbassi, on 3/21/19

bad data for CTD, DO, FLORT, VEL3D and PAR seen after 15 December 2014 to the end of the deployment.

example plot from CTD shown.

By Leila Belabbassi, on 3/21/19

annotation ID 712 should be updated by adding that data quality is bad for this time range.

By Leila Belabbassi, on 3/20/19

There are 3 days at the end of deployment 3 for which data are available in the telemetered stream and not the recovered_host stream. These data should be available in the recovered_host stream.

By Lori Garzio, on 3/21/19

The automated valid data tests were triggered for all deployments because of the high percentage of data outside of global ranges and outliers (for all variables).

By Lori Garzio, on 3/21/19

Total volume scattering coefficient is substantially higher for deployment 4 compared to the previous 2 deployments. A similar pattern is observed on the other two fluorometers on RII11 (FLORDG031 and FLORDG032). This should be investigated.

By Lori Garzio, on 3/21/19

Instrument appeared to start failing (negative total volume scattering coefficient values). Excluding from data range summary.

By Lori Garzio, on 3/21/19

Total volume scattering coefficient is substantially higher for deployment 4 compared to the previous 2 deployments. A similar pattern is observed on the other two fluorometers on RII11 (FLORDG031 and FLORDG033). This should be investigated.

By Lori Garzio, on 3/21/19

Total volume scattering coefficient is substantially higher for deployment 4 compared to the previous 2 deployments. A similar pattern is observed on the other two fluorometers on RII11 (FLORDG032 and FLORDG033). This should be investigated.

By Lori Garzio, on 3/21/19

It appears that the instrument failed shortly after deployment (values are negative). Data should be annotated with reason for failure (if known).

By Lori Garzio, on 3/21/19

suspect data with individual profiles

By Leila Belabbassi, on 3/20/19

suspect data with individual profiles

By Leila Belabbassi, on 3/19/19

suspect data profiles

By Leila Belabbassi, on 3/20/19