Skip to content

Terms and conditions

Your use of AI-LAB is subject to the following terms and conditions.

General principles

As a general principle, the HPC resources are intended to provide additional computational power to AAU students and teachers.

What is AI-LAB not intended for?

  • Processing confidential (level 2) or sensitive (level 3) data (see AAU data classifications)
  • Staff research activities
  • Running any production system
  • Long-term storage of data
  • Hosting long-term shared research projects

Looking for research HPC? If you are interested in using HPC resources for research, please explore CLAAUDIA's other HPC resources. If you need other project solutions, please submit a request via the Service Portal.

1. Access and Responsibility

The use of AI-LAB requires that you are either a student at, or an employed teacher at AAU. You are responsible for any actions taken on these systems.

2. Fair and Sustainable Use

All users must ensure fair and sustainable use of AI-LAB.

Additional shared storage is only available within the AI-LAB Projects directory.

3. GDPR Compliance and Data Responsibility

You must adhere to GDPR regulations. Students should check their responsibilities, as well as reading how AAU processes your data in the privacy agreement for AI-LAB.

AI-LAB must not be used to store confidential and/or sensitive data. If you need to process sensitive data, we recommend the use of DeiC Interactive HPC resources.

4. Job Duration

Jobs can run for no longer than 12 hours. Work that requires longer job durations should use the checkpoint feature.

5. Deletion of Accounts and Data

Each year, on 1 August, all students will lose access to AI-LAB. To regain access, students must reapply.

Files will remain available as long as the student reapplies before the end of the year. However, if no application is submitted by 31 December, all files will be permanently deleted from AI-LAB.

6. Prohibited Usage and Consequences

AI-LAB may not, under any circumstances, be used for any purpose outside the scope of study activities or teaching (internship activities are included as study activities).

Any misuse of AI-LAB will result in an immediate and permanent ban. Any criminal or unlawful activity will be reported to the appropriate authorities.

7. Updates to Terms and Conditions

We reserve the right to make periodic changes to these terms and conditions, and commit to inform users of the changes made.

8. Service Windows

What is a service window?

A service window is a scheduled time when maintenance work is done on AI-LAB that may disrupt normal use. AAU informs users in advance so they can plan their work around it. Once it is done, the system returns to normal and users can resume their work.

8.1. Right to Maintenance and Modification of Systems

We reserve the right to periodically shut off entire systems for maintenance or security purposes. These systems require maintenance and updates at regular intervals, and we commit, where possible, to provide a minimum of two calendar weeks warning before any shutdown period commences.

We reserve the right to modify, redesign, disable or remove any of the existing services. Where possible, users will be notified of major modifications to AI-LAB a minimum of one calendar month before these changes are implemented. Updates, upgrades and shutdown periods are not considered major modifications.

8.2. Communication Policy Around Service Windows

  1. Service window date reminder email

    • Sent to all users of AI-LAB
    • Dispatched 4 weeks before service window

  2. Notice of service window pre-arranged on ServiceInfo.dk

    • Put on 1 day before the service window

Time frames on shorter notice periods should be set as close to the indicated timeframes below as possible.

  1. Service window date reminder email

    • Sent to all users of AI-LAB
    • Dispatched 2 weeks before service window

  2. Orientation email about service window

    • Sent to the internal CLAAUDIA and ITS management list
    • Dispatched 2 weeks before service window

  3. Notice of service window pre-arranged on ServiceInfo.dk

    • Put on 1 week before the service window

  4. Orientation email to system owner forum / key stakeholders / research group leaders

    • Dispatched 2 weeks before service window

  5. Orientation email to all users

    • Dispatched 1 week before service window

  6. Completion of planned work changed on ServiceInfo.dk

    • Changed on first working day after the service window

  1. After 1st hour

    • Out of order notice posted on homepage / key network team pages

  2. After 2nd hour

    • Email to users and stakeholders

  3. Unresolved problems at end of day

    • Update on status — even if no change has occurred

  4. After problem resolution

    • Inside first hour of normal working hours after incident resolution
    • Problem resolved notice sent to users and stakeholders