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
Have the following messages when trying to install the api in Raijin. Any ideas?
$ module use /projects/el8/opt/modules/modulefiles
$ module load agdc-api/0.1.0-b20150513
mpi4py/1.3.1 is only available for python/2.7.3 and python/2.7.5
mpi4py/1.3.1(3):ERROR:151: Module 'mpi4py/1.3.1' depends on one of the module(s) 'python/2.7.5'
mpi4py/1.3.1(3):ERROR:102: Tcl command execution failed: source /opt/Modules/extensions/extensions.tcl
agdc-api/0.1.0-b20150513(10):ERROR:105: Unable to locate a modulefile for 'psutil'
agdc-api/0.1.0-b20150513(10):ERROR:105: Unable to locate a modulefile for 'numpy'
agdc-api/0.1.0-b20150513(10):ERROR:105: Unable to locate a modulefile for 'scipy'
$
The text was updated successfully, but these errors were encountered:
The first warnings are related to dependencies. So you basically need to have those modules loaded first. The module load system has become somewhat unwieldly with many conflicts as the modules would try and load the "default" everything for you. This can cause conflicts if a user already has a different module loaded. So for the time being we've used a dependency check, to warn, and specify the exact versions that are required.
The second set of errors indicate that the module system can't find a specific module, eg.numpy.
I've just had a look at the modules under el8, and there's not much there. I'm unsure as to who was maintaining it. I use project u46 for loading my modules, which I can make a guess that you're not a member of.
You could try replacing el8 with u46 in your module use line, but I'm probably a little ambitious on it working for you.
In the meantime I can try and copy the modules across, and change the project access to el8.
Hi there,
Have the following messages when trying to install the api in Raijin. Any ideas?
The text was updated successfully, but these errors were encountered: