REPACSS CPU

RP account needed

REPACSS CPU is the general-purpose partition of REPACSS, a power-aware cluster that runs on variable energy. It has 110 nodes, each with dual AMD EPYC 9754 CPUs (256 cores), 1.5 TB RAM, and 1.92 TB local NVMe on InfiniBand, suited to multi-core and MPI simulation and in-memory analyses.

Get Support

OFFICE HOURS

Email repacss.support@ttu.edu to schedule

GET AN ACCOUNT ON REPACSS CPU

External TTU Account Setup Help

Submitting Jobs Documentation

You can run jobs of different sizes and durations on REPACSS. The list below shows the queues you can submit to, with the nodes, max runtime, hardware, and average wait time for each.

Jobs run through Slurm; the login node is for editing, compiling, and staging only. CPU jobs go to the zen4 partition, submitted with sbatch or run interactively with the interactive wrapper (REPACSS recommends it over salloc). It handles the full range of CPU work e.g. serial, OpenMP, MPI, and hybrid. Max wall time isn't published — run sinfo to check current limits. See the Job Basics and Job Examples guides for sample scripts.

For more details, please visit [Credits for REPACSS Resources page], [REPACSS Jobs Basics], and the [Job Examples page].

Queue specifications Documentation

Queue CPU cores / node Num nodes Node RAM
zen4
General-purpose parallel/serial computing, memory-intensive processing, and standard MPI workloads
 2x AMD EPYC 9754 (256 cores) 110 1536 GB

Software Documentation

No software usage data is currently reported for REPACSS CPU in XDMoD.

SEE ALL SOFTWARE AVAILABLE ON REPACSS CPU

Storage Documentation

REPACSS storage is allocated per group (shared by project members): $HOME for scripts and config, $SCRATCH for active job I/O (not for long-term storage), and $WORK for results to keep. Each group shares 9 TB across the three areas. Check your group's usage from a login node with quota -s.

For more information, visit the [Introduction to REPACSS: A Beginner’s Guide].

File System Documentation

Directory Path Quota Purge Backup Notes
Home $HOME See notes Persistent personal storage for user scripts and configuration files. Quota varies by allocation; check your group's usage with df -h /mnt/$(id -gn)
Scratch $SCRATCH See notes High-performance temporary storage space subject to periodic purging. Quota varies by allocation; check your group's usage with df -h /mnt/$(id -gn)
Work $WORK See notes Long-term storage for research outputs and work purposes. Quota varies by allocation; check your group's usage with df -h /mnt/$(id -gn)
Shared Area /mnt/SHARED-AREA See notes Quota varies by allocation.
Shared Scratch /mnt/SHARED-SCRATCH See notes Quota varies by allocation.

File Transfer Documentation

Globus Connect is the recommended way to move data in and out of REPACSS, through the collection named REPACSS. Do not use scp, sftp, rsync, or direct connections to the login nodes. For step by step instructions, see [REPACSS File Transfer with Globus].

Supported Methods Data Transfer Node / Globus Collection Notes
GLOBUS CONNECT | RECOMMENDED REPACSS Transfer files in the Globus web app