According to annotation IDs 1430-1431, no CT data are expected. However, sea_surface_temperature values are -5, sea_surface_conductivity values are 0.0, and met_salsurf values are 0.0. It looks like other variables are using these data in their calculations, which is creating bad data products. Excluding from summary data ranges

By Lori Garzio, on 4/8/19

Data gaps should be annotated: [['2017-01-02T10:59:17', '2017-01-03T23:08:12'], ['2017-01-26T12:11:28', '2017-01-29T14:44:28'], ['2017-01-29T14:44:28', '2017-01-31T18:27:25'], ['2017-01-31T18:45:15', '2017-02-05T13:46:10'], ['2017-02-05T21:34:14', '2017-02-08T19:43:18'], ['2017-02-08T19:57:53', '2017-02-11T13:14:58']]

By Lori Garzio, on 4/8/19

There is a lot of noise for sea_surface_conductivity and met_salsurf at the end of the deployment.

By Lori Garzio, on 4/8/19

Missing data at the end of the deployment should be annotated.

By Lori Garzio, on 4/8/19

These variables are missing global ranges for this instrument: stream metbk_hourly - met_buoyfls, met_buoyflx, met_frshflx, met_heatflx, met_latnflx, met_mommflx, met_rainflx, met_sensflx, met_netsirr_hourly. stream metbk_a_dcl_instrument and metbk_a_dcl_instrument_recovered: met_windavg_mag_corr_east, met_windavg_mag_corr_north, met_heatflx_minute, met_latnflx_minute, met_netlirr_minute, met_sensflx_minute.

By Lori Garzio, on 4/8/19

metbk_hourly data will not be reviewed because of issues producing the data products have not been resolved - see Redmine tickets 13111, 13113, 13221. Data plots are available in the review images.

By Lori Garzio, on 4/8/19

met_current_speed, met_relwind_speed, met_wind10m, shortwave_irradiance, and met_netsirr global ranges should be reviewed. See review notes for CP01CNSM-SBD11-06-METBKA000 for more details.

By Lori Garzio, on 4/8/19

Annotation IDs 1430 and 1431 should be updated to indicate this refers to deployment 5 (not 4)

By Lori Garzio, on 4/8/19

missing met_relwind_direction, met_current_speed, and met_current_direction for deployments 1-3.

By Lori Garzio, on 4/8/19

Surface Current Speeds are substantially higher for this deployment compared to other deployments. This should be investigated.

By Lori Garzio, on 4/8/19

Missing data: met_latnflx_minute, met_windavg_mag_corr_east, met_windavg_mag_corr_north, met_heatflx_minute, met_netlirr_minute, met_relwind_direction, met_relwind_speed, met_salsurf, met_current_direction, met_current_speed for deployments 6 and 7. From the provenance.json file, it appears that various cal coefficients are missing for both deployments: CC_height_of_windspeed_sensor_above_sealevel_m, CC_use_velpt, CC_depth_of_conductivity_and_temperature_measurements_m

Deployment 6 UID: CGINS-METLGR-00038. There is no cal sheet in github
Deployment 7 UID: CGINS-METLGR-00037: There is no cal sheet in github

https://github.com/ooi-integration/asset-management/tree/master/calibration/METBKA

By Lori Garzio, on 4/5/19

These variables are missing global ranges for this instrument: stream metbk_hourly - met_buoyfls, met_buoyflx, met_frshflx, met_heatflx, met_latnflx, met_mommflx, met_rainflx, met_sensflx, met_netsirr_hourly. stream metbk_a_dcl_instrument and metbk_a_dcl_instrument_recovered: met_windavg_mag_corr_east, met_windavg_mag_corr_north, met_heatflx_minute, met_latnflx_minute, met_netlirr_minute, met_sensflx_minute.

By Lori Garzio, on 4/5/19

eastward_velocity and northward_velocity (from the collocated VELPT) don't have any units or description in the recovered_host-metbk_a_dcl_instrument_recovered METBK .nc file for deployments 3 and 6.

By Lori Garzio, on 4/8/19

Missing data at the end of the deployment should be annotated.

By Lori Garzio, on 4/8/19

suspect data: met_current_speed

By Lori Garzio, on 4/8/19

recovered_host data are missing for several data products in the middle of deployment 3, but they are available in the telemetered data stream. These recovered_host data should be available.

By Lori Garzio, on 4/8/19

precipitation is negative at the beginning of the deployment.

By Lori Garzio, on 4/5/19

According to annotation ID 1381, no CT data are expected for deployment 1. However, sea_surface_temperature values are recorded at -5, and it looks like other variables are using that temperature in their calculations, which is creating bad data products. Excluding from summary data ranges

By Lori Garzio, on 4/5/19

The deployment 1 data should be annotated to explain why no recovered_host data are available. According to the ingest csv: "no recovered instrument data"

By Lori Garzio, on 4/5/19

met_current_speed, met_relwind_speed, met_wind10m, shortwave_irradiance, and met_netsirr global ranges should be reviewed. See review notes for CP01CNSM-SBD11-06-METBKA000 for more details.

By Lori Garzio, on 4/5/19