Resource information

Environment

General Environment
The General Environment is suitable for research work without sensitive data.Protected Environment
The Protected Environment must be used for projects with protected health information. Access to the Protected Environment is granted on a per-project basis; please see the environment's documentation for more information.

Resource type

Access type

Resources owned by the CHPC and its partners

Unallocated resources
All users may submit jobs to unallocated resources.
Recommended for new users

AI-related research (resources owned by the One-U Responsible AI Initiative)
One-U Responsible AI Initiative GPU nodes are available, upon request (to helpdesk@chpc.utah.edu), to researchers with AI-related projects.

The options below require allocation for priority access. The CHPC has limited resources (computational time) available to researchers, and it apportions time on in-demand systems (generally newer hardware than unallocated resources) by merit. Most allocation requests are reviewed by a committee of researchers from various departments. Small allocations are reviewed internally by CHPC staff. For more information, including instructions for applying for an allocation, please see our documentation on allocations.

CPU allocation (my group has a CPU allocation)
CPU allocation provides priority access to CPU-only, CHPC-owned nodes.CPU freecycle (my group does not have a CPU allocation)
Users without a CPU allocation may submit freecycle jobs. Freecycle jobs run on CHPC-owned nodes with low priority. If a user with a CPU allocation submits a job, freecycle jobs may be canceled.
Subject to preemption

GPU allocation (my group has a GPU allocation)
GPU allocation provides priority access to CHPC-owned nodes with GPUs.GPU freecycle (my group does not have a GPU allocation)
Users without a GPU allocation may submit GPU freecycle jobs. GPU freecycle jobs run on CHPC-owned nodes with GPUs with low priority. If a user with a GPU allocation submits a job, GPU freecycle jobs may be canceled.
Subject to preemption

Resources owned by research groups

Node ownership (my group has purchased nodes)
Research groups may purchase nodes; researchers affiliated with a group have priority access to group-owned nodes.Guest (my group has not purchased nodes or I want to use other groups' nodes)
All users may run jobs on research group-owned nodes when they are not in use. If a user from the owner group submits a job, guest jobs may be canceled.
Subject to preemption

Node sharing

Show partitions with node sharing enabled
Node sharing allows multiple jobs to run on a single node. In contrast, partitions without node sharing allocate entire nodes for jobs. Node sharing allows users to utilize resources more effectively for small jobs, but it is still possible to request an entire node by specifying --mem=0, so we recommend that all users use partitions with node sharing enabled.
Recommended for most usersShow partitions without node sharing enabled