REPACSS CPU is the general-purpose partition for processor-based computing on Texas Tech's REPACSS cluster, built for parallel simulation, modeling, and data analysis that runs on CPUs rather than GPUs. Its defining characteristic is per-node capacity: each node combines a high core count with a large pool of memory and fast local storage. With that much on a single node, work that would otherwise be spread across several nodes — high thread-count jobs, or analyses that need a large dataset held entirely in memory — often fits on one, which keeps code simpler and avoids inter-node communication overhead. When a job does need to scale past a single node, the nodes are linked by a high-speed interconnect for multi-node MPI.
That makes REPACSS CPU well suited to large-memory R and Python workflows, in-memory analytics, genomics, and multi-core or MPI simulation. REPACSS is also a Texas Tech research prototype designed to run high-performance computing on variable, renewable energy, so it additionally fits researchers with an interest in energy-aware or sustainable computing, on top of those who simply need the cores and memory.
Jobs
Work on REPACSS is managed by the Slurm workload manager. After logging in, you land on a login node, which is meant only for preparing work like editing files, compiling code, and staging data, not for running it. All computation must be submitted to the compute nodes as a Slurm job. Jobs run either as batch scripts (submitted with sbatch) or as interactive sessions (started with the interactive wrapper, which REPACSS recommends over calling salloc directly). CPU work runs in the zen4 partition, which is also the cluster's default, so a job that doesn't name a partition is sent there.
Slurm schedules by priority rather than strict first-come-first-served: jobs gain priority the longer they wait (aging), and a backfill mechanism lets smaller or shorter jobs fill gaps ahead of larger ones, so tightly-scoped jobs often start sooner. The zen4 partition handles the full range of CPU workloads such as serial, multithreaded (OpenMP), distributed (MPI), and hybrid MPI+OpenMP, along with job arrays and dependencies for managing many related runs. One REPACSS-specific detail worth knowing: each Slurm "CPU" is a hyperthread, so for threaded code you'll generally want --cpu-bind=cores to pin threads to physical cores.
Jobs are charged against your ACCESS allocation at 1 ACCESS credit per CPU core-hour, so one full 256-core node used for one hour draws 256 credits. Walltime limits aren't stated in the user guide, so confirm those with sinfo/scontrol or the REPACSS team.
The following is an example on how to create and compile a test program and the basics of a job script:
- Create a file named
mpi_program.cwith the following content:
#include <stdio.h>
#include <mpi.h>
int main(int argc, char **argv) {
int rank, size;
char processor_name[MPI_MAX_PROCESSOR_NAME];
int name_len;
MPI_Init(&argc, &argv);
MPI_Comm_rank(MPI_COMM_WORLD, &rank);
MPI_Comm_size(MPI_COMM_WORLD, &size);
MPI_Get_processor_name(processor_name, &name_len);
printf("Hello from processor %s, rank %d out of %d processors\n",
processor_name, rank, size);
MPI_Finalize();
return 0;
}- Load the required modules and compile the program:
module load gcc/15.2.0
module load mpich/4.3.2
mpicc mpi_program.c -o mpi_program- Create a file named
mpi_job.shwith the following contents:
#!/bin/bash
#SBATCH --job-name=mpi_job
#SBATCH --output=mpi_job.out
#SBATCH --error=mpi_job.err
#SBATCH --partition=zen4
#SBATCH --time=01:00:00
#SBATCH --nodes=2
#SBATCH --ntasks=8
#SBATCH --cpus-per-task=1
#SBATCH --mem-per-cpu=2G
# Load modules
module load gcc/14.2.0
module load mpich/4.1.2
# Run MPI program using srun (for OpenMPI/MPICH)
srun -n 8 ./mpi_program- Make the script executable and submit it using
sbatch:
sbatch mpi_job.sh
For more details, please visit Credits for REPACSS Resources page, REPACSS Jobs Basics, and the Job Examples page.
Queue specifications
| Name | Purpose | Nodes | CPU cores / node | GPUs / node | Node RAM | Jobs
30 days
|
Wait Time
30-day trend
|
Wall Time
30-day trend
|
|---|---|---|---|---|---|---|---|---|
| zen4 | General-purpose parallel/serial computing, memory-intensive processing, and standard MPI workloads | — | 2x AMD EPYC 975 (256 cores) | — | 1500 GB | — | — | — |
Storage
File System
| Directory | Path | Quota | Purge | Backup | Notes |
|---|---|---|---|---|---|
| $HOME | /mnt/GROUPID/home/USERID | Persistent personal storage for user scripts and configuration files. | |||
| $SCRATCH | /mnt/GROUPID/scratch/USERID | High-performance temporary storage space subject to periodic purging. | |||
| $WORK | /mnt/GROUPID/work/USERID | Long-term storage for research outputs and work purposes. |
File Transfer
REPACSS organizes user storage into three areas, all located under your group on a shared filesystem, so storage is allocated and counted per group rather than per individual — members of a project share the same space. Home ($HOME) is persistent space for scripts, configuration, and source code. Scratch ($SCRATCH) is high-performance space for the active inputs and outputs of running jobs; it is periodically purged, so it shouldn't hold anything you need to keep. Work ($WORK) is longer-term space for research data and results you want to retain between jobs. You can check your group's current usage from a login node with df -h /mnt/$(id -gn) or quota -s.
Data moves in and out through a few methods. Globus Connect is a web-based service for large, reliable transfers, using parallel streams with automatic retry, reached through the collection endpoint named REPACSS. scp copies files over SSH from the command line and suits small or occasional transfers. rsync syncs files and resumes partial transfers efficiently, and sftp gives interactive file access over SSH — but large scp, rsync, or sftp transfers should not run on the login nodes, since that degrades performance for all users.
For more detail, please visit the File Transfer page (https://guide.repacss.org/understanding/repacss-system/file-system/file-transfer.html) and the system architecture page (https://guide.repacss.org/understanding/repacss-system/architecture.html).
| Supported Methods | Data Transfer Node | URL |
|---|---|---|
| GLOBUS CONNECT | RECOMMENDED | https://app.globus.org/dashboard | |
| SCP | ||
| SFTP | ||
| RSYNC |
Login to REPACCS CPU
Access requirements. REPACSS can only be reached from inside the TTU network. On campus, you must be on TTUnet via wired Ethernet or TTUnet Wi-Fi; TTUguest and EduRoam aren't supported. Off campus (or in buildings with known network limitations, such as Computer Science), you must first connect through TTU's GlobalProtect VPN. You also need an active TTU eRaider account with a configured password and MFA; both are prerequisites rather than optional, since MFA is enforced on the VPN used to reach the system. Please look at the VPN Setup Guide for instructions on how to do so.
Connecting over SSH. The login host is repacss.ttu.edu. From a macOS or Linux terminal, connect with ssh <eraider_username>@repacss.ttu.edu. On Windows, you can use PowerShell directly with the same command, or a dedicated SSH client like MobaXterm. Create a new SSH session using repacss.ttu.edu as the remote host and your eRaider username. On your first connection you'll be asked to verify the server's RSA key fingerprint (answer yes) and then enter your password.
Once logged in, keep in mind that the login node is meant for lightweight tasks only: editing and managing files, installing user-level software or modules, compiling code (if lightweight), and submitting SLURM job scripts. Do not run compute-intensive applications or parallel jobs directly on the login node; all computational work must go through the compute nodes via SLURM. For detailed information, please visit the SSH Login page in the REPACSS guide.
Note that the VSCode Remote-SSH setup is the one case that uses a different host name, repacss.hpcc.ttu.edu; ordinary SSH uses repacss.ttu.edu.
Password reset. REPACSS accounts are linked to TTU eRaider, so a forgotten or compromised password is reset through the eRaider system or TTU IT Help Central, not through an ACCESS portal.
For more information on REPACSS access, please visit the Connecting Overview page and the Password Management page.