Project Description Large Spring 2026¶

Here are detailed instructions for what you should include in the project description for the NAISS Large Spring 2026 call. If you are re-using a description from an earlier proposal, please highlight changes. We urge you to respect the maximum page limits for all sections.

Overview (0.5 page)¶

Provide an abstract of the proposed research.

Include information on computations if compute resources are requested.

If storage resources are requested include data origin and planned analysis. If relevant mention which compute projects other than this that are generating the data (NAISS projects, PRACE, et cetera)

Resource usage, codes and performance (1.5 pages)¶

This section is required if at least one compute resource is requested. It can be omitted if only storage resources are requested. Provide a detailed description of how your applications will make efficient use of the requested computational resources. Include quantitative evidence such as scalability studies, performance measurements, or graphs (e.g., execution time as a function of core count). Specify the computational resources needed, including the estimated number of gpuhours and/or corehours per month and the systems on which the work will run. These estimates should be supported by calculations.

Example 1: the expected number of jobs per month, the gpuhours required per job, and the anticipated runtime.

gpuhour_per month = nodes x used_gpus_per_node x wall_time x number_jobs_month

Example 2: the expected number of jobs per month, the corehours required per job, and the anticipated runtime.

corehour_per_month = nodes x used_cores_per_node x wall_time x number_jobs_month

If the requested resources differ significantly from previous allocations or from previously used resources, explain and justify the changes, including any requirements for specialised hardware such as large memory nodes or GPUs. If the project is not a direct continuation of an earlier one, or if you have not previously been granted resources for similar work, include relevant records of past usage. The proposal must also include a detailed description of all required software, indicating whether it must be installed on the system or supplied by the users. Additionally, clarify any licensing requirements and confirm whether the requested resources support the necessary licenses.

Data management plan (1.5 pages)¶

This section may be omitted if no storage, or only default storage, is requested. It should in particular describe how storage and backup of data and metadata are safeguarded during the research process, how long-term storage is safeguarded, and by whom. Users are encouraged to organise their data systematically and maintain clear documentation of file contents.

Include at least the following:

1. Please describe the type of data to be managed. Describe the type/types of data to be used in the project, including how data are to be generated/collected. How will data be captured (e.g.: questionnaires, interviews, observations, measurements, recordings etc.). If necessary, has the project passed an ethical review? Can the data be considered sensitive personal data? Include quantitative information when available, such as estimated initial data volume, expected growth throughout the project, and approximate number of files, to justify requested NAISS storage.
2. Please briefly describe data flows, including processing, and tools which may be used to manage data. E.g. How will you organise data that is collected/reused? Will data be organised in databases? Will a specific software or tool be required to use the material? Describe how data will be handled within the NAISS environment, including how ephemeral (scratch) storage versus project storage will be used. Provide a brief motivation for how the requested storage will be efficiently used based on workflow, file size, production rates, and processing steps. If relevant, explain how data will be transferred into and out of the NAISS system.
3. Please describe the downstream plan for your data. E.g. Where will you transfer the dataset at the end of the allocation? Describe the mechanism by which you will transfer data to external sites for further analysis or archival at the end of the allocation. Give an estimate of the amount of data that will be transferred in each transfer instance. Explain how data will be handled if continued NAISS storage is not granted. If applicable, describe whether data will be made publicly available, for example through a general-purpose repository such as Zenodo.
4. NAISS strongly recommends keeping a copy of primary research data elsewhere, so briefly describe where primary data will be stored and how backup will be managed. If the project is not a direct continuation of a previous allocation, include a brief record of previous storage usage if relevant to motivate the current request.
5. Storage is intended only for active data used in analysis, therefore you should explain how outdated or unused data is routinely removed during the project. If storage at a specific NAISS centre is required (e.g. due to hardware, data locality, or workflow constraints), provide justification here or reference the appropriate section.

Sensitive data handling (1 page)¶

In addition to sections Resource usage, codes and performance (1.5 pages) and Data management plan (1.5 pages) above, this section is required if at least one resource for sensitive data is requested. It can be omitted if no resource for sensitive data is requested.

To ensure the compliance with GDPR, we need the following information:

• Categories of data subjects (e.g. citizens, patients, students, etc.)
• Types of personal data (e.g. name, identifier, address, etc)
• Types of sensitive personal data (e.g. voice, genetic information, political opinions, etc.)

We also want to understand certain aspects of your data management plan. Please describe the type of data that will be stored in this project. Answer at least the following questions:

• If you have drawn up a Data Management Plan (DMP), please provide the link. If not, consider Data Stewardship Wisard or DMPonline.
• The type of data to be stored (genomes, fastq files, image data, .tiff files, etc).
• Is this project covered by a Data Processing Agreement?
• Have you completed a Data Protection Impact Assessment? Read more at the Swedish Authority for Privacy Protection.

Scientific challenges (2 pages)¶

Describe how the proposed project relates to the state of the art of the scientific area, has the potential to increase the knowledge within its scientific area, and how the proposed project uses adequate computational methods to address scientific questions. Include a justification for the need of large-scale data/HPC.

Research group and management (0.5 page)¶

Describe the complete research group that will be working on the proposed project: name of member, HPC experience, position, and roles. Indicate how the allocated resource will be managed within the group.

References (0.5 page)¶

Include a list of references for the project description.