From ALICE Documentation

Revision as of 21:52, 21 September 2020 by Kosterj1 (talk | contribs) (Access policy)

Access policy

The access policy for ALICE is very similar but more restrictive than the Leiden University Account Policy.

Facilities are available to all researchers from both Leiden University and LUMC. Please review the policies for the system, this will assist in finding the right level of service for your project and choosing job parameters correctly. Overall we want to provide the best quality of service to all users so please consider how we may improve the service you receive and give us your feedback.

Access needs to be granted actively (by the creation of an account on the cluster). Use of resources is limited by the scheduler. Depending on the availability of queues ('partitions') granted to a user, priority to the system's resources is regulated on the basis of Faculty/institute/PI levels.

To request an account on ALICE, contact (mail request). Please provide as much as possible of the following information:

  • Full name of user (and if known, ULCN or LUMC account)
  • Affiliation: research group (PI), institute, faculty (and organization, if not Leiden University or LUMC)
  • Type of employment (HL, UHD, UD, Postdoc/researcher, PhD-, MSc- or BSc student, guest researcher). Students must provide the name of their supervisor. Guest researchers must provide the name of their host. Project PIs can request users to be added to their project. Supervisors and hosts can request access for students and guest researchers, respectively.
  • Starting date for the access
  • End date for the access. Some default durations apply for the accounts for the different types of employment; these are renewable upon request.
  • Research/education. Specify whether the access is need for research or education.
    • Research: provide a short description of the research/work that will be carried out (max 200 words); if possible include the relevant research grant number(s). Specify if this information cannot be used for dissemination purposes by the university.
    • Education; if possible add the name(s) of the course(s) and teacher(s). Specify also what type of work it concerns, e.g., dissertation, student assignment, etc.
  • Type of usage. Specify if the usage concerns code development, code testing and debugging, model scaling (performing larger executions), production usage (a series of recurring job executions), pre- and postprocessing of data, interactive and/or batch usage of nodes, etc.
  • Required resources. Provide a short description of the resources that are needed: CPU and/or GPU, software applications and libraries, an estimate of the total number of jobs and computing hours, and the need for permanent (/home) as well as temporary (/scratch) storage (in TB). Add any information that may help the support staff to determine at an early stage if assistance is needed.
  • Experience. Specify if the user is familiar with using Linux and using HPC resources / compute clusters. This will help support staff point the user at relevant training material.