Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

...

Anker
Stammdaten
Stammdaten

Meta data

...

During the course of online submission, the project proposer needs to address metadata on the HLRN service portal. This includes information about

  • the principal investigator (scientist holding a PhD),
  • the person in charge of submitting the proposal,
  • project partners,
  • other evaluations and funding for the project
  • usage of other compute resources,
  • project lifetime,
  • software requirements (please check availability with your consultant before),
  • compute time requirements in core hours, and
  • storage requirements.

Anker
Projektbeschreibung
Projektbeschreibung

Main proposal

...

The main proposal

  • needs to upload a prepared document in PDF format,

...

...

  • is written in English or German. Usually about 10 pages

...

  • ,

...

  • includes the main scientific content and has to address all relevant aspects like

...

  • Abstract 
  • Project description
    • Problem description and aims of the project
    • Scientific significance, innovation, expected results, utilization of results
    • Mathematical modeling used, 
    • Technology and tools for numerical solution 
    • Preliminary studies/results of the preceding project 

    • Descriptions of research plan and work packages
  • Computational facets
    • Software, libraries, licenses, target architecture (a list)
    • Necessity of parallel computing hardware
    • Concept for parallelization, scaling properties, application performance
    • Parallel efficiency, strong/weak scaling
    • Performance properties, precondition for estimations in the resource plan
    • Necessity of HLRN resource, larger than e.g. university
  • Resource estimation
    • Detailed plan for compute time and NPL (see Accounting and NPL)
    • work plan 
    • Storage demands, scaling properties for I/O
  • Literature
  • Funding decisions
  • Publication listproject description, computational facets and resource estimation,
  • is written based on the template  (LaTeX, Word).

For the main proposal within the template one of the three types need to be chosen

  1. initial proposal
    • scientific part
    • technical part
  2. whitelist proposal (if already evaluated by BMBF, DFG, EU, NHR, or GCS)
    • proposal and acceptance of external funding institution
    • technical part
  3. follow-up proposal
    • scientific part (brief update) and reference to the initial proposal
    • technical part

To avoid:
  • Imprecise or incomprehensible estimation of requested computational resources (especially NPL/ core-hours); for example, missing arguments to justify a certain number of N runs instead of a smaller number. One page is our recommended minimum.
  • No proof, that the software to be used is suitable and efficient for parallel execution (and parallel I/O) on our specific supercomputer. Recycling a scalability demo by a third party is meaningless, without showing that your planned production run is fully comparable to it (algorithm selection within the software, I/O pattern, machine architecture, problem size per core).
  • The overall aim and/or motivation behind the project is unclear.
  • The applicant lacks HPC/Unix skills and an experienced co-applicant is missing.
  • Insufficiency of the applicant's local resources is not indicated.

In case of questions, please contact your HLRN consultant.

In case of continuation of a running compute project ("Fortsetzungsantrag für ein Großprojekt"):

Instead of "Projektbeschreibung"/initial application, you need to submit a "Statusbericht"/status report of the current project.

The structure of the report might be similar to the initial application. "Statusbericht"/Status report should hold the following properties:

  • Describe the current status of the project and the reasons for the continuation of the project.
  • Since the referees have access to the initial application, it is reasonable to use references to the initial application instead of repeating descriptions
  • Describe results, problems and future plans
    • Current progress
    • Summary of the studies and results obtained in the preceding project
    • Publications from the initial application
    • New problems to be addressed in the continuation of the running project or problems not (fully) solved in the initial application and
      intended to be covered in the continuation of the running project
    • Differences from the initial application
    • Resource estimation
    • Detailed plan for compute time and NPL (see Accounting and NPL), work plan
    • Storage demands, scaling properties for I/O
To avoid:

...

  • The HLRN was not mentioned in relevant publications.
  • Cut & paste of previous proposals.

...

Anker
Kurzbeschreibung
Kurzbeschreibung

...

Public abstract

All present HLRN projects that have been successfully reviewed by the Scientific Board are listed on the HLRN project list. Each proposal for a compute project needs to submit a Kurzbeschreibung / project public abstract in PDF format based on the HLRN abstract template.

...