I'm from the Australian Ozflux community. I recently read A Brief Practical Guide to
Eddy Covariance Flux Measurements and then followed on with the 5 part series in your webinar (I wish I'd been led to it all sooner!).
At Ozflux, we have our own processing pathway. The raw fluxes are process in the Campbell Sci loggers (but we keep both the raw data and 30min averages) and then analysed through a Python coded pathway.
I'm interested in how EddyPro compares and also in describing our footprint from the data itself (currently, I use the rule of thumb for my 20m tower and analysis of wind direction). What I've found with EddyPro is that the raw data is broken up into files relating to the averaging period. Our raw data on the other hand is broken up only by collection periods (ie. in my case, roughly once a month).
Is there a way of tell EddyPro that it's a long file that needs to be averaged into 30min points or will it only work to raw data file lengths for its averages?