...
- Run for 2020 whole year run
- AmeriFlux site submission
- Some 2020 met variables are not used in Ameriflux submission. Eg : Rs_net_Avg ' -> 'NetRs_Avg' and ' Rl_net_Avg ' -> ' NetRl_Avg. Should these names be changed?
- Some met variables are renamed using Ameriflux-Mainstem-Key . Eg : CM3Up_Avg'-> 'SWDn_Avg', 'CM3Dn_Avg'-> 'SWUp_Avg', Solar_Wm2_Avg -> SWDn_Avg (Currently this is being changed in L1_ameriflux.txt). Are there occasions where both of these names are present in raw met file ?
- CM3Up_Avg is present from Jan1 to May 1. SWDn_Avg is present from May 2 to Dec 31 for the same year / in the same raw met file.
- If we continue to use the current process, when this situation happens, we will get L1_ameriflux as below:
- [[SWIN]]
- [[[xl]]] var_name = CM3Up_Avg
- sheet_name = met_data_30
- [[SWIN]]
- [[[xl]]] var_name = SWDn_Avg
- sheet_name = met_data_30
- [[SWIn]]
- [[[xl]]] var_name = CM3Up_Avg
- var_name = SWDn_Avg
- sheet_name = metdata_30
- [[SWIN]]
- If the above is not feasible,
- Solution : We can change in the raw met file , during the met_merger. But we will need to changes these via code / have another key file ( additional input file).
- Soil heat flux calculation (Guide to Processing Flux data with eddypro and pyfluxpro document), is it shg_mv_Avg or shf_mv_Avg?
- "If soil heat flux is recorded in mV [shg_mV_Avg], that value will need to be multiplied with the shf calibration [shf_cal_Avg] value and entered in a new column title [shf_1_Avg] “shf_1_Avg=[shf_mV_Avg(1)]*[shf_cal_Avg(1)]”
Check for shf_Avg(1) and shf_Avg(2) if exists, if not check if shg_mV_Avg exists and do this. "
- "If soil heat flux is recorded in mV [shg_mV_Avg], that value will need to be multiplied with the shf calibration [shf_cal_Avg] value and entered in a new column title [shf_1_Avg] “shf_1_Avg=[shf_mV_Avg(1)]*[shf_cal_Avg(1)]”
...