210 likes | 340 Vues
This overview details the deployment of a waves array used to capture wave evolution during a coastal storm. It highlights the use of redundant acoustic surface tracking for quality checking and the flexibility provided by a "full profile" deployment to observe near-surface to near-bottom velocity oscillations. Key insights include error quantification in near-surface velocities, processing optimization procedures, and the use of tools like WaveView for data quality verification. The report summarizes early and peak storm energy parameters, alongside addressing issues related to pressure sensor accuracy and error management in directional spectra.
E N D
Rutgers ADCP Waves Array Data Review December 2005 Deployment
Overview • Deployment captures evolution of waves from a passing coastal storm. • Redundant acoustic surface track derived spectra allow quality checking of directional array. • Deployment with “full profile” allowed flexibility to observe velocity oscillations from near surface to near bottom • 4-Beam “error velocity” quantifies error in the instantaneous near surface velocities. • Setup to optimize processing is detailed
Waves Data QACheck List • Use WaveView to verify data quality ( *.wvs file) • Check for reasonable parameters in the time series (Hs, Tp, Dp) • Check error log • Check for agreement in 1-D spectra • Check for reasonable high frequency cutoff • Check for reasonable directional spectra
Early Storm Primary Energy = 9.1 sec. Secondary Energy = 5.5 sec.
Early Storm • Vertical Velocity Time Series
Early Storm • Direction Time Series
Early Storm • Magnitude Time Series
Early Storm • Error Time Series
Early Storm – Time Series • Error Time Series • Speed • Direction • Vertical
Peak of Storm Primary Energy = 10.7 sec. Secondary Energy = 3.0 sec.
Peak of Storm • Vertical Velocity Time Series
Peak of Storm • Direction Time Series
Peak of Storm • Magnitude Time Series
Peak of Storm • Error Time Series
Peak of Storm Time Series • Error Time Series • Speed • Direction • Vertical
Solution for Processing • Expert Options Required because of 75 cm “offset” in the pressure sensor. • Use Acoustic Surface Tracking for water level + primary non-directional estimate • Manually set bins for directional waves processing (#9-14) • Manually set High Frequency cutoff for velocity directional spectra to 0.36 hz • Set Processing FFT Length to 8192 points, post process to generate “hourly” average
Comparing Spectra • Why issue with velocity spectra when using pressure sensor to define tide? • Pressure For Water Level • Surface Tracking for Water Level
Why Error In Spectra? • Issue with Pressure Sensor, error of ~751 mm. • Range of Error 1209 to 584 mm