Versions Compared

Key

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

...

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.

GUI

The GUI version of EddyPro is not available on the cluster because it is a fork of the main project and is of an older version.Running Jobs:

Note

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 download Engine is available to download for Windows and Mac OS from here.

Create projects on Alcova or create projects locally and upload to the cluster.

If using on the Windows version or if uploading a project created locally then . 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 edited in a text editor to update the pathing.

...

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:

Code Block
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:

Code Block
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 after creating a project that was created using the Windows GUI version of EddyPro and saved on Alcova:

Code Block
file_name=//alcova.arcc.uwyo.edu/project/<your_project>/<eddypro_project_example>/<project<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 Linux the cluster this needs to be edited to:

Code Block
file_name=/alcova/<your_project>/<eddypro_project_example>/<project<eddypro_project_name>.eddypro
out_path=/alcova/<your_project>/<eddypro_project_example>/output
data_path=/alcova/<your_project>/<eddypro_project_example>/<directory_of_data>

...