suspect data

By Leila Belabbassi, on 6/13/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

Data arrays are all fill values for every deployment for fdchp_a_tmpatur, fdchp_a_windtur_north, fdchp_a_windtur_up, fdchp_a_windtur_west, fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, fdchp_a_fluxmom_crosswind (Redmine 13402). There are several errors listed in the computed_provenance section of the provenance.json files (one example file attached). When this issue is resolved annotation ID 1395 should be updated.

By Lori Garzio, on 6/7/19

There are no global ranges in the system for this instrument for fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, and fdchp_a_fluxmom_crosswind

By Lori Garzio, on 6/7/19

Data arrays are all fill values for fdchp_a_tmpatur, fdchp_a_windtur_north, fdchp_a_windtur_up, fdchp_a_windtur_west, fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, fdchp_a_fluxmom_crosswind (Redmine 13402). There are several errors listed in the computed_provenance section of the provenance.json files (one example file attached). When this issue is resolved annotation ID 1396 should be updated.

By Lori Garzio, on 6/7/19

There are no global ranges in the system for this instrument for fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, and fdchp_a_fluxmom_crosswind

By Lori Garzio, on 6/7/19

Annotation ID 544: recovered data are missing. These data should be available for download or the annotation should be updated to explain why the data aren't available.

By Lori Garzio, on 6/7/19

Data arrays are all fill values for every deployment for fdchp_a_tmpatur, fdchp_a_windtur_north, fdchp_a_windtur_up, fdchp_a_windtur_west, fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, fdchp_a_fluxmom_crosswind (Redmine 13402). There are several errors listed in the computed_provenance section of the provenance.json files (one example file attached). When this issue is resolved annotation ID 1397 should be updated.

By Lori Garzio, on 6/7/19

There are no global ranges in the system for this instrument for fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, and fdchp_a_fluxmom_crosswind

By Lori Garzio, on 6/7/19

The missing data for the majority of deployments 1 and 5 should be annotated.

By Lori Garzio, on 6/7/19

Data arrays are all fill values for every deployment for fdchp_a_tmpatur, fdchp_a_windtur_north, fdchp_a_windtur_up, fdchp_a_windtur_west, fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, fdchp_a_fluxmom_crosswind (Redmine 13402). There are several errors listed in the computed_provenance section of the provenance.json files (one example file attached). When this issue is resolved annotation ID 1398 should be updated.

By Lori Garzio, on 6/7/19

recovered_inst data for deployment 6 are not available for download. These data should be available or annotated to explain why they aren't available.

By Lori Garzio, on 6/7/19

There are no global ranges in the system for this instrument for fdchp_a_fluxhot, fdchp_a_fluxmom_alongwind, and fdchp_a_fluxmom_crosswind

By Lori Garzio, on 6/7/19

Re annotation ID 1376 for this instrument - the equivalent annotation on CE02SHSM-SBD12-08-FDCHPA000 (ID 1373) was updated by wingardc: "UPDATED, 2019-02-05: Per communication with the instrument subject matter expert, the onboard processing error applies only to the motion-corrected wind speed and flux calculations. Those parameters are marked here with a QC Flag = "fail". All other measurements are considered to be good. Users should only use the motion-corrected wind speed and flux data from the recovered instrument data stream." This information presumably also applies to this instrument and should be communicated to users.

By Lori Garzio, on 6/7/19

Re annotation ID 1375 for this instrument - the equivalent annotation on CE02SHSM-SBD12-08-FDCHPA000 (ID 1373) was updated by wingardc: "UPDATED, 2019-02-05: Per communication with the instrument subject matter expert, the onboard processing error applies only to the motion-corrected wind speed and flux calculations. Those parameters are marked here with a QC Flag = "fail". All other measurements are considered to be good. Users should only use the motion-corrected wind speed and flux data from the recovered instrument data stream." This information presumably also applies to this instrument and should be communicated to users.

By Lori Garzio, on 6/7/19

Re annotation ID 1374 for this instrument - the equivalent annotation on CE02SHSM-SBD12-08-FDCHPA000 (ID 1373) was updated by wingardc: "UPDATED, 2019-02-05: Per communication with the instrument subject matter expert, the onboard processing error applies only to the motion-corrected wind speed and flux calculations. Those parameters are marked here with a QC Flag = "fail". All other measurements are considered to be good. Users should only use the motion-corrected wind speed and flux data from the recovered instrument data stream." This information presumably also applies to this instrument and should be communicated to users.

By Lori Garzio, on 6/7/19

Unusual spike in irradiance at the beginning of deployment 4 at wavelength=683nm. excluding from final data ranges.

By Lori Garzio, on 6/7/19

Suspect data towards the end of the deployment. Excluding from final data ranges.

By Lori Garzio, on 6/6/19

Data periodically flatline. This should be annotated if there was an issue with the instrument. Excluding from final data ranges.

By Lori Garzio, on 6/6/19

A substantial percentage (between 20-60%) of data are outside of global ranges for every deployment. Zooming in on the x-axis in the plots shows that all of the values that are outside of global ranges are slightly negative.

By Lori Garzio, on 6/6/19