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

Id: 2088 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: 1655 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: 1656 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: 1405 By: swhite

Only few records available. The Wire-Following Profiler failed after few days and had to be recovered.

Id: 732 By: leila

The Wire-Following Profiler was not performing correctly because of visible damage observed when recovered.

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

All communication to the Wire-Following Profiler were lost and no data are expected.

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

Data not recoverable.

Id: 554 By: leila

Telemetered data end on 27 Jan 2015.

Id: 733 By: leila

Surface buoy mal functioning.

Id: 735 By: leila

The surface buoy departed and had to be recovered.

Id: 736 By: leila

Telemetered data end on 2 Oct 2015.

Id: 734 By: leila

The Wire-Following Profiler failed.

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

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

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

The Wire-Following Profiler is stuck at the top of its range. The problem is assumed to be related to fouling of the line.

Id: 43

The Wire-Following Profiler is stuck at the top of its range. The problem is assumed to be related to fouling of the line.

Id: 44

The Wire-Following Profiler is stuck at the top of its range. The problem is assumed to be related to fouling of the line.

Id: 45 By: leila

Deployment 10; 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: 1727 By: areed
Flag: suspect Exclude: No

Deployment 10; 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: 1728 By: areed
Flag: suspect Exclude: No

Deployment 10: The Wire-Following Profiler is stuck at the top of its range.

Id: 939 By: leila

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

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

Deployment 13: WFP is likely stuck and profiles became erratic starting 2019-06-18.

Id: 1626 By: cdobson

Deployment 14: 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: 1884 By: cdobson