Starting from quarter 04/2022, the two NHR centers

• NHR@ZIB and
• NHR@Göttingen

follow the Content

Project account

NHR center NHR@ZIB follows NHR-wide regulations and account in the new unit core hours.

Both NHR centers provide computational resources primarily to universities in Germany under public law.

• A user accesses an account containing a number of units core hour.
• The NHR centers charge for batch jobs on the compute systems. The charge for a job is a number of units core hourA User Account accesses a project account containing units of core hour. A project account can be a Test Project or a Compute Project.
• A batch job on the compute system is charged by a number of core hour to measure the usage.
• Usage of persistent storage including the tape library is are currently not accounted.

Charge rates

The NHR centers operate different types of compute nodes (HLRN-IV system) organized in partitions, see Hardware. The charge rates for the partitions are given in the table.

...

standard96

standard96:test

...

large96

large96:test

large96:shared

...

192*

...

medium40

medium40:test

...

large40

large40:test

...

*increased charge rate due to high memory layout

** The nodes will be equipped with four NVidia A100 (40 GB) GPUs

Job charge

The charge for a batch job on the NHR systems is the number of core hours and is calculated from the number of nodes reserved for the jobNHR@ZIB operates system Lise with different Compute partitions. Properties for available (slurm-)partitions you find on the pages

• Slurm partition CPU CLX,
• Slurm partition GPU A100, and
• GPU PVC partition.

Each partition holds a specific charge rate.

1: Practically the charge is a very small number (close to zero).

Job charge

The charge of core hours for a batch job depends on the number of nodes, the wallclock time used by the job, and the charge rate for the job nodespartition used. For a batch job with

• num a number of nodes n,

• running with a wallclock time of t hours, and

• on a partition with a charge rate charge_p

the job charge charge_j yields

charge_j = numn * t * charge_p

...

Accounts for core hour

Running batch jobs with a user account, the user can access different accounts in general. The NHR centers distinguish between

• personal accounts and
• project accounts

User account

...

...

At the beginning of each quarter the bank account is granted by 75000 core hour  during the lifetime of the user account. In reasonable and exceptional cases, the grant of the bank account can be extended to 300 k core hour per quarter. For that please contact your consultant. At the end of each quarter all remaining core hour in the bank account are dropped.

Project account

A compute project holds a bank account for the project. This project account contains core hour. At the beginning of each quarter the account is granted by the number of core hour following the funding decision for the compute project. Unused core hour are transferred to the subsequent quarter, but only one time.

In case of problems with core hour in the project account please look at /wiki/spaces/PUB/pages/425995 or contact your consultant. This might affect the

• application for additional core hour,
• movement of core hour between quarters.

Batch job and account

Batch jobs are submitted by a user account to the compute system. For each job the user chooses the account that will be charged by the job.

• For the user account the default account for compute time is defined on the link Informationen zu Ihrer Kennung/Account information of the service portal. At the beginning of the user account lifetime the default account is the personal account.

• The user controls the account for a job using the Slurm option --account at submit time.

To charge the account myaccount
add the following line to the job script. 
#SBATCH --account=myaccount

After job script submission the batch system checks the account for account coverage and authorizes the job for scheduling. Otherwise the job rejected.