Introduction
######################################################################
This is a readme file for a data set collected by the OSU Ocean Mixing
Group during the August 2005 and May 2006 River Influences on Shelf
Ecosystems (RISE) cruise.  The data has been processed and compiled
into this form by Levi Kilcher.

License
######################################################################
This data is intended for use by members of the RISE project only.
All others must recieve prior consent from the OSU Ocean Mixing Group
before obtaining or using this data in any way.

Data Format
######################################################################
-The data is provided in a single Matlab 7 format file:
	timeSeries.mat
-This file provides a compact way of looking at a large fraction of
the data from this cruise.
-This file contains a single structured variable tms.
-Data below 50 meters has been dropped out of this data set.
-IMPORTANT NOTE: The last bin in each Chameleon drop is actually the
average over the meter above the bottom of the drop.  This means
that the last non-NaN point in EACH column of EACH chameleon variable
(this issue does not apply to velocity data, which does not even
contain data near the bottom) is actually taken as the average over
the 1-meter above the end of the profile.  This means that these
points do not fall exactly on the depth grid tms.depth.  In order to
find the exact depth of each bin use pressure (tms.P).  When simply
looking at the data as provided, this should not be too much of an
issue, i.e. tms.depth should work fine as a depth axis.

Variables/Units
#######################
This is a list of all variables in this data set, their associated
units, and definitions.

IMPORTANT NOTE: Historically, we've made variables available which
were not quality controlled.  Therefore, if you downloaded data prior
to Feb-20-2006, be aware that many variables (particularly turbulence
variables: EPSILON, Krho) are inaccurate and unfit for publishing or
other interpretation.


_Variable_	_Units_		_Definition_

time		Matlab Time	Time

lon		decimal degrees	Longitude

lat		decimal degrees	Latitude

depth		meters		Depth

ind1				Position indices for points along line "1"

ind4				Position indices for points along line "4"

N_cham				Number of chameleon drops in the given profile

N_adcp				Number of 30 second profiles in the given profile

P		dbar		Pressure

T		C		Temperature

C		S/m		Conductivity

S		psu (ppt)	Salinity

THETA		C		Potential Temperature

SIGMA		kg/m^3		(Potential Density)-1000

N2		1/s^2		Square of Bouyancy frequency

EPSILON		W/kg (m^2/s^3)	Energy Dissipation Rate

Krho		m^2/s		Turbulent Eddy Diffusivity

DTDZ		C/m		Vertical Temperature Gradient

DRHODZ		kg/m^2		Vertical Density Gradient

OBS		Volts**		Optical Backscatter

FLR		???Volts???	Fluorescence

tau_b		N/m^2		Bottom Stress = ustar^2*rho_0

u		m/s		Eastward velocity

v		m/s		Northward velocity

w		m/s		Vertical Velocity (positive upward)

bottom		meters		Bottom depth as measured by ADCP

p_max		dbar		Max pressure of chameleon drop


Notes
######################################################################
The fields "ind1" and "ind4" have been included in this variable.
They are the indices for lines "1" (a not quite north-to-south line)
and "4" (a east-to-west line) respectively.  These variables were
included as a simple way to properly and efficiently obtain data along
these two lines. 
If you have no idea what I am talking about, try:
plot(tms.lon,tms.lat)
then try:
plot(tms.lon(tms.ind1),tms.lat(tms.ind1),tms.lon(tms.ind4),tms.lat(tms.ind4))
Hopefully this will make it all clear.

To get a variable (e.g. Salinity) along one of these lines (e.g. line
4), try:
S=tms.S(:,tms.ind4,:);

Hopefully this helps clarify what these variables are for.
Finally, FYI, the data was organized in this way because the two lines
crossed, and in order to avoid repeating data, the data was saved in
this form.  The crossing point of these two lines was saved as the
first column becuase it was assumed that it would be looked at the
most frequently - it has the most data.


######################################################################
This readme was written by Levi Kilcher
Updated: 8/24/2006