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: 2080 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: 1649 By: swhite
Flag: suspect Exclude: No

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: 1650 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: 1402 By: swhite

Missing.

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

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

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

The Wire-Following Profiler was intentionally converted into a fixed-depth instrument to prolong the battery endurance.

Id: 230 By: leila

Recovered data are not available because the Wire-Following Profiler motor and PAR cables were swapped and the data are thus unreliable.

Id: 228 By: leila

Telemetered data are sparse because telemetry schedule was irregular during this deployment.

Id: 232 By: leila

Data transmission interrupted.

Id: 605 By: leila

Deployments 8&9; 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: 1719 By: areed
Flag: suspect Exclude: No

Deployments 8&9; 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: 1720 By: areed
Flag: suspect Exclude: No

Deployment 13: 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: 1881 By: cdobson