Scientists with a doctoral degree who belong to a German accredited university are eligible to apply for computing resources (project proposal) to use the HPC cluster HoreKa. Within the scope of the approved projects, non-doctoral scientists can also use HoreKa.
NHR@KIT offers three categories of projects depending on compute resources needed which implies different call and review types.
|Project category||Duration||Min. Resources||Max. Resources||Review||Call|
|NHR Test||6 months, not extendable||- / -||500,000 CPUh / 5,000 GPUh||Technical||Rolling|
|NHR Normal||1 year, extendable||2,000,000 CPUh / 30.000 GPUh||14,999,999 CPUh / 199,999 GPUh||2x Scientific||Rolling|
|NHR Large||1 year, extendable||15,000,000 CPUh / 200.000 GPUh||70,000,000 CPUh / 1,000,000 GPUh||2x Scientific + NHR user committee||Quarterly|
NHR Test projects¶
NHR test projects for activities like testing, porting, developing and benchmarking applications can be granted after a technical review by a review board of the NHR@KIT center, i.e., approval of test projects are not subject to scientific reviewing. Proposals for test projects have to be submitted via JARDS, and are limited to a maximum of 500,000 CPU hours and/or 5,000 GPU hours. Note that the maximum project time of 6 months can not be extented. It is expected that any follow-up activity of the given compute project is part of a NHR normal or NHR large project.
NHR Normal projects¶
NHR normal projects are scientifically reviewed compute time projects for the cluster HoreKa with the duration of 1 year starting at the date of approval. Any proposal of compute time from 2,000,000 CPU core hours (and/or 30,000 GPU hours) up to 14,999,999 CPU core hours (and/or 199,999 GPU hours) are considered normal size projects - note that the final amount of granted computing time will decided by the Steering Committee of Baden-Wurttemberg. Application for normal projects can be done any time of the year (rolling call). Allowed activities prior to the official project start can be found below.
NHR Large projects¶
NHR large projects are compute time projects that reviewed by the Steering Committee of Baden-Wurttemberg and finally approved by the NHR User Committee. Any proposal of compute time from 15,000,000 CPU core hours (and/or 200,000 GPU hours) up to 70,000,000 CPU core hours (and/or 1,000,000 GPU hours) are considered large size projects - note that the final amount of granted computing time will decided by the Steering Committee of Baden-Wurttemberg and the NHR User Committee. Application for large projects can be only done quarterly and start time is scheduled 3 months after the submission deadline.
|Call no.||Submission Deadline||Deadline techical reviews||Deadline scientific reviews||NHR user committee Meeting||Project start|
Allowed activities prior to the official project start can be found below.
Application of NHR normal and large projects¶
Any qualified prinicipal investigator can submit a proposal by using the JARDS project management platform. After finalizing a proposal via JARDS, the application form has to be printed, signed and a scanned copy has to be sent to firstname.lastname@example.org.
Detailled project description¶
During the application process you are required to upload a detailed project description, for which a template per project category is provided. The usage of the outlined structure given in the template is mandatory. Applications that do not use the required outlined structure given in the templates for the detailed project description might be rejected.
Estimating the amount of resources needed¶
It can be hard to estimate how many resources (CPU core hours / GPU hours) your project will need. The easiest way to find out is to apply for a NHR test project before handing in the proposal for a NHR normal or large project.
Please keep in mind that individual compute nodes on HoreKa are always assigned to a single job exclusively. Please calculcate your resource consumption with 76 CPU cores per node, and not 152 CPU threads per node (see the Project accounting page).
All NHR normal and large project proposals are reviewed by the multi-disciplinary Steering Committee of Baden-Wurttemberg and for large projects additionally by the NHR User Committee. Projects are marked as preliminary until the review phase is over. During this time a prinicipal investigator can already add contributors to the project (see the Manage project contributors chapter), and the project members are able to use HoreKa.
While a project is in the reviewing phase (preliminary state), usage is limited to a maximum of 5% of the requested compute hours or 500,000 CPU compute hours (whichever is more). In the rare ccase of a long reviewing phase a higher fraction of the requested computing resources will be granted on an individual base. The full amount of granted resources becomes available as soon as the project will have been approved by the Steering Committee of Baden-Wurttemberg and for NHR large projects also by the NHR User Committee.
Should the steering committee decline a project proposal, the associated accounts will lose access to HoreKa and no further computation is possible.
The project duration is 1 year starting for NHR normal projects at the date of final approval or for NHR large projects 3 months after submission deadline.
Project implementation is the responsibility of the prinicipial investigator (PI). During the project, the NHR centers will monitor the project utilization data and provide the consumption data to the PI on a regular basis, cf. Project accounting.
All computing time projects using NHR resources such as HoreKa are required to submit a final or an annual project report once the project is completed or prior the project enddate. Note that the duration of NHR normal and large projects are limited to 12 months. Reports of the last 12 months must be be written as scientific articles and, in addition to the subject-specific results above all include:
- information about achieved performances on the used computer platforms
- typical number of processors used
- degrees of parallelization and vectorization
- indication of the respective computing times (CPU core and GPU hours) to achieve the results presented
- total number of core-h consumed during the reporting period.
- list of publications
Please note that diagrams showing the scalability of your code must be included in the report. Scalability of your code must be included in the report, even if there have been no changes there have been no changes from the previous year.
The report has to be submitted latest 3 months after the project end to the NHR@KIT.
In case of a planned continuation of the project, the project report is part of the application procedure for project extension.
Only NHR normal and large projects can be extended.
Extensions of up to 3 months / 25% of the initially granted resources do not have to be re-evaluated by the steering committee.
Extensions of up to 1 year / more than 25% of the initially granted resources have to be fully re-evaluated by the steering committee.
The decision on project extension is not based on the general scientific eligibility, but rather on a description of the existing results and details and the further course and work plan/achievements of the project. Renewed proof of scalability is not required for project extension, if the complexity of the project and the numerical methods to be used have not changed.
Application of project extension¶
Project extensions are manged using JARDS. Please note that it is currently not possible to use the "Extend" function on your existing project entry, but extensions have to be handed in as new projects. During the creation of the new project, please upload an intermediary report containing a description of the existing results and details and the further course and work plan/achievements of the project as the Extended project description document.