| Package: | |
|---|---|
| Description: | |
| License: | Unknown |
This section lists the available versions of the package on the different clusters.
Sorry, this is still under construction.
NOTE: The theano installs on the Deepthought2 RHEL6 nodes are all Singularity based. For more information, see the section on Using Singularity based Theano installations.
The keras, tensorflow, and theano packages are not natively installed on the Deepthought2 RHEL6 nodes for various technical reasons. What is provided instead are Singularity containers which have versions of both python2 and python3 installed with these packages.
To use these python packages, you must load the appropriate environmental
module (e.g. module load theano) and then launch the python
interpretter inside the Singularity container. To help with this,
the following helper/wrapper scripts have been provided:
ol>
theano or theano-python2 will invoke a
Theano-enabled python2 interpretter within the container. Any arguments
given will be passed to the python command, so you can do something like
theano myscript.pl
theano-python3 will behave as above, but invoke a
Theano-enabled python3 interpretter within the container.
theano-cache, theano-cache-python2 will
run the theano-cache command (using python2) inside the container.
Any arguments given will be passed to the theano-cache command.
theano-nose, theano-nose-python2 will
run the theano-nose command (using python2) inside the container.
Any arguments given will be passed to the theano-nose command.
theano-cache-python3, theano-nose-python3 behave
like theano-cache and theano-nose, respectively, but
invoke python3 variants of the named script.Note that if you load the keras environmental module and then issue the
python command, you will start up a natively installed python
interpretter which does NOT have the theano, etc. python modules
installed. You need to start one of the python interpretters inside the
container to get these modules --- you can either do that using the correct
singularity command, or use the friendlier wrapper scripts
described above.
It is hoped that for most users, the "containerization" of these packages should not cause any real issues, and hopefully not even really be noticed. However, there are some limitations to the use of containers: ol>
foo is installed natively on Deepthought2, it is likely not
accessible from within the container (unless it was also installed inside that
container). virtualenv scripts
to install new python modules for use within the container, as that will be
installing packages natively, which would not then be available inside the
container.
However, you are permitted to create your own Singularity containers and use them on the Deepthought2 cluster. You will need to have root access on some system (e.g. a workstation or desktop) to create your own Singularity containers (we cannot provide you root access on the Deepthought2 login or compute nodes), but if you have such you can build your own containers. You can also copy the system provided containers and edit them. More details can be found under the software page for Singularity.