Skip to content

Policies and ProceduresΒΆ

This user documentation site is focused on practical information you may need for performing successful computational work on HiPerGator. To minimize information duplication we link to the UFIT Research Computing main website for the more foundational documents such as policies and procedures that you are responsible for following, but may not need to refer to as frequently as the practical user documentation found here. We attempt to summarize some of the policies and procedures here. Please refer to the original documents for full text of the policies.

  • Policies are the documents that set the limits of what you can do on the system to make sure the system is usable for all our clients, minimize outages, and avoid violating the policies set by the University of Florida and UFIT. Relevant documents will have to be read and acknowledged before accounts suspended for policy violations are reactivated.
    • Accounts Policy lists HPG account eligibility criteria, prohibition of the personal use of the system, authentication, account expiration, and shared account use prohibition. This policy is mandatory reading and must be read in full by every HPG user.
    • Login Node Policy, Scheduler Policy, and the Jobs andProcesses policies deal with the same area of responsibility and can be summarized as follows: Login nodes (servers) must only be used for non-computational interactive work and very short tests of job scripts. Do not run full analyses on login nodes. There are several interfaces and environments for interactive work, which are described in Development & Testing and Interfaces.
    • Storage Policy describes the major filesystems on HiPerGator, limits of their use, requirements for obtaining some types of storage, and accompanying services. See Practical Storage Use for the user documentation based on the policy.
    • Software Licensing Policy clarifies that UFIT Research Computing does not purchase software licenses for or on behalf of researchers who are required to use UF Software Licensing Services or purchase software licenses directly from vendors or resellers. WARNING: 'node-locked' licenses will not work on HiPerGator. RC requires groups to provide evidence of having Matlab and SAS licenses before they obtain access to the corresponding environment modules and to follow the appropriate access procedure for other software, e.g. the gaussian access procedure.
    • Service Level Expectations Policy explains our commitments to providing a certain level of service and availability as well as the limits of HiPerGator resource availability and user expectations.
    • Other Universities Policy. explains how researchers and instructors at other Florida universities and colleges as well as instructors at the Southeast Conference universities can obtain access to HiPerGator and use it for research or teaching.
    • PHI on HiPerGator Policy and Procedure includes both the policy and the procedure for storing and analyzing protected health information (PHI) on HiPerGator.
    • FERPA on HiPerGator Policy and Procedure includes both the policy and the procedure for storing and analyzing student records (FERPA data) on HiPerGator.
    • ITAR and EAR Policy includes both the policy and the procedure for storing and analyzing ITAR/EAR data on HiPerGator and HiPerGator-RV.
  • Procedures - documents that explain how some of the policies are implemented. They cover the following areas:
    • Groups and Allocations: mandatory membership and resource requirements for being able to perform work on HiPerGator.
    • Scheduling: brief outline of the relationships betwen HiPerGator user accounts, groups, and scheduler (SLURM) accounts and quality of service levels (QOSes) as well as the Service Level Agreement (SLA) for scheduling.
    • Teaching Support: procedures for using HiPerGator resources to teach a class.
    • Operation during an emergency outlines the procedure for handling HiPerGator resources and support during emergencies/campus closure.
    • Data Removal lists the the only procedure RC will follow for removing data from inactive HiPerGator groups with expired resources.