Medium allocations¶
This page provides general information about the requirements for submitting a medium allocation request. Proposals are reviewed monthly throughout the year and will be reviewed the same month if you submit your proposal prior of the 15th the same month. Vacations and holidays may affect processing times. Read more information about how to register a proposal.
Who is eligible to apply?¶
The Principal Investigator (PI) is responsible for the proposal and usage of any resources granted. You cannot be a PI for compute resources in a Medium and a Large project simultaneously.
You must be at least an assistant professor or academic research leader with full responsibility for the larger research project. You must hold an appointment of at least 60 percent at a Swedish university or research institution recognised by the Swedish Research Council, as NAISS is financed by Swedish tax payers with the objective to strengthen science and research in Sweden.
Project information¶
When registering a proposal in SUPR you have to provide the following information:
- Project title
- Affiliation name of university/institute or similar
- Abstract a scientific project abstract in English
- Requested duration and start date
- Classification according to Research Council classification codes
Resource usage¶
Explain how you have estimated your need for computing resources and justify the requested amounts for each resource. Provide motivation for the system specific information requested.
Computational resources¶
The proposal must specify the computational resources needed, including the monthly corehour requirements and the systems on which the workloads will run. This includes your estimates of the typical and maximum number of cores per job, the memory requirements (per core, per node, or aggregated, as appropriate for the resource and parallelisation model), and any other relevant technical constraints. 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.
Example 2: the expected number of jobs per month, the corehours required per job, and the anticipated runtime.
Specify and describe the software that will be used, indicating whether it must be installed on the system or provided by the project members. Clarify all licensing requirements and confirm that the requested resources support the necessary licenses. If the software is not centre provided, explain how it is parallelised and describe its scalability and performance for the problem sizes relevant to this project.
Storage resources¶
The storage section may be omitted if no storage, or only default storage, is requested. NAISS storage allocations are specified in terms of both size (GiB) and, for most resources, number of files (No.). Explain how you have estimated your storage requirements and justify the requested amounts in both categories for each storage resource. The estimate for number of files does not need to be exact; an order of magnitude estimate (e.g., 1 million files) is sufficient. If your storage needs vary over the duration of the project, please describe how they change over time. To assist the allocation process, specify the required size (GiB) and number of files (No.) for distinct periods (months) with differing demands. Provide the total required amount for each period, not incremental additions. The periods should not be overlapping and cover the full requested allocation duration.
Example: For a 12 month project with 3 initial months of preparatory/test data followed by 9 months of full scale data processing:
| Period | size (GiB) | Files |
|---|---|---|
| Months 0-3 | 2000 | 1 million |
| Months 4 12 | 5000 | 3 million |
Data management plan (DMP)¶
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:
- 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?
- 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?
- 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.
- 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.
- 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.
Sensitive data handling¶
In order to comply 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.)
- Is this project covered by a Data Processing Agreement?
Activity report¶
If you have previously been granted NAISS resources, you have to upload activity reports for those projects to be eligible for new allocations. Include an explanation for any major deviations from the originally planned usage.