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: 2085 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: 1653 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: 1654 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: 1404 By: swhite

No telemetered data available because the surface buoy went adrift .

Id: 723 By: leila

Instrument setting under investigation. Velocity data are unreasonable because the number of beams should be 3 not 0.

Id: 726 By: leila
Flag: fail Exclude: No

MMP failed. No telemetered data are available. The list of files got too long for the inductive modem and time run out to search and send out the data files via telemetry.

Id: 724 By: leila

Instrument setting under investigation. Velocity data are unreasonable because the number of beams should be 3 not 0.

Id: 727 By: leila
Flag: fail Exclude: No

Velocity data are unusually spiky.

Id: 731 By: leila
Flag: suspect Exclude: No

Possible causes: istrument damaged or instrument at fault and stopped sending data.

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

Data with correct format are not available.

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

No telemetered data available because surface buoy broke free.

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

Wire Following Profiler profiling erratically and sometimes unable to reach the programmed top depth.

Id: 606 By: leila

No telemetered data available because surface buoy broke free.

Id: 116 By: leila

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

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

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

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

Instrument setting under investigation. Velocity data are unreasonable because the number of beams should be 3 not 0.

Id: 728 By: leila
Flag: fail Exclude: No

Instrument setting under investigation. Velocity data are unreasonable because the number of beams should be 3 not 0.

Id: 729 By: leila
Flag: fail Exclude: No

Instrument setting under investigation. Velocity data are unreasonable because the number of beams should be 3 not 0.

Id: 730 By: leila
Flag: fail Exclude: No

Wire Following Profiler profiling erratically and sometimes unable to reach the programmed top depth.

Id: 607 By: leila

No telemetered data available because the surface buoy went adrift after a series of strong winter storms.

Id: 236 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: 1725 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: 1726 By: areed
Flag: suspect Exclude: No

Deployment 10: Surface buoy went adrift following a large storm on 02 March 2018.

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

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

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

Deployment 12: Erratic profiles 2019-03-24 through 2019-03-26 and 2019-04-03 onward until recovery.

Id: 1624 By: cdobson

Deployment 14: Starting 11/29/2019 WFP01 was unable to complete full range descending profiles.

Id: 1829 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: 1883 By: cdobson