@@ -39,12 +39,12 @@ You can use `module spider` to get the list of available modules regardless of w
The main software environment is based on the Intel solution for clusters (called "Cluster Edition" these days). It provides:
* The Intel compilers: icc (C), icpc (C++), ifort (Fortran) compilers, provided through the **intel-gnu8-runtime** module.
* The Intel MPI environment, provided through the **impi** module (depends on **intel-gnu8-runtime**)
*The Intel python environment, provided through the **intelpython3** module (depends on **intel-gnu8-runtime**)
* The Intel compilers: icx (C), icpx (C++), ifx (Fortran) compilers, provided through the **intel-oneapi-compilers** module.
* The Intel MPI environment, provided through the **intel-oneapi-mpi** module (depends on **intel-oneapi-compilers**)
*A virtual python environment can be created by using **anaconda3** module (depends on **intel-oneapi-compilers**)
* And other stuff.
That environment relies on a Gnu runtime distribution for most the its runtime. Since the default Gnu runtime on our CentOS distribution is quite antique, we decided to rely on gcc 8.3 instead.
That environment relies on a Gnu runtime distribution for most the its runtime. Since the default Gnu runtime on our CentOS distribution is quite antique, we decided to rely on gcc 12.2.0 instead.
This technicality is probably mostly relevant to C++ developers.
