So looking at the stage 2 processing files - we're not using consistent approaches across all sites for some variables - eg. soil heat flux, net radiation etc.
Stage 1 needs to be site specific of course, but I feel like stage 2 should be as uniform between sites as possible. Not all variables are available at all sites, but for those that are available across sites (eg. Net Radiation) we should try to ensure they are consistent.
For BB1/BB2: we run calc_avg_trace on SW & LW - both IN & OUT, then recal NETRAD from the cleaned componenets
For DSM/RBM/HOGG/YOUNG: we run calc_avg_trace on SW & LW - IN only and don't apply any cleaning to NETRAD
I'm wondering if it would make sense to have a "global" stage 2 ini file to define how we processes variables that are globally available - which could then be appended to (or called from) the site specific ini files.
If that won't work we should have some folks go through each and compare procedures between sites for consistency. But that could be tedious and won't be a permanent solution as thing could diverge anytime future edits are made.
So looking at the stage 2 processing files - we're not using consistent approaches across all sites for some variables - eg. soil heat flux, net radiation etc.
Stage 1 needs to be site specific of course, but I feel like stage 2 should be as uniform between sites as possible. Not all variables are available at all sites, but for those that are available across sites (eg. Net Radiation) we should try to ensure they are consistent.
I'm wondering if it would make sense to have a "global" stage 2 ini file to define how we processes variables that are globally available - which could then be appended to (or called from) the site specific ini files.