During descending profiles, the vertical velocity estimates may be incorrect due to interference with beam 3 measurements arising from the nearby CTD sensor. Users should cross-compare these vertical velocity estimates with those derived from the CTD pressure record to determine profiles of possible concern. Good vertical velocity estimates will closely align with the CTD derived estimates. Regardless, there should be minimal impact on the estimates of the horizontal velocities. However, care should be taken with these estimates to confirm this conclusion.

Id: 1659 By: swhite
Flag: suspect Exclude: No

Deployment 1: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.

Id: 2091 By: swhite
Flag: fail Exclude: Yes

During descending profiles, the vertical velocity estimates may be incorrect due to interference with beam 3 measurements arising from the nearby CTD sensor. Users should cross-compare these vertical velocity estimates with those derived from the CTD pressure record to determine profiles of possible concern. Good vertical velocity estimates will closely align with the CTD derived estimates. Regardless, there should be minimal impact on the estimates of the horizontal velocities. However, care should be taken with these estimates to confirm this conclusion.

Id: 1660 By: swhite
Flag: suspect Exclude: No

UPDATED, 2020-04-15: Corrected algorithm has been uploaded to the system and is active. * The algorithm supplied by the vendor to calculate water velocities is incorrect. Corrected code is currently in review.

Id: 1407 By: swhite

Wire Following Profiler is stuck around 55 dbar.

Id: 1393 By: leila

Wire Following Profiler is stuck at the bottom of its range.

Id: 1394 By: leila

Missing

Id: 569 By: leila
Flag: not_available Exclude: No

Deployment 5-7: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.

Id: 2092 By: swhite
Flag: fail Exclude: Yes

Wire Following Profiler is stuck at the top of its range.

Id: 613 By: leila

Failed

Id: 354 By: leila
Flag: not_operational Exclude: No

Deployment 8; During the times indicated by the start and end times of this annotation, the VEL3D instrument on the Profiler contained a firmware bug which caused beam 3 (downward-facing) to be on during ascents, and beam 1 (upward-facing) to be on during descents, instead of vice versa. Therefore the issue of incorrect vertical velocity estimates due to interference with the CTD noted in a previous annotation will affect the ascending profiles rather than the descending profiles.

Id: 1731 By: areed
Flag: suspect Exclude: No

Deployment 8; During the times indicated by the start and end times of this annotation, the VEL3D instrument on the Profiler contained a firmware bug which caused beam 3 (downward-facing) to be on during ascents, and beam 1 (upward-facing) to be on during descents, instead of vice versa. Therefore the issue of incorrect vertical velocity estimates due to interference with the CTD noted in a previous annotation will affect the ascending profiles rather than the descending profiles.

Id: 1732 By: areed
Flag: suspect Exclude: No

Deployment 8: Wire-Following Profiler stopped transmitting data. Issue identified as a software problem.

Id: 227 By: leila
Flag: not_available Exclude: No

Deployment 9: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.

Id: 2093 By: swhite
Flag: fail Exclude: Yes

Deployment 12: Due to a clock rollover issue, all WFPs have ceased sampling on 1/1/2020. No WFP data are being collected after this date. A resolution is being researched by the vendor.

Id: 1885 By: cdobson