September 24th, 2026 at the University of Konstanz (Universitätsstraße 10, 78457 Konstanz, Room M629).
Registration and the call for abstracts are now open.
If you would like to actively participate in the 12th bwHPC Symposium, you have 2 options:
Abstracts (about 500 words) can be submitted via the event website (KIT Indico account required) or by e-mail to symposium2026@bwhpc.de. Selected abstracts will be invited to write short papers for inclusion in the conference proceedings, published online via Konstanz KOPS.
The bwHPC Symposium offers a unique opportunity for scientific users, operators of bwHPC services, and bwHPC support centres to actively engage in dialogue. The focus is on the presentation of scientific projects and success stories carried out with the support of bwHPC high-performance computing resources in the context of the BaWü data federation.
The symposium is free of charge and open to researchers from all scientific fields. Lunch and coffee will be provided on-site free of charge. An optional evening social event will take place on September 23rd at your own cost.
Key dates:
| Abstract submission deadline | August 3, 2026 |
| Notification of acceptance | August 18, 2026 |
| Registration deadline | September 14, 2026 |
For registration, abstract submission, and further details, please visit the event website. For questions, contact symposium2026@bwhpc.de.
We are looking forward to your participation.
Sincerely, Your bwHPC symposium team
]]>We encourage users to migrate to open-source alternatives, for example:
Not all of these are available on NEMO2 yet, but we can provide them on request. Please contact the helpdesk (see below).
If you have access to MATLAB through your own or your institution’s license, the following options may be available:
If you would like to use MATLAB on NEMO2 with your own license or need help migrating to an alternative, please submit a ticket to the central helpdesk: https://bw-support.scc.kit.edu
]]>We have fixed an SSH configuration issue on the login nodes that unintentionally allowed the use of local SSH keys stored in $HOME/.ssh/authorized_keys files.
Due to a misconfiguration of the SSH service on the login nodes, SSH keys stored in your local $HOME/.ssh/authorized_keys file were incorrectly accepted in addition to SSH keys configured through our central authentication system at login.bwidm.de. This behavior was never intended and has now been corrected.
As intended, you can access the cluster using:
If you need to set up SSH keys for authentication, please follow the official guide:
This guide will walk you through the process of properly configuring your SSH keys in the central authentication system.
If you have questions about SSH authentication or experience any login issues, please submit a ticket.
]]>To accommodate the holiday period, we are making temporary changes to NEMO2’s configuration, balancing increased flexibility for users with energy conservation efforts.
During the holidays, queue limits are significantly increased to give you more flexibility. You can now submit up to 10,000 jobs and request larger jobs with more CPU cores. This allows you to make better use of the available resources during the typically quieter holiday period.
The increased limits will be automatically lifted on January 7, 2026, when standard queue limits will be restored.
To conserve energy during the holidays, we will shut down a portion of the compute nodes. Sufficient capacity remains online to process jobs throughout the holiday period, but please expect potentially longer queue times due to the reduced number of available nodes.
If you have questions about the holiday configuration or experience any issues, please submit a ticket.
The NEMO Team wishes you happy holidays and a happy New Year 2026!
]]>We have successfully performed a rolling upgrade of bwForCluster NEMO 2 to enhance system security, stability, and performance. This upgrade was designed to minimize disruption to your work while implementing critical updates.
The following updates were applied across the cluster:
Our goal is to achieve 100% uptime for NEMO2. The rolling upgrade approach allowed us to:
During the rolling upgrade:
If you have questions, feedback, or experienced any issues during the upgrade, please contact our support team via the ticket system.
]]>We’re excited to announce that FIDO2 SSH keys are now supported on bwForCluster NEMO 2! This new authentication method offers a significantly improved login experience with enhanced security.
FIDO2 SSH keys (using hardware tokens like Yubikeys) provide hardware-based authentication for SSH connections. Unlike traditional SSH keys, they offer several key advantages:
The most significant improvement: FIDO2 SSH keys work immediately without requiring 2-factor authentication unlock. While regular SSH keys on our clusters need to be “unlocked” with your username, password, and OTP after each validity period (8-12 hours), FIDO2 keys are always ready to use - you simply touch your hardware key when prompted.
Setting up FIDO2 SSH keys is straightforward:
ssh-keygen -t ed25519-skWe’ve prepared comprehensive guides to help you get started:
FIDO2 SSH keys are currently supported on:
If you have questions about FIDO2 SSH keys or need assistance with setup, please contact our support team or visit our documentation pages linked above.
]]>We are pleased to announce that the snapshot feature for home directories has been activated. Snapshots are automatically created to help you recover files that were accidentally deleted.
The following snapshot schedules are now in place:
Your snapshots are available in the /home/.snapshots/ directory. To access your personal snapshots:
/home/.snapshots/@GMT-2025.11.17-14.05.01)Example: If your home directory is /home/fr/fr_ab1234, your snapshots are located at:
/home/.snapshots/@GMT-2025.11.17-14.05.01/fr/fr_ab1234
If you have any questions about accessing or restoring files from snapshots, please contact the NEMO support team.
]]>Each node is configured with:
One of these nodes has already been integrated into NEMO2 and is ready for testing.
To use it, please submit your jobs with the partition h200.
Please note: no software modules are installed yet on these nodes.
You may need to bring your own software environment (e.g. via containers or conda) for testing.
#!/bin/bash
#SBATCH --job-name=test-h200
#SBATCH --partition=h200
#SBATCH --gres=gpu:1
#SBATCH --cpus-per-task=8
#SBATCH --mem=64G
#SBATCH --time=02:00:00
# load CUDA if available, otherwise use your own environment
module load system/cuda/12.6.0 || true
srun nvidia-smi
module avail miniforge (alias: module avail conda).
The miniforge module automatically initializes the conda environment.
You do not need to run conda init to add conda to your .bashrc or .bash_profile, which can cause problems with other software or environments.
After loading the Miniforge module, you can directly activate a conda environment with the command conda activate <env>.]]>NEMO1 has reached the end of its life. However, there are still 25 Milan nodes and one Nvidia V100 node available until the end of May when we officially shut down NEMO1 (31.05.2025). After that, we will try to keep BeeGFS online for data transfers until we know when the new AI nodes will be delivered. But we will then shut down BeeGFS with only a few days notice. Please try to migrate your data by May 31st. After this date, we can no longer guarantee data availability.
If you still want or need to perform calculations on NEMO1 until May 31st, please write a ticket with your NEMO1 username. We will then activate your user for NEMO1.
For NEMO hardware and Slurm partitions visit our wiki.
]]>