You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Date

Attendees

Yong Wook Kim

Bethany Blakely  

Rob Kooper 

Minu Mathew 

Taylor Pederson 

Agenda

  1. Run for 2020 whole year run
  2. AmeriFlux site submission
  3. 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?
  4. 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 ?
    1. 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.
    2. 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
    3. If the above is not feasible,
      1. 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).

Action items

  •  


  • No labels