ALIs

kommt noch

Rules for Status Reports

Report Obligation

According to the regulations of the HLRB steering committee, each project should submit a status report every 12 months, counting from the date of acceptance of the proposal. The status report is in fact:

  1. an intermediate report, if the duration of the project will continue after the report. The intermediate report is the base for the decision whether a project will be extended for another year.
  2. a final report that presents the results of a project (both the technical and the algorithmic part) and documents the relevance of using high-end HPC resources.

Content of a Status Report

The status report is informal, but should comprise the following topics on at least 4 and at most 10 pages:

  • Summary of the goals of the project
  • Description of the computations run on the high-end systems, especially the technical and algorithmic methods, programming techniques, as well as the resources needed for those computations
  • Scientific and technical results from the computations
Use the Status Report Template for preparing your reort
  • (Optional:) Preparation and publication of a web document to be linked on the LRZ WWW-server (about 1 page with links to related pages and further reading). The document should present the results of the project in a commonly understandable way, preferably with illustrations. The document will linked under the URL
    http://www.lrz-muenchen.de/projekte/hlrb-projects/
    (which has already been used for the publication of project abstract and images).
  • Provision of reference copies of publications on the project (in electronic or printed form). Printed copies will remain at the LRZ and will not be returned.
  • The completed online questionary
    https://www.lrz-muenchen.de/services/compute/supermuc/questionary.cgi
    submitted to the LRZ.

In addition, an intermediate report - the basis for a project extension - requires:

  • reasons why the extension of the project is sensible or, if necessary, a description of encountered difficulties, necessary changes or adaption of the project goal, of the methods, of the programming technique etc.
  • estimation of the resources (CPU hours and disk space) needed for the next project period.

Publication of the Reports

  • The final reports or abstracts may be published as LRZ reports.
  • The steering committee and LRZ organize regular status and reviewing workshops. Appropriate contributions (which may be reworks of intermediate or final reports) are chosen for presentation and for publication in the resulting book of proceedings.

Project Planning

At every login, both the date of expiration and the CPU time budget of the project are listed. Since there will be an interval of up to two months between submission of an intermediate report and the acceptance of extension of a project by referees and reviewers, the report should be written in time, e.g., already before the project is running short of computing time.