Difference between revisions of "Pre Installed Packages"
(→Preamble) |
|||
| Line 8: | Line 8: | ||
However, if you do not specify the packages the system tries to integrate and run the code using the packages already present on the DataMiner, this is done to facilitate the integration of the developers. | However, if you do not specify the packages the system tries to integrate and run the code using the packages already present on the DataMiner, this is done to facilitate the integration of the developers. | ||
Obviously, in this case if the process uses non-installed packages it will fail during the execution and it will be the developer's responsibility to request the installation of the missing packages. | Obviously, in this case if the process uses non-installed packages it will fail during the execution and it will be the developer's responsibility to request the installation of the missing packages. | ||
| − | The | + | The Interpreter version also serves to better identify the type of code being executed and to support the entire debugging phase in the event of problems. |
So in general, algorithm support will be better if the information generated is greater, but in any case the system tries to integrate and execute the code. | So in general, algorithm support will be better if the information generated is greater, but in any case the system tries to integrate and execute the code. | ||
Revision as of 10:58, 11 June 2019
Contents
Preamble
This Wiki reports the packages pre-installed on the computational machines for a variety of languages. On this machines also run DataMiner service with algorithms created through Statistical Algorithms Importer (SAI). In general it is better to specify the packages with the relative versions as they shown below. However, if you do not specify the packages the system tries to integrate and run the code using the packages already present on the DataMiner, this is done to facilitate the integration of the developers. Obviously, in this case if the process uses non-installed packages it will fail during the execution and it will be the developer's responsibility to request the installation of the missing packages. The Interpreter version also serves to better identify the type of code being executed and to support the entire debugging phase in the event of problems. So in general, algorithm support will be better if the information generated is greater, but in any case the system tries to integrate and execute the code.
R Packages
A constantly updated list of installed R 3.4.4 Packages is available at the following LINK.
Github packages are show here:LINK. Versioning is not handled, but github packages are updated daily to the latest version.
Linux Debian Packages
A constantly updated list of installed Debian 3.2.51-1 x86_64 Packages is available at the following LINK
Octave Packages
Octave 4.2.1 is installed on the computational machines with basic packages.
Knime Packages
Knime-Full 3.6.1 is installed on the computational machines.
Java Packages
Java 8 is installed on the computational machines, with the dependencies of the Ecological Engine framework, retrievable through Maven HERE (refer to the latest version).
Python Packages
Python 2.7 and 3.6 are installed on the computational machines with basic packages.
Windows Packages
Windows .Net compiled programs are supported through the Mono 3.2.8 simulator.
