From ALICE Documentation

Revision as of 21:14, 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 the following information:

  • Full name of user (and if known, ULCN account)
  • Research group, institute, faculty (and organization, if not Leiden University)
  • 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. Supervisors/hosts can also request access for students/guest researchers.
  • Starting date for access
  • End date for access (some default durations of accounts apply for the different types of employment)
  • A short description of the research/work that will be carried out; if possible include the relevant research grant number(s). Please specify if the access is requested for educational purposes.
  • Please specify also if the usage concerns code development, code testing and debugging, model scaling (performing larger executions), pre- and postprocessing, etc. If the access is for educational purposes, please specify what type of work it concerns (e.g., dissertation, assignment, etc).
  • Provide a short description of the resources that are needed for your work: 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).