Dear list,
I'm sorry to bother you again, but it's still not very clear for me if I
should turn on or off this option.
I'm now using EB 4.1.0. When I went from 3.9.x to 4.0.x I didn't changed
this option, thus I had it set to true by default. It seems it was
working fine.
I'm using HierarchicalMNS. I must say it's fine for me if the install
directory doesn't match the hierarchy of the modules. So if I understand
well, I can just let this option
to "True" and don't care that the modules are mixed as it works.
Now my software are installed in /opt/ebsofts/ and my modules to
/opt/ebmodules
I compiled SciPy-bundle/2019.10-Python-3.7.4 for fosscuda/2019b with
fixed-installdir-naming-scheme=0
my module is here:
/opt/ebmodules/all/MPI/GCC-CUDA/8.3.0-10.1.243/OpenMPI/3.1.4/SciPy-bundle/2019.10-Python-3.7.4.lua
and the software is here:
/opt/ebsofts/MPI/GCC-CUDA/8.3.0-10.1.243/OpenMPI/3.1.4/SciPy-bundle/2019.10-Python-3.7.4
But i'm unable to load it:
module --debug=1 --ignore-cache load SciPy-bundle/2019.10-Python-3.7.4
[...]
Lmod has detected the following error: The following module(s) are
unknown: "SciPy-bundle/2019.10-Python-3.7.4"
Is this related or is this an issue with my $MODULEPATH? Right now, it
contains /opt/ebmodules/all/Core.
I'm not sure I understand why some modules are in Core and other in MPI?
Thanks for the clarification.
Best
