Overview

EddyPro is a powerful open source software application for processing eddy covariance data. It computes fluxes of water vapor (evapotranspiration), carbon dioxide, methane, other trace gases, and energy with the Eddy Covariance method. EddyPro is developed, maintained and supported by LI‑COR Biosciences. It originates from ECO₂S, the Eddy COvariance COmmunity Software project, which was developed as part of the Infrastructure for Measurement of the European Carbon Cycle (IMECC-EU) research project. We gratefully acknowledge the IMECC consortium, the ECO₂S development team, the University of Tuscia (Italy) and scientists around the world who assisted with development and testing of the original version of this software.
Sample datasets for EddyPro Engine can be found here.

Using

Use the module name eddyproengine to discover versions available and to load the application.

Use eddyproengine_rp --help or eddyproengine_fcc --help to learn more.

To run on EddyPro Engine on the cluster, the folders tmp and output need to be created inside of the directory that contains the project file.

Multicore

Currently, there does not appear to be any documentation that demonstrates that eddyproenginecan run in a parallel fashion over multiple cores/nodes. So, only request a single node and core when using.

Running Jobs:

A user (working with the developers) has informed us that “only one instance of an executable can be run at a time, and they need their own separate environment and output directories to function as well.“

If you are experiencing issues, please contact us and we can try and coordinate with other users running this application at the same time.

GUI

The GUI version of EddyPro Engine is available to download for Windows and Mac OS from here. The GUI version is not supported on the cluster.

Projects and data files can be created on the local desktop and then uploaded to the cluster or created from a local desktop on Alcova storage.

To use EddyPro project files on the cluster then some edits need to be made to the project file by editing it with a text editor. In order to get the project to work on your local desktop again the pathing in the project file will need to be reverted to what it was before.

Edits To Local Desktop Project Uploaded To Cluster

The following is an example of the pathing set in the project file that was created on a local desktop and uploaded to the cluster:

file_name=C:/Users/<user>/<eddypro_project_folder>/<eddypro_project_name>.eddypro
out_path=C:/Users/<user>/<eddypro_project_folder>/results
data_path=C:/Users/<user>/<eddypro_project_folder>/<directory_of_data>

To use on the cluster this needs to be edited to:

file_name=/project/<project_name>/<user_name>/<eddypro_project_folder>/<eddypro_project_name>.eddypro
out_path=/project/<project_name>/<user_name>/<eddypro_project_folder>/results
data_path=/project/<project_name>/<user_name>/<eddypro_project_folder>/<directory_of_data>

Edits To Project Using Alcova

The following is an example of the pathing set in the project file that was created using the Windows GUI version of EddyPro and saved on Alcova:

file_name=//alcova.arcc.uwyo.edu/project/<your_project>/<eddypro_project_example>/<eddypro_project_name>.eddypro
out_path=//alcova.arcc.uwyo.edu/project/<your_project>/<eddypro_project_example>/output
data_path=//alcova.arcc.uwyo.edu/project/<your_project>/<eddypro_project_example>/<directory_of_data>

To use this project on the cluster this needs to be edited to: