There are several days during deployments 1, 2, and 3 where recovered_wfp data are not available but telemetered data are available. These data should be available in the recovered_wfp data streams.

By Lori Garzio, on 8/8/19

Annotation ID 1403 needs to be updated when the algorithm is fixed.

By Lori Garzio, on 8/8/19

vel3d_k_pressure (dbar) is an array of all fill values for every deployment.

By Lori Garzio, on 8/8/19

Annotation ID 1401 needs to be updated when the corrected code is provided.

By Lori Garzio, on 8/8/19

Suspect profile in Oct 2016

By Lori Garzio, on 8/8/19

Unreasonably high chl-a and backscatter outliers are scattered throughout all deployments.

By Lori Garzio, on 8/8/19

Suspect data for deployment 1 - see annotation ID 750

By Lori Garzio, on 8/8/19

Missing the pressure coordinate for deployment 1.

By Lori Garzio, on 8/8/19

The estimated_oxygen_concentration values shift substantially from deployment 1 (165-200 umol/L) to deployment 3 (200-235 umol/L) - DO shouldn't change that much at that depth. A similar shift in DO data between deployments 3 and 4 for GP02HYPM-WFP03-03-DOSTAL000 was observed by a SME (see annotation ID 1444). This should be investigated.

By Lori Garzio, on 8/8/19

Suspect data - instrument appears to have failed halfway through the deployment

By Lori Garzio, on 8/8/19

Suspect data for deployment 1 - see annotation ID 750

By Lori Garzio, on 8/8/19

I submitted a helpdesk question on 11/12/2018 regarding an offset between recovered and telemetered data for all global HYPMs: "There appears to be a substantial offset between data with the same timestamps from recovered_wfp and telemetered methods for all deployments of all global WFP CTDs, and I have included information from two representative deployments of two different profilers as examples. It looks like the values recorded for the first common timestamp are exactly the same, and as the profiler moves along in time the offset between the values recorded for the same timestamp become increasingly more offset. Then, the profiler reaches the end of the profile (either at its shallowest or deepest point), resets, and the pattern begins again. This is most easily seen in the pressure data, but there is an offset for all science parameters.

Examples:
GI02HYPM-WFP02-04-CTDPFL000 deployment 1
GP02HYPM-WFP02-04-CTDPFL000 deployment 3

The *_intersect.csv files attached contain data where recovered and telemetered timestamps intersect. For each timestamp and science parameter there are recorded values (from .nc files downloaded from the system) and the difference. For each parameter, the difference between the values at the bottom and top of the profiler's range are exactly zero, and (particularly for pressure) the differences steadily increase until they are reset at zero at the bottom/top of the profile. This pattern continues throughout the deployment. The plots attached are zoomed in to one upcast and one downcast, and highlight the offset in the data between the two methods."

Redmine 13743

By Lori Garzio, on 8/8/19

I submitted a helpdesk question on 11/12/2018 regarding an offset between recovered and telemetered data for all global HYPMs: "There appears to be a substantial offset between data with the same timestamps from recovered_wfp and telemetered methods for all deployments of all global WFP CTDs, and I have included information from two representative deployments of two different profilers as examples. It looks like the values recorded for the first common timestamp are exactly the same, and as the profiler moves along in time the offset between the values recorded for the same timestamp become increasingly more offset. Then, the profiler reaches the end of the profile (either at its shallowest or deepest point), resets, and the pattern begins again. This is most easily seen in the pressure data, but there is an offset for all science parameters.

Examples:
GI02HYPM-WFP02-04-CTDPFL000 deployment 1
GP02HYPM-WFP02-04-CTDPFL000 deployment 3

The *_intersect.csv files attached contain data where recovered and telemetered timestamps intersect. For each timestamp and science parameter there are recorded values (from .nc files downloaded from the system) and the difference. For each parameter, the difference between the values at the bottom and top of the profiler's range are exactly zero, and (particularly for pressure) the differences steadily increase until they are reset at zero at the bottom/top of the profile. This pattern continues throughout the deployment. The plots attached are zoomed in to one upcast and one downcast, and highlight the offset in the data between the two methods."

Redmine 13743

By Lori Garzio, on 8/8/19

I submitted a helpdesk question on 11/12/2018 regarding an offset between recovered and telemetered data for all global HYPMs: "There appears to be a substantial offset between data with the same timestamps from recovered_wfp and telemetered methods for all deployments of all global WFP CTDs, and I have included information from two representative deployments of two different profilers as examples. It looks like the values recorded for the first common timestamp are exactly the same, and as the profiler moves along in time the offset between the values recorded for the same timestamp become increasingly more offset. Then, the profiler reaches the end of the profile (either at its shallowest or deepest point), resets, and the pattern begins again. This is most easily seen in the pressure data, but there is an offset for all science parameters.

Examples:
GI02HYPM-WFP02-04-CTDPFL000 deployment 1
GP02HYPM-WFP02-04-CTDPFL000 deployment 3

The *_intersect.csv files attached contain data where recovered and telemetered timestamps intersect. For each timestamp and science parameter there are recorded values (from .nc files downloaded from the system) and the difference. For each parameter, the difference between the values at the bottom and top of the profiler's range are exactly zero, and (particularly for pressure) the differences steadily increase until they are reset at zero at the bottom/top of the profile. This pattern continues throughout the deployment. The plots attached are zoomed in to one upcast and one downcast, and highlight the offset in the data between the two methods."

Redmine 13743

By Lori Garzio, on 8/5/19

Missing the pressure coordinate for deployment 1.

By Lori Garzio, on 8/8/19

Missing the pressure coordinate for deployment 1

By Lori Garzio, on 8/8/19

Suspect data for deployment 1 - see annotation ID 750

By Lori Garzio, on 8/8/19

Suspect data - gradual shift in salinity at the beginning of the deployment.

By Lori Garzio, on 8/8/19

Suspect data for deployment 1 - see annotation ID 750

By Lori Garzio, on 8/7/19

Too much variability in conductivity, salinity, and density values at the beginning of the deployment.

By Lori Garzio, on 8/7/19