Using the cluster is free of charge.

Neither for your user account nor for your project usage, you or your academic institution will be charged in any way.

However, operating and maintaining the HPC is quite an expensive business nonetheless (power consumption, cooling, administration). The compute resources should thus be used responsibly, by designing your compute jobs as efficient as possible.

There are regular office hours, but no support chat.

Video office hours every Wednesday 10 am 11 am:
Zoomlink
Meeting-ID: 665 7163 2291
Kenncode: 113329

Office hours every first Wednesday (monthly):
Alexanderstrasse 2, Room 205, 213 und 214

While logged in on one of the login nodes , you can use the command account_expire to see your user account's end-of-validity date.

You will get an automatic email reminder 4 weeks before expiry of your account, and another one on the day of expiry.

These go to your professional TU-ID mail address configured in the TUDa's IDM system.

To extend your account, simply fill and sign the "Nutzungsantrag " again, and send it to us fully signed via office post (or via your local contact person ).

That can be caused by two basic reasons: the login node is not answering at all (perhaps due to being down or having network problems), or it answers but denies you access.

• Try another login node (the one you tried may be down)
• Have a look at our news page for possible maintenance downtimes or unexpected outages.
• Check your professional email inbox (and spam folder) for mails with the subject “Your account on the Lichtenberg High Performance Computer”, warning of or indicating your recent account's expiry.
• In case of “Permission denied” or “Incorrect password” (the login node answers, but denies you access), even from different login nodes:
  • make sure to log in with your TU-ID. Most ssh programs guess your remote login name from what you are on the local system, and that works only if it happens to be your TU-ID. To make matters worse: the windows ssh client likes to transmit “ADS-DOMAIN\yourWindowsName” and that can't work, even if “yourWindowsName” would be your TU-ID.
    Either use
    ssh <TU-ID>@lclusterXX.hrz.tu-darmstadt.de or
    ssh -l <TU-ID> lclusterXX.hrz.tu-darmstadt.de
  • check the language settings of your keyboard for inadvertent changes. English keyboard layout has Y and Z inverted, and does not sport german umlaut's.
  • try changing your TUID password, as this is sync'ed to the HLR a few seconds later.
• Read the (ssh) error message in its entirety. Sometimes it even explains how to fix the actual problem.
• Error: “message authentication code incorrect” – Windows has a weird problem with the Hash-based Message Authentication Code.
  Add the ssh option “-m hmac-sha2-512”.
• Try to log in explicitly with IPv4 or IPv6:
  ssh -XC –4 <TU-ID@>lcluster15.hrz.tu-darmstadt.de
ssh -XC –6 <TU-ID@>lcluster17.hrz.tu-darmstadt.de
• Already running the most recent version of your ssh/scp access program (PuTTY / KiTTY / BitVise / WinSCP / FileZilla)?
  From time to time, we refine the allowed (ie. considered safe) list of ssh key ciphers and negotiation algorithms, and some older program (versions) might be unable to cope with them.
• Have you recently made any changes in your login startup scripts .bashrc or .bash_profile? When failing, commands in these startup scripts can cause the bash to end prematurely, and that might look like you are denied access.
  If only interactive logins are affected, you can try accessing the likely culprit with your scp program (BitVise / WinSCP / FileZilla), and either
  • download it, comment the recent changes and re-upload it
    or
  • delete the troublemaker (and then restoring your last version from .snapshots/)

If nothing of the above works out: open a ticket, always mentioning your TUID (no enrollment/matricle no) and preferably from your professional TUDa email address.

Avoid sending “screenshots” of your terminal window as pictures (jpg/png or the like). A simple copy&paste in text form of your login attempts and the resulting error message is sufficient.

If there isn't any explanatory error message, please use the “verbose” mode by running “ssh -vv …” and append the output to the ticket mail (again please not as screenshot/picture, but as text).

If you can login interactively, but any upload of files to the HPC does not work, check for the following:

• Quota exceeded
  Use “cquota” to assess whether you exceeded the allotted quota where you want to upload to. If so, delete (large) files to make room for the new.
  
• Output to terminal during login
  Some file transfer programs do not like being interrupted by textual output on STDOUT or STDERR , while negotiating their transfer protocol.
  Check your shell's startup files (~/.bashrc, ~/.bash_profile, ~/.bash_login and ~/.profile) for any “echo” or “date” or similar commands generating output, and move these behind the following check line:
  [ -z "$PS1" ] && return
  This makes sure output is only generated during interactive sessions, and not during scp/sftp/sshfs access.
  
• automatic “forward” into your desired shell
  If you prefer to work with another shell than our default bash (like ksh or zsh), move its initialization command also behind such check:
  [ -z "$PS1" ] && return
exec /bin/zsh

If all that does not help, you can open a ticket with us (see “Contact” right of this column).

Avoid sending “screenshots” of your terminal window as pictures (jpg/png or the like). A simple copy&paste in text form of your login attempts and the resulting error message is sufficient.

Since June 2020, we have established a new password synchronisation: as soon as you change your TU-ID password in the IDM system of the TU Darmstadt, the login password to the Lichtenberg HPC will be in sync with it.

This is in effect from the get-go, ie. your first login to the Lichtenberg HPC will work with your central TU-ID password.

The same holds true for guest TU-IDs.

Using the "member " command (since Nov 2022) without parameters, you see a list of all your memberships in HPC projects.

Additionally, your currently active projects / memberships are recorded nightly in a file called .project in your HOME directory:

 cat $HOME/.project

• Director of the institute (DI): Most departments are organized into institutes (Fachgebiete). If this does not apply to your organization, please insert the dean, or a person with staff responsibility for the main research group.
• Principal Investigator (PI): is responsible for the main scientific aspects of the project. This can be the DI, as well as a junior professor or postdoc.
• Project Manager / Person of Contact (PoC): In general, this is the main researcher working the major part of this project. The PoC is responsible for the administrative aspects of the scientific project. He or she is also the “technical contact” the HRZ communicates with.
• Member or Additional researchers (AR):All other researchers who can do computations on this project's account. These might be other colleagues, PhD students, team members, as well as students and student workers.

The general project classes by amount of resources (Small, NHR-Normal and NHR-Large) are listed in our project class overview .

Beside plain computational projects, you might also be member of some rather technical billing accounts (eg. courses/trainings).

In general, we have the following naming pattern:

• project<5#>
  This is a Small (or preparation) project
• p<7#>
  This is a NHR project (Normal or Large)
• special<5#>
  Technical projects for select groups
• kurs<5#>
  Trainings, workshops and lectures with practical exercises on the Lichtenberg cluster (see Lectures and Workshops ).

In general, a project is always owned by a person of contact (fka project manager) – usually the main researcher and thus, a PhD or a post-doc. This PoC is entitled to add (and remove) others from the project (like bachelor and master students or colleagues), using the “member” command .

All these coworkers need to have their own user account on the HLR before being added to a project.

There is no upper limit as to how many persons can be member of a given project.

Beware: while sharing your project account is explicitly allowed, sharing your user account is strictly prohibited!

In general, the Lichtenberg “local” or Small projects should be in the range and size of a PhD project, or intended to prepare NHR-Normal or -Large projects. For longer research terms and scientific endeavours, recurring follow-up projects are required.

Nonetheless, the initial proposal should outline the whole scientific goal, not only your 1^st year's objectives.

If the limit of a Small project is insufficient for your scientific challenge, apply here for a NHR-Normal or NHR-Large project.

The project owner (PM or PoC – Person of Contact) is responsible for applying and (after completion) for reporting on the project.
The PoC will be working with the HRZ/HPC team for the (technical) reviews, and hand in the original of the signed proposal to the HRZ.

Students can apply for a bachelor or master thesis' project.

The proposal has to be signed by the PoC and by the PI/DI, who is required to be professor or post-doc.

For a “Small” (or preparation) project, only the web form needs to be completed, printed out, signed and sent to the HRZ.
This form mainly asks for technical details and a short abstract (150-300 words) of the scientific goals.

For the larger NHR projects, refer to the JARDS portal for details.

“Small”/preparation projects can be submitted at any time and the proposals will be handled upon entry.

For the larger NHR projects, deadlines (if any) can be found on the JARDS portal.

All projects are subjected to a technical review by the HRZ/HPC team.

If a project proposal is not sufficiently clear (ie. in terms of job sizes and runtimes), we will contact the PoC and ask for clarification or modification.

After the TR has been completed successfully, “Small” projects are started immediately.

NHR-Normal and NHR-Large projects are then reviewed scientifically by (external) HPC experts from the field of the project.

Based on these reviews, the steering committee (Resource Allocation Board) approves (or denies) the proposal and assigns the resources, either as requested or in reduced form.

The minimum is 3 months, and the maximum grant period for any given project is one year, regardless of the project's class .

If you know that your project needs less than a year, we suggest to write your proposal accordingly.
As the computational resources are allotted evenly over the granted time period, shorter projects get a greater resource share per month, resulting in higher priority per job.

In well-reasoned cases, a project can be extended beyond one year, for one or two months.

If your research project will take much longer than a year to complete, you will need to apply for follow-up projects every year.

Information about your publications and how to reference the computing time grant can be found under High Performance Computing – Publications .

For all publications prepared using TU Biblio, the category „Hochleistungsrechner“ within the „Divisions” list (as a subcategory of „Hochschulrechenzentrum“) has been added to TU Biblio.

Please use this category for your research publications related to the Lichtenberg Cluster, as then your publication will automatically be listed here accordingly.