...
Login nodes: 4 nodes, icelake no-gpu
|
| |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
...
which establishes a connection to one of the available login nodes. To connect to Leonardo LEONARDO you can also indicate explicitly the login nodes:
$ login01-ext.leonardo.cineca.it
$ login02-ext.leonardo.cineca.it
$ login05-ext.leonardo.cineca.it
$ login07-ext.leonardo.cineca.it
The mandatory access to Leonardo LEONARDO is the two-factor authentication (2FA). Please refer to this link of the User Guide to activate and connect via 2FA. For information about data transfer from other computers please follow the instructions and caveats on the dedicated section section Data storage or the document Data Management.
Accounting
The accounting (consumed budget) is active from the start of the production phase. For accounting information please consult our dedicated section.
The account_name (or project) is important for batch executions. You need to indicate an account_no to be accounted for in the scheduler, using the flag "-A"
...
On LEONARDO, as on the other HPC clusters in CinecaCINECA, a a linearization policy for the usage of project budgets has been defined and implemented. The The goal is to improve the response time, giving users the opportunity of using the cpu hours assigned to their project in relation to their actual size (total amount of core-hours).
...
In addition to the home directory $HOME, for each user is defined a scratch area $SCRATCH (or $CINECA_SCRATCH), a large disk for the storage of run time data and files.
An new user specific area $PUBLIC is defined on LEONARDO, useful for example to share installations with other users (it is indeed the default directory for SPACK sub-directories, see more details in the dedicated page).
A A $WORK area is defined for each active project on the system, reserved for to all the collaborators of the project.
Total Dimension (TB) | Quota (GB) | Notes | |
|---|---|---|---|
| $HOME | 0.46 PiB | 50GB per user |
|
| $CINECA_SCRATCH | 41.4 PiB | no quota |
|
| $PUBLIC | 0.46 PiB | 50GB per user |
|
| $WORK | 10 PB |
|
...
The software modules are collected in different profiles and organized by functional categories (compilers, libraries, tools, applications, ...). The profiles are of two types: “programming” type (base and advanced) for compilation, debugging and profiling activities, and “domain” type (chem-phys, lifesc, ...) for the production activity. They can be loaded together.
"Base" profile is the default. It is automatically loaded after login and it contains basic modules for the programming activities (ibm, gnu, pgi, cuda compilers, math libraries, profiling and debugging tools, ...).
If you want to use a module placed under other profiles, for example an application module, you will have to previously load the corresponding profile:
...
Almost all the softwares on Leonardo LEONARDO were installed with Spack manager, which loads automatically the possible dependencies, so "autoload" command is unnecessary.
For listing all profiles you have loaded you can use the following command:
...
$ modmap -m <module_name> Note: on LEONARDO you can find modules compiled to support GPUs and modules suitable only for CPUs. You can check the compiler in the full name of the module, where the version is specified (e.g. gromacs/2022.3--intel-oneapi-mpi--2021.10.0--oneapi–2023.2.0). Remind that modules compiled with gcc, nvhpc, cuda should be used only on the Booster partition, while modules compiled with intel oneapi are suitable for running on the DGCP partition. Please refer to the specific sections of the two partitons for more details on the available compilers: Booster Programming environment and DCGP Programming environment.
Note also that since the DCGP partition is currently in the pre-production phase, changes in the Module environment may occur. Please read the UserGuide for updates.
Spack environment
In case you don't find a software you are interested in, you can install it by yourself.
In this case, on Leonardo we LEONARDO we offer the possibility to use the “spack” environment by loading the corresponding module. Please refer to the dedicated section in UG2.6: Production Environment
Please note that we are still optimizing Leonardo LEONARDO software stack, and more installations may be added/replaced. Always check with "module av" (the hash in the module name can change).
...