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: 1631 By: wingardc
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: 1632 By: wingardc
Flag: suspect Exclude: No

UPDATED, 2019-03-11: 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: 1400 By: lgarzio

UPDATED, 2019-03-11: 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: 1662 By: wingardc

The bulkhead connector for the PAR sensor failed and shorted the profiler power system to seawater, draining the profiler battery pack in fairly short order. No data is available for this time period.

Id: 1663 By: wingardc
Flag: not_available Exclude: No

The bulkhead connector for the PAR sensor failed and shorted the profiler power system to seawater, draining the profiler battery pack in fairly short order. No data is available for this time period.

Id: 1664 By: wingardc
Flag: not_available Exclude: No

The surface expression for the profiler mooring broke free during a storm event on December 06, 2015 and ended up drifting north to Vancouver Island where it was recovered. No further telemetered data will be available from this mooring or profiler system for this deployment.

Id: 1665 By: wingardc
Flag: not_available Exclude: No

The surface expression for the profiler mooring broke free during a storm event in October 2016. On March 13, 2017, the subsurface sphere came to the surface and drifted north towards Vancouver Island where it was recovered from the shore. The mooring wire was severed near the base and showed signs of abrasion and other damage consistent with a ship strike. The profiler was no longer on the wire and is presumed lost at sea. No recovered profiler data is available for this deployment.

Id: 1661 By: wingardc
Flag: not_available Exclude: No

UPDATED, 2017-03-13: The subsurface float came to the surface at 06:16 UTC and drifted north towards Vancouver Island where it was recovered. The mooring wire was severed and showed signs of abrasion and other damage consistent with a ship strike. The profiler was no longer attached to the wire and is presumed lost at sea. * The buoy of the offshore Washington profiler went adrift at sometime around noon local time October 14, 2016. The subsurface beacons have not reported, so it is likely that the stretch hose between the buoy and the subsurface float parted, just as it did last year. If this is the case, the profiler is continuing to collect data, but it is no longer able to telemeter data to shore.

Id: 925 By: michaesm
Flag: not_available Exclude: No

At noon on July 10, 2017, the IMM port of the profiler mooring was turned off due to the incorrect configuration of the VEL3D-K. The instrument's sample rate was set too high, resulting in unusually large data files which caused a significant increase in the IMM telemetry time and an unsustainable power draw from the profiler battery pack. To insure the profiler continues to collect data over the course of the deployment, the IMM will remain off for the duration of the Spring/Summer 2017 deployment.

Id: 96 By: m.vardaro
Flag: not_available Exclude: No

Battery pack on the profiler is getting low. To conserve power for profiling, data telemetry has been disabled.

Id: 1666 By: wingardc
Flag: not_available Exclude: No

Battery pack on the profiler was getting low. Sensors did not have enough power to fully operate (most noticeable in the VEL3D-K data streams), and the profiler did not have enough power to descend to the full operating depth. Stopped operating altogether on 2019-04-26 after completing 1728 profiles over the course of the deployment.

Id: 1667 By: wingardc
Flag: not_available Exclude: No

Data indicates that profiler travel up the wire is periodically blocked near 150 m, keeping it from fully ascending during a profile. Suspect fouling on the wire is impeding travel.

Id: 1830 By: wingardc

Due to a clock rollover issue, all WFPs ceased sampling on 2020-01-01. No further WFP data are being collected from this system. A resolution is being researched by the vendor.

Id: 1905 By: wingardc
Flag: not_operational Exclude: No