call are available at
https://github.com/easybuilders/easybuild/wiki/Conference-call-notes-20181212
.
Next conf call is planned for Jan 9th 2019, join via
https://umu.zoom.us/j/561463243 .
regards,
Kenneth
On 12/12/2018 11:41, Kenneth Hoste wrote:
Dear EasyBuilders,
The next EasyBuild
Dear EasyBuilders,
Notes for today's conf call are available at
https://github.com/easybuilders/easybuild/wiki/Conference-call-notes-20181212
.
Next conf call is planned for Jan 9th 2019, join via
https://umu.zoom.us/j/561463243 .
regards,
Kenneth
On 12/12/2018 11:41, Kenneth Hoste
Hi Thomas,
In addition to what Jack said, I (we) recommend users to always load
specific versions of modules for the sake of reproducibility, e.g.
module load Python/2.7.12-foss-2016b
Cheers,
Sam
On Wed, Dec 12, 2018 at 4:21 PM Jack Perdue wrote:
> Howdy Thomas,
>
> FWIW, we have a flat
Howdy Thomas,
FWIW, we have a flat module hierarchy and I/we would
never ever suggest someone trying to use 2016b
modules with 2018b toolchains/modules.
Jack Perdue
Lead Systems Administrator
High Performance Research Computing
TAMU Division of Research
j-per...@tamu.eduhttp://hprc.tamu.edu
Hi Thomas,
I do not think there is such a feature available in any module management
system, but people that have more experience with flat module naming schemes
may give you better insights than me.
We went with a hierarchical module naming scheme for the exact reason of
avoiding that type
Hi
We have installed a lot of modules with the foss-2016b toolchain on our HPC
cluster.
And there are a several modules installed with the foss-2018b toolchain.
But some endusers have problems to load some modules if a module is installed
with the foss-2016b and foss-2018b toolchain.
use-case:
Dear EasyBuilders,
The next EasyBuild conf call is planned for *today* Wed Dec 12th 2018,
at 5pm CET.
This will be the last conf call of this year.
You can join the conf call via https://umu.zoom.us/j/561463243 .
Current agenda:
* updates on upcoming EasyBuild v3.8.0
* an easyblock for
7 matches
Mail list logo