(also on emontgomery.tiddlyspot.com - http://tinyurl.com/b6cjjp)

Notes on processing ADV data

Use the newmetaADVExamples.m in m_cmg/trunk/hydratools to guide how to do processing.  The programs needed are also in that directory.

A summary of the standard processing steps used for ADV data after offload.

convert raw data to netCDF format
use browsehydraburst to evaluate burst data quality
in cleanhydra, use thumbfinger with high std. dev. (typically 10) to remove large spikes
in cleanhydra,use deglitch1vector with lower std. dev. (typically 2.8) to filter noise in bursts 
check that data results are as expected, re-do if thresholds weren't good
evaluate thresholds for vrange and brange
in cleanhydra, use fix_vbrange to despike v and b range data
use flagbadadv to review and flag any remaining data spikes
use adv2nc to convert to earth coordinates and output EPIC conventions

These are more nuts and bolt for how to accomplish the above.
1) prepare metadata
2) copy newmetaADVExamples.m to a name appropriate to the data (meta_moorid_adv.m)
3) edit the new file to incorporate metadata- the end of the metadata entry section is typcally at metadata.goodbursts.  

4) enable or disable the various sections defined in blocks by: 
	if 0 (or 1 to enable)
	end
4a) there are a variable number of steps in the processing- 
	the first step is adr2cdf.m that creates raw burst and statistics files
	the middle variable number of steps involve using cleanhydra to fix bad data
	then flagbadadv.m is used to mark any remaining data that may need removal
	  (this is interactive, and may not be needed if the data is clean)
	the last is adv2nc.m where the relative x,y,z data are converted to east, north and up
	   with associated conversion to using EPIC conventions 

5) invoke your meta_moorid_adv in matlab repeatedly to accomplish the various processing steps
6) use browsehydraburst to re-check the -cal.nc result

File naming summary-

Each step generates a burst file (*advb*), a statistics file (*advs*) and a quality file (*advq*). The burst file contains the time series for each variable for each burst.  The statistics file contains variables cointaining the statistics for all variables in each burst (mean, std, min, max)  as a timeseries.  The q file contains info on what was modified by each processing step.  Normally, we use different names at each step by incrementing the number following the b or s in the filename; the q file is appended to, so doesn't need to be renamed.    Typically the names are as follows:
####advb.cdf		raw burst data from logger in netCDF 
####advb1.cdf		thumbfinger applied to burst data in netCDF 
####advb2.cdf		deglitch1vector applied to burst data in netCDF 
####advb3.cdf		clip or fix_vbrange applied to raw burst data in netCDF 
			flagbadadv is usually modifeis an existing file, so no new name
####advb-cal.nc		best burst data converted to earth coordinates as EPIC

####advs.cdf		statistics of ####advb.cdf
####advs1.cdf		statistics of ####advb.cdf
####advs2.cdf		statistics of ####advb.cdf
####advs3.cdf		statistics of ####advb.cdf			
####advs-cal.nc		statistics of ####advb-cal.nc