Ok, I take the bait, we use environment modules on all our systems and 
EasyBuild on most of our clusters, including JURECA (at number 
50<http://www.top500.org/system/178718>) ;)

On 16 December 2015 at 16:31, Kenneth Hoste 
<[email protected]<mailto:[email protected]>> wrote:
On 16/12/15 16:10, Kilian Cavalotti wrote:
Hi there,

On Mon, Dec 14, 2015 at 2:49 PM, Christopher Samuel
<[email protected]<mailto:[email protected]>> wrote:
Or maybe an indication in terms how many are using environment modules?
We use environment modules on all our HPC systems, including on our
Top500 machine Avoca, a 4 rack BlueGene/Q (originally #31, now #124).

To be honest, you'd be mad not to..
Let me jump on the bandwagon and true that.

Stanford Research Computing uses environment modules on most of its
HPC systems, and Lmod on the largest and most recent ones.
We also use EasyBuild in production on our latest GPU cluster (a Cray
CS-Storm, http://top500.org/system/178566).

Oh, I had no idea the Stanford system was that big!
Currently ranked #104, who does better? ;-)

Just to clarify: you're using the 'stock' toolchains on that system, rather 
than the (experimental) Cray support?


regards,


Kenneth



--
Dr. Alan O'Cais
Application Support
Juelich Supercomputing Centre
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49 2461 61 5213
Fax: +49 2461 61 6656
E-mail: [email protected]<mailto:[email protected]>
WWW:    http://www.fz-juelich.de/ias/jsc/EN


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to