...
Depending on the /wiki/spaces/PUB/pages/425995, the main proposal has to satisfy a prescribed layout:
...
Proposal type
...
Initial
...
. The layout is given in the following samples.
- Initial proposal: layout sample with the two main sections
- scientific part
- technical part
...
✓
...
- technical part
...
Follow-up
...
- scientific part (brief update) and reference to the initial proposal
- technical part
...
✓
...
- Whitelist proposal: layout sample
- Follow-up proposal:
...
- layout sample with the two main sections
- scientific part (brief update) and reference to the initial proposal
- technical part
Please avoid:
- Imprecise or incomprehensible estimation of requested computational resources (especially 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 current HPC systems architecture. 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.
- The NHR and/or HLRN was not mentioned in relevant publications.
- Cut & paste of previous proposals.
...