...
Add missing variables in L1 formattingwe will only use the ameriflux related oneamerfilux only L1 and mainstem L1, combine thesemanually change variables names to run pyfluxpro L1there are three variablesmaybe we can automate this by creating the changed variables first than convert it later using another mappingmaybe the above process is less priority
Make L1 formatting more efficientthere are several L1 files
Erroring variables : {AmeriFlux variable name -> PyFluxPro-friendly variable name} mapping belowLE->FeLE_SSITC_TEST->Fe_EP_QCLW_IN->FldLW_OUT->FluL2 formatting for AmeriFluxminor formatting issuespyfluxpro version changeserroring variables name to plot as wellempty data frames because of the deletion (no data, empty line)
Excel Formatting for the AmeriFlux- Run whole pipeline for a certain site probably using whole year
- Run PyFluxPro and others to generated the final output for AmeriFlux
How do we handle VWC, VWC1, automatically.- Submit output to AmeriFlux site
- Separate each steps and manually run the steps based on the user's need
- Check L1.txt variable names if exist in full_output and met_data_30 (less priority)
Case : Checking if Variables in L1.txt actually exists in full_output and Met_data_30 — input excel sheet to pyfluxpro.
variable name XYZ in L1_ameriflux. but this is not there in full-output and met-data-30.. pyfluxpro throws a warning. it runs. but we will catch this when submitting to ameriflux.
- Create unit test
- Google form?
- L2 checks for Variables section : https://github.com/OzFlux/PyFluxPro/wiki/Level-2#the-variables-section
- Currently we check for DependencyCheck, ExcludeDates and RangeCheck.
- PyFluxPro supports other checks as well, such as, DiurnalCheck, ExcludeHours, CorrectWindDirection, LinearCheck. But these are also not used by CABBI.
- Currently we check for DependencyCheck, ExcludeDates and RangeCheck.
Low Priority
- Data validation.
- user input validation
- data input validation
- QA / QC
- Logging
- Code clean up
- read/write module changes in utils
...