# EESSI

[EESSI](https://www.eessi.io/) (European Environment for Scientific Software Installations) provides pre-built scientific software optimized for different CPU and GPU architectures. On Komondor, the software is available through CernVM File System (CVMFS) and the module system.

## Available versions and production status

As of **2026-11-17**, the following versions are available on Komondor:

#### EESSI environments on Komondor

|   Version | Upstream status              | Included foss toolchains   | Load command                |
|-----------|------------------------------|----------------------------|-----------------------------|
|   2023.06 | Production; Komondor default | `2022b`, `2023a`, `2023b`  | `module load eessi/2023.06` |
|   2025.06 | Production                   | `2024a`, `2025a`, `2025b`  | `module load eessi/2025.06` |
|   2026.06 | Production                   | `2026.1`                   | `module load eessi/2026.06` |

All three belong to the [EESSI production repository](https://www.eessi.io/docs/repositories/software.eessi.io/). The [official version overview](https://www.eessi.io/docs/repositories/versions/) confirms that `2025.06` and `2026.06` are fully available and continue to receive software additions. They can be used for production workloads; they are not preview releases. The newer versions provide different application collections and compiler toolchains rather than replacing the older environment in place.

Choose a version that provides the application and toolchain you need, and specify both the EESSI version and the application module version in batch scripts for reproducibility. The Komondor default remains `2023.06`.

Environment loading has been checked on vn01 for all three versions. This does not validate every application, MPI configuration, or GPU workload on compute nodes. Check your application’s results and performance on the intended nodes before moving an existing production workflow to a different EESSI version.

## Loading the environment

Load the default EESSI environment with:

```bash
module load eessi
```

The default version is **2023.06**. The names `eessi` and `EESSI` both work, including when specifying a version:

```bash
module load eessi/2023.06
module load eessi/2025.06
module load eessi/2026.06
```

These are alternatives: load the version required by your application. For example, `module load EESSI/2025.06` loads the same environment as `module load eessi/2025.06`.

#### IMPORTANT
Loading an EESSI environment automatically purges previously loaded modules, including the default Cray programming environment and any application modules. Load EESSI **before** loading your application. Switching EESSI versions also removes previously loaded application modules; load the application again after switching.

No separate `module purge`, `module unuse`, `module use`, or sourcing of an initialization script is needed. Use the same module commands inside a Slurm batch script, after the `#SBATCH` directives. Load the environment on the allocated compute node so EESSI can select software for that node’s architecture.

## Loading an application

For example, to use LAMMPS from EESSI 2023.06:

```bash
module load eessi/2023.06
module avail LAMMPS
module load LAMMPS/29Aug2024-foss-2023b-kokkos
```

The application is then available in the current shell or batch job. Available application versions depend on the selected EESSI release and the node’s CPU/GPU architecture. Check availability after loading the intended environment.

Use `module list` to inspect the loaded modules. To remove the environment and all loaded application modules, run:

```bash
module purge
```

This does not restore the modules that were loaded before EESSI. Load any required Cray or other local modules explicitly afterwards.

For the EESSI software catalogue, see the [available software overview](https://www.eessi.io/docs/available_software/overview/).

Last update by Attila DEBRECZENI: 2026-11-17
