Changes to default partition for Claix jobs that do not define it.
Dear HPC Users,
With the introduction of Claix 2025, we have changed the way default partitions are defined for jobs that provide none.
Prior to this change, the default partition was statically defined for all Slurm project accounts. A job submitted without a partition would fall back to this hard-coded default partition.
This has now changed. We now take a best-effort approach to define the default partition for each job dynamically, based on the login / submit node from which the job was submitted, the account used and the resources requested.
Jobs submitted from Claix23 machines will set a default c23ms partition for CPU only jobs and c23g partition for GPU jobs.
The same will now happen with jobs submitted from Claix25 machines (c25ms and c25g).
IH projects and login nodes will also be taken into account.
We still ask for users to try and explicitly define partitions for their jobs to avoid any undesired behaviors.
The best practice is therefore still to define partitions in the jobs explicitly.
This change should not affect the majority of jobs or how they are billed.
Overleaf: Automated Check of the Terms of Use
Overleaf has been technically adjusted. Compliance with the applicable terms of use is now filtered and checked automatically. As a result, an automated process replaces the previous manual filtering. This consequently supports a reliable, efficient, and consistent implementation of the intended framework conditions.
The automated verification process prevents individuals who do not have “Employee” status from accessing the system as soon as they log in.
Design Improvements and Bug Fixes (v1.21.0)
Bugfixes and Improvements:
- Improved the overall modal design, especially for mobile devices
- Enhanced the design of the error modal
- Free models can now continue to be used even after the hard limit has been reached
- Fixed an issue where chat titles would sometimes only appear after reloading the page
Support for gpt-image-2 and Admin Improvements (v1.21.0)
Features:
- Added support for the new model:
gpt-image-2
Bugfixes and Improvements:
- Improved the overall modal design, especially for mobile devices
- Enhanced the design of the error modal
- Image generation settings are now persisted and remain available after a page reload
- The deployment list in the admin area now directly indicates whether a deployment is enabled for the frontend and/or API
- Free models can now continue to be used even after the hard limit has been reached
- Fixed an issue where chat titles would sometimes only appear after reloading the page
Update for Efficient Elements
Microsoft has released an update for PowerPoint version 2606 (build 20131.20090). Unfortunately, this update can lead to an error in the “Element Wizard” of Efficient Elements. Therefore, we have already reacted. We have provided an updated version of Efficient Elements. The corresponding update is now available on our download server.
What to Do?
Please install the latest version of Efficient Elements from the download server. Please close all Microsoft Office applications before the installation. This applies in particular to PowerPoint, Excel, and Word. Afterwards, the Element Wizard should function as usual again.
If the problem persists, please contact the IT-ServiceDesk.
Please provide the following information in your message:
- Efficient Elements version used
- Microsoft 365 version or build number
- Windows version
- short description of the error or a screenshot of the error message
Important Changes for HPC Accounts – Usage of the NHR community AAI
We are unifying the account experience for our HPC services. As part of this, your local account must be connected to the National High Performance Computing (NHR) Community Authentication and Authorization Infrastructure (CAAI).
This linking is mandatory to keep access to your HPC account. Please link your account by June 31, 2026.
TL;DR
The following section summarizes the actions required to keep your HPC account active. Detailed explanations and instructions are provided throughout this email.
– External users with an existing RWTH account: Please link your home organization identity with your RWTH account as described on IT Center Help [1], if you have not already done so.
– All users (internal and external): Please log in once to the RWTH RegApp [2] via your home organization (SSO) to keep access to your HPC account.
– Applicants for computing time (JARDS): Use the new home organization login as described in the JARDS manual [3].
What has changed and why?
Previously, you logged in to the RWTH RegApp directly with your RWTH account to manage your HPC account.
Last year, we introduced the NHR CAAI as an identity proxy in front of the RegApp:
1. You now first log in via NHR CAAI using your home organization credentials.
2. You are then forwarded to the RWTH RegApp.
This allows external users to use our HPC systems seamlessly with their home organization identity.
If you have not used the RWTH RegApp since this change, your RegApp account is probably not yet mapped to your NHR CAAI account. We need this mapping to maintain a unified and consistent user account lifecycle.
What is required for external users with an RWTH account?
If you are not a member of RWTH Aachen University, but you do have an RWTH account:
1. Link your home organization account to your RWTH account as described on IT Center Help [1], if you have not done this yet.
2. Afterwards, follow the steps for all users below.
This ensures that your home organization login and your RWTH account are correctly associated.
What must all users (internal and external) do?
All users (RWTH-internal and external) have to:
1. Go to the RWTH RegApp [2].
2. When redirected to NHR CAAI, select your home organization (e.g., RWTH, your external institution, your ORCID or your Google account).
3. Log in with your home organization’s Single Sign-On (SSO) credentials.
During this process, an NHR CAAI account is created (if necessary) and mapped to your existing RWTH RegApp account.
Verify that it worked
We strongly recommend that you verify the result:
1. Open the RWTH RegApp [2].
2. Go to: “Registered services” → “RWTH High Performance Computing”.
3. Check that the displayed HPC username matches your actual HPC username.
If the RWTH High Performance Computing service is missing, or if the username is incorrect, please contact the IT-ServiceDesk (servicedesk@itc.rwth-aachen.de).
Will this affect my current HPC usage?
For now, your ability to connect to and authenticate on the HPC systems is not affected by the state of your RegApp account, until we start deactivating unlinked accounts in six months.
This means:
– If anything goes wrong during the procedure, you can continue to use the HPC service for the time being.
– We will notify users who have not completed the migration.
– We will also monitor and investigate cases where the migration appears to have failed.
If you have any reason to believe that you have lost access to your RWTH RegApp account due to this migration, please contact the IT-ServiceDesk (servicedesk@itc.rwth-aachen.de).
Did anything change for the computing time application as well?
Until now, you have been able to log in to JARDS via an email callback in order to apply for computing time. The JARDS login was also switched to a federated SSO login via CAAI on April 2, 2026.
We recommend that you use this new login method from now on and sign in to JARDS using the account of your home institution.
To keep your existing JARDS account when switching to the new home-organization login (SSO), your home organization’s Identity Provider (IdP) must transmit the same email as you previously used for the JARDS email callback. To ensure this, please follow these instructions:
1. Log in here: https://login.nhr-verein.de
2. Navigate to “Index → My E‑Mail Addresses”.
3. If the email is not the same as you used as JARDS email callback, add the email.
4. Confirm the email you receive.
5. Log in to JARDS via SSO.
Until October 1, 2026, you can continue to apply for compute time (“JARDS.application”) either via the existing email callback (not recommended) or via the new SSO login (recommended). For all reviewers (“JARDS.review”), the email callback will remain available even after October 1, 2026.
If you have any questions or problems, the team at the IT-ServiceDesk (servicedesk@itc.rwth-aachen.de) will be happy to help you.
Kind regards,
Your HPC Team
[1] https://help.itc.rwth-aachen.de/service/rhr4fjjutttf/article/9a42e86854ab43049d0f27b17e3ff601/
[2] https://regapp.itc.rwth-aachen.de
[3] https://jards.itc.rwth-aachen.de/jards/WEB/application/showloginhelp.php
Procurement Process for SoSci Is Underway
We are currently in the process of procuring the online survey tool SoSci. This process will take a little more time, so we ask for your patience in the meantime. However, the new license will be available in time. You will be able to find it directly in the software store before the current license expires. We will, of course, keep you updated on the latest developments.
Procurement process for Siemens NX is underway
The procurement process for the Siemens NX software is currently underway. This process will take a little while longer. We therefore ask for your patience at this time. As soon as the process is complete, we will list the items with updated validity periods in the software store.
Microsoft Licenses Now in the Software Shop
As of now, there is an important update for IT purchasers. You can order items via the Microsoft Select Plus volume licensing agreement. This takes place conveniently in the asknet software shop. Specifically, these items are known as B-products.
Currently, the offer includes licenses without Software Assurance. Furthermore, you can purchase Software Assurance separately as maintenance. Do you want to order licenses that include Software Assurance instead? This is expected to be possible starting in late August. Therefore, we ask for a little patience.
Despite these updates, the existing framework conditions remain completely unchanged.
New Model Available for Employees and Students: GPT-5.5
Features:
- For employees and students, the model GPT-5.5 has been added. Data processing for GPT-5.5 takes place exclusively within the European Union.
- For employees, the following usage limits apply:
- GPT-5.5 (Reasoning high): 100 requests per 3 hours
- GPT-5.5 (Reasoning minimal): 100 requests per hour
- For students, the following usage limits apply:
- GPT-5.5 (Reasoning high): 100 requests per day
- GPT-5.5 (Reasoning minimal): 100 requests per 6 hours
- For GPT-5.4-mini, the usage limits have been adjusted as follows:
- Employees: 1,000 requests per hour
- Students: 250 requests per 6 hours
- The following models have been removed:
- GPT-5.2
- GPT-5.3
