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: 1647 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: 1648 By: swhite
Flag: suspect Exclude: No

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

Deployment 1; 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: 1718 By: areed
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: 1401 By: swhite

Deployment 2: The WFP slid up the wire between profiles on various dates including 2019-01-01, 2019-01-29, and from 2019-02-05 through 2019-02-07.

Id: 1623 By: cdobson

Deployment 2: The WFP becamestuck at 25m from 2019-02-11 through 2019-02-18.

Id: 1622 By: cdobson

Deployment 2: Telemetry of data from the WFP ceased on 2019-02-21.

Id: 1621 By: cdobson

Deployment 3: Starting 12/03/2019 WFP01 was unable to complete full range descending profiles.

Id: 1842 By: cdobson
Flag: not_operational Exclude: No

Deployment 3: 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: 1879 By: cdobson