Clusters

All clusters use SLURM (Simple Linux Utility for Resource Management) for managing job scheudling.

KU Community Cluster

The KU Community Cluster utilizes the condo model to bring together hardware purchased from different researchers into a single heterogenous cluster. This allows participating researchers to have dedicated use of their purchased nodes, or they may run larger computing jobs by sharing idle nodes owned by other researchers. The main benefit is access to a much larger cluster than would typically be available to a single research group.

The cluster hardware and software is administered by CRC staff. This removes the need for postdocs or graduate students from maintaining your computing system. CRC staff also assists users with any problems they may have using the cluster and helps new users by conducting training sessions and one on one sessions.

You must be an owner of hardware in the KU Community Cluster or be sponsored by an owner group within the cluster to gain access. There is no free partition of the cluster and we currenlty do not have a rate charge of core hours.

Bigjay

Bigjay is a NSF funded cluster providing traditional high performance and high throughput computing. It is currently restricted to the PIs, Co-PIs, and their collaborators. It however is part of the sixhour parititon within the KU Community Cluster.

Hawk

Hawk is a small condo model high performance cluster for use with Research Health Information (RHI), or Research Identifiable Data.

Individually identifiable health information that is used in research but that are not associated with or derived from a healthcare service event is considered research health information (RHI), or research identifiable data. Additionally, data that were previously considered protected health information (PHI) that are obtained pursuant to a HIPAA authorization or IRB waiver of HIPAA authorization are also considered RHI. Even though it is not PHI, you should still separate individual identifiable data elements from non-identifiable data elements whenever it is feasible. Furthermore, user access control should be implemented to provide the minimum necessary access to RHI and RHI must only be processed, stored, and transferred via approved methods.