How li-cor-environmental/eddypro-engine works
Project type and purpose
• This is the “EddyPro Engine,” a command-line, Fortran-based open-source application for processing eddy covariance data. It computes fluxes (H₂O, CO₂, CH₄, energy, etc.) via two main processing pipelines (RP and FCC). A separate GUI repository exists, but this tree is the engine itself.
File structure
• Top level:
• prj/Makefile and scripts to build two executables: “rp” (run processing) and “fcc” (frequency correction chain).
• src/: three subdirectories:
– src_common/: core Fortran modules and utilities shared by both pipelines (I/O, statistics, metadata, math, file handling, exception handling).
– src_rp/: modules implementing the “Run Processing (RP)” workflow—time-lag correction, statistical tests, flux computation, biomet data integration, output routines.
– src_fcc/: modules implementing the “Frequency Correction Chain (FCC)” workflow—spectral analysis, cospectral modeling, correction functions, output routines.
• No traditional frontend/backend split; it’s a monolithic CLI engine organized into modular pipelines built and invoked via Makefile.
Insights from README
• Two independent processing modes (RP and FCC).
• Build instructions: gfortran, prj/Makefile target “make rp” and “make fcc.”
• Dependencies: Fortran compiler, shell scripts, 7-Zip and pausep utilities in bin/.
Elements
• Clear labels on each block (e.g., “Configuration Parser,” “Common Core,” “RP Pipeline”)
• From CLI to Config → Core → Pipeline → Output
• From Pipeline back to Core for shared utilities
• CLI (e.g., green)
• Shared modules (blue)
• RP modules (orange)
• FCC modules (yellow)
• External utilities (gray)
• File system/external data (brown)
Detailed capture of essential elements
• src_common/ as a library block subdivided into I/O, Math, Statistics, Exception Handling
• src_rp/ and src_fcc/ as separate pipeline blocks showing major functional groupings (e.g., “Time-lag correction,” “Statistical tests,” “Spectral analysis,” “Model fitting”)
• prj/Makefile and build scripts as the “Build & Deployment” block
• External utilities as side‐blocks called by the pipelines