You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug was introduced in #99 which runs the executable from the current working directory instead of the task directory by using the absolute path to the executable.
The text was updated successfully, but these errors were encountered:
Currently, the CABLE executable is run from the current working
directory instead of the task directory by using the absolute path to
the executable. However, we should be running the executable from the
task directory (otherwise CABLE will complain it cannot find the soil
and PFT namelist files). This was a bug that was introduced in the #99.
This change makes it so we change into the task directory before running
the CABLE executable.
Fixes#123
Currently, the CABLE executable is run from the current working
directory instead of the task directory by using the absolute path to
the executable. However, we should be running the executable from the
task directory (otherwise CABLE will complain it cannot find the soil
and PFT namelist files). This was a bug that was introduced in the #99.
This change makes it so we change into the task directory before running
the CABLE executable.
Fixes#123
We should run the CABLE executable from the task directory. Otherwise CABLE will complain it cannot find the soil and PFT namelist files:
This bug was introduced in #99 which runs the executable from the current working directory instead of the task directory by using the absolute path to the executable.
The text was updated successfully, but these errors were encountered: