Policies

UF Research Computing Acceptable Use Policy

This acceptable use policy applies in addition to the UF Acceptable Use Policy and UF Information Technology Acceptable Use policy

The purpose of HiPerGator and its related resources is to advance the scientific, educational, and research efforts of the University of Florida and its partners. Any activity that interferes with this purpose may be modified or cancelled by UFIT Research Computing staff.

By using HiPerGator systems and resources, you agree to the following Acceptable Use Policy.

A valid GatorLink account is required to obtain a HiPerGator account. Active computational and blue storage allocations are required for data analyses, creation, or maintenance of active user accounts on HiPerGator.

Login Nodes

Login nodes are intended to be used for managing jobs or data, editing files, and similar tasks. Short interactive tests consuming no more than a total of 16 cores, 64GB of memory for up to 10 minutes are permitted as long as they do not impact other users. UFRC reserves the right to terminate any processes outside of the guidelines or any processes that impact the node performance or interactive user experience on the login nodes. If test requirements exceed the above resource limits or processes need to run across nodes (e.g. parallel computing with MPI), then users must request an interactive session on the development partition.

Scheduler/Job

Scheduled jobs are intended as the main mechanism for data analyses on HiPerGator. Investment QOS jobs have the priority in the queue. There are no guarantees for job start time or resource availability in the burst QOS. There is no burst QOS for GPU jobs. Processes that frequently poll the scheduler for queue or job status are not allowed. Inefficient job requests that result in significant unused resources or limit the availability of limited resources may be terminated without warning.

Jobs which request resources in GPU partitions but do not use GPUs are not allowed.  Jobs which request GPUs but do not use them will result in job termination and/or account suspension.

Storage

Storage provided by UFIT Research Computing (UFRC) is only for research and educational data, code, and documents for use on HiPerGator and with HiPerGator services. UFRC creates, modifies, and enforces quotas based on group allocations. In addition, UFRC reserves the right to delete, move, or otherwise make data unavailable on any storage system as deemed necessary by UFRC personnel to maintain the overall quality of service.

While UFRC makes every effort to maintain the availability and integrity of our storage systems, the storage systems are not backed up by default. Users are responsible for purchasing backup services or setting up backups of their data.

Each HiPerGator user is provided 40GB of home directory storage. The home area is intended for source code, scripts, and project documents and cannot be used for Input/Output (I/O, i.e. Reading or Writing) from jobs and programs. Limited file recovery is available via daily snapshots of home areas for one week and weekly snapshots for three additional weeks.

Blue is the main shared storage. Jobs and programs are expected to perform their I/O and write their outputs to Blue storage. An investor may request a free Blue storage quota increase for up to three months once per year. Additional ‘burst’ storage with a recurring 30-day grace period may be allocated based on project need.

Orange storage is intended to be used for long-term retention of data that is not actively involved in job computations and for light-duty services like static data serving via https://data.rc.ufl.edu. An active Blue allocation is required to acquire an Orange allocation.

Red is high-performance shared storage intended for short-term storage in jobs for projects that require the highest I/O performance. Red storage allocations cannot be purchased, only assigned based on need upon Director approval. Data is removed 24 hours after allocation expiration.

Local job scratch storage on compute nodes is configured automatically for each job. There is no quota, and the local scratch data for the job is removed when the job ends. UFRC will make a reasonable effort to manage free space on local scratch storage, but user processes may fill up local storage. UFRC is not responsible for job failures resulting from full local scratch. For more information about data removal procedures visit https://www.rc.ufl.edu/about/procedures/.

Restricted Data

If your research data contains HIPAA (Health Insurance Portability and Accountability Act), FERPA (Family Educational Rights and Privacy Act), PII (Personally Identifiable Information), PHI (Protected Health Information), or any other regulated data, please contact Research Computing staff prior to using any Research Computing systems to verify that all required measures and controls are supported.

Cryptocurrencies and Mining

Performing “mining” operations involving cryptocurrencies such as BitCoin, distributed cryptography such as the distributed.net projects, and all forms of volunteer computing such as Folding@Home are prohibited.

Licensing

Some software offered on the system is controlled by individual license agreements. It is the responsibility of the user to maintain proper licensing of any user-installed software.

Maintenance

Research Computing makes every attempt to schedule server and cluster maintenance during regularly scheduled maintenance windows. However, issues do occur that may need to be handled outside these pre-described maintenance windows.

Service Accounts

Research Computing supports the use of non-interactive service accounts for workflow and application execution or data transfers from external sources. Submit a support request to start the process of obtaining an approved service account. Project duration and sufficient documentation are required with the account request.

Account aliases for interactive use by a person that are associated with a position that changes regularly are not supported by RC.

MFA

Multi-Factor authentication is required for all individual Research Computing accounts.