The FuseTS services are reliant on a specific set of dependencies (such as vam.whittaker, GPy, etc.) and its own code. Consequently, it is essential for these dependencies to be installed within the execution environment. While accomplishing this for local execution is relatively straightforward, it presents greater challenges within the context of openEO.
In the current version of the library, the dependencies are provided through openEO's job_options, as shown below:
Even though this works as is, it does require an update of the archives each time a change is done in the FuseTS library. A possible improvement would be to either:
Find an alternative solution to providing the dependencies in openEO that can be supported on any openEO backend
Include the creation and upload of the archives part of the build process
The FuseTS services are reliant on a specific set of dependencies (such as vam.whittaker, GPy, etc.) and its own code. Consequently, it is essential for these dependencies to be installed within the execution environment. While accomplishing this for local execution is relatively straightforward, it presents greater challenges within the context of openEO.
In the current version of the library, the dependencies are provided through openEO's
job_options
, as shown below:Even though this works as is, it does require an update of the archives each time a change is done in the FuseTS library. A possible improvement would be to either: