HyCODE Data Highlights
Data CDs are available for all 3 deployments. Please contact grace.chang@opl.ucsb.edu if you would like one sent to you.
(Click on images for larger versions)
Plots of ADCP east (blue) and north (cyan) component velocity time series (left) and
stickplots (12-hour averaged; right) at several depths over the period of 17 May - 15 September 2000. The mean current speed over the two
deployments is 19.5 cm/s. Transport directions were mainly toward the south, particularly during times of highest current
velocities. Notice the turning of the currents starting on approximately 18 June and continuing for about one month. This
could have been the growth of a cyclonic eddy from the nearshore southward coastal jet that has been observed in past field
experiments in the area (LEO-15).
Data Report for sensor functionality).
These time series, in general, exhibit the seasonal stratification of the water column with episodic mixing by various physical processes.
The HyCODE site was heavily influenced by relatively low-salinity, high-temperature estuarine flows at the near-surface during the
beginning of the first deployment. These estuarine flows correlate with relatively high southward current velocities. The extreme
mixing event (near-bottom water increased by nearly 10oC over one day) correlates with the highest southwestward flow observed
over the two deployments.
PAR at 5, 11, and 20 m.
Time series of ac-9 data (absorption (a), scattering (b), and attenuation (c) coefficients at nine wavelengths) at 5 (left), 11 (middle), and 20 m (right ).
The increase in near-surface a, b, and c during the end of July was possibly due to advection of higher biomass waters to the HyCODE site.
Note that this is the time period of intensive shipboard and aircraft sampling by HyCODE investigators.
Left: Beam attenuation at 660 nm wavelength at 5 and 11 m. Right: Chlorophyll-a concentration derived from fluorometers
at 5 and 11 m. These time series correlate well with each other and to ac-9 time series.
Hydroscat-6 data from deployment 2.
|