#1085 Add Purdue RCAC institutional profiles (Bell, Gautschi, Negishi) Pull request opened by aseetharam --- name: New Config about: A new cluster config Please follow these steps before submitting your PR: • If your PR is a work in progress, include

[WIP]

in its title • Your PR targets the

master

branch • You've included links to relevant issues, if any Steps for adding a new config profile: • Add your custom config file to the

conf/

directory • Add your documentation file to the

docs/

directory • Add your custom profile to the

nfcore_custom.config

file in the top-level directory • Add your profile name to the

profile:

scope in

.github/workflows/main.yml

• Add your custom profile path and GitHub user name to

.github/CODEOWNERS

--- Summary Adds three institutional profiles for Purdue University Rosen Center for Advanced Computing (RCAC) HPC clusters: •

purdue_bell

— Bell (AMD EPYC 7662 Rome, 128c/256GB CPU) •

purdue_gautschi

— Gautschi (AMD EPYC 9654 Genoa, 192c/384GB CPU + NVIDIA L40/H100 GPU) •

purdue_negishi

— Negishi (AMD EPYC 7763 Milan, 128c/256GB CPU) Design notes • Separate profiles per cluster; shared structure, cluster-specific partition and resource mappings. • Container runtime: Apptainer (system default on all three;

/usr/bin/singularity

is a symlink). • Required user param:

--cluster_account

(hard-fails if unset; RCAC mandates

--account

on all jobs). Added to

validation.ignoreParams

to suppress schema warnings. • Opt-in

--use_standby true

routes eligible jobs through the 4 h standby QoS. • Gautschi exposes

process_gpu

label routing to

smallgpu

(L40, default) or

ai

(H100, via

--gpu_partition=ai

). • Bell and Negishi intentionally do not expose GPU labels: their GPU partitions are AMD ROCm hardware, incompatible with CUDA-only nf-core GPU modules. • Shared iGenomes mirror at

/depot/itap/datasets/igenomes

. • Container cache and work dir use

$RCAC_SCRATCH

with

$SCRATCH

and

$HOME

fallbacks (works in CI without RCAC env). Testing Each profile validated on its target cluster with:

nextflow run nf-core/demo -profile test,purdue_<cluster> --cluster_account <acct> --outdir $RCAC_SCRATCH/...

Live runs on Bell, Gautschi, and Negishi produced

sacct

records with the expected

Partition

,

Account

, and

QOS

values. Gautschi additionally validated with

--use_standby true

to confirm QoS propagation. Not included •

purdue_gilbreth

(GPU-only cluster; CPU-heavy nf-core steps would waste GPU nodes). Can be added later if a GPU-pipeline use case emerges. • Anvil (ACCESS resource); separate effort. Contact Arun Seetharam, @aseetharam, aseethar@purdue.edu nf-core/configs