Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Automate / code PyFluxPro “Creating the Database” section. (Done)
    1. Test with various dataset.
      1. Run EddyPro for Jan 2021 with 2 weeks data
      2. Make the below changes for the file output from Eddypro run:
        1. Match the meta data header rows in both files.
        2. Change timestamp format
        3. Convert temperature units for various columns
        4. Convert units and rename column
        5. Timestamp checks - check the first and last timestamps - should be 00:00 and 23:00.(we don't need to do it, confirmed to Bethany)
      3. Manual entry of 2 sheets in excel. Copy output files from preprocessor.py and the changed output file from EddyPro run.
      4. Install and run PyFluxPro
    2. Man hours = approx. 15 hours
  2.  Create a function to check if required variables are available and correctly formatted for eddypro in format.py
    1. Required variables : Ambient Relative Humidity (RH), Global Radiation (SWIN), Longwave Incoming Radiation (LWIN), Photosynthetically Active Radiation (PPFD) (Done)
    2. Check the variable upper/lower case names. (Done)
    3. Check if eddypro reads variables in case-sensitive manner.
      1. EddyPro labels are case-sensitive. The data will not get read to EddyPro.
    4. Man hours = approx. 4 hours
  3. Test preprocessor.py, format.py and eddypro headless with Sept - Oct 2020 data. (Mac has a problem)
    1. Man hours = approx. 2 hours
  4. Create a function for quality check in precip data. This should be in preprocessor.py.
    1. Missing timestamp check : the function should break and write the till then processed output to file.
    2. Possible data values check : The range of precip data is 0-0.2 mm. the function should break and write the till then processed output to file.
    3. Man hours = approx. 4 hours
  5. Formatting the EddyPro output for AmeriFlux publication (changing the variables)
    1. L1 processing
    2. L2 Processing
    3. Man hours = approx. two days per L1 and L2

Other Tasks

  1. Test run eddypro_rp in macOS.
    1. Resolve the current error of

      Code Block
      NCSA-xxx:bin minum$ ./eddypro_rp "xx/xxx/xxx/templates/templates.eddypro"
       *******************
       Executing EddyPro 
       *******************
      sh: -c: line 0: unexpected EOF while looking for matching `"'
      sh: -c: line 1: syntax error: unexpected end of file
       Reading EddyPro project file: /xx/xxx/xxx/xx/templates/templates.eddypro..
       Done.
      sh: -c: line 0: unexpected EOF while looking for matching `"'
      sh: -c: line 1: syntax error: unexpected end of file
       Fatal error(86)> Could not retrieve files from directory. Either directory does not exist
       Fatal error(86)> or it does not contain files matching the selected requirements.
       Fatal error(86)> Program execution aborted.
      STOP 1


  2. Use python packages to convert units (cf_units or udunits) in format.py and preprocessor.py
    1. Yong Wook Kim will look into this
  3. Compare output from EddyPro
    1. will coordinate with Bethany Blakely 
  4. Compare the eddypro output with the manual input file and the automated input file.
    1. will coordinate with Bethany Blakely 
  5. Automate / code PyFluxPro “Formatting the PyFluxPro Control Files” - I think this does not require any man hours as these files are already shared by Bethany.
  6. Work on automated data acquisition Yong Wook Kim 
  7. Make pyfluxpro run in the pipeline Yong Wook Kim 
  8. Possibly dockerize the process (What should be the output delivery) Yong Wook Kim 
  9. Add an web site like Pecan for showing the necessary information (weather, site, etc) Minu Mathew