slurm

Launch and manage GPU-accelerated SLURM jobs on the SONIC cluster.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/aaaxn/skills --skill slurm-aaaxn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slurm
Source: https://github.com/aaaxn/skills/tree/main/slurm
Command: npx skills add https://github.com/aaaxn/skills --skill slurm-aaaxn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines launching and managing GPU-accelerated jobs on the SONIC SLURM cluster, handling environment setup, partition selection, and dataset staging to prevent common mismatches and timeouts.

Core Features & Use Cases

  • Provides a clear submission workflow for squeue/sinfo/sbatch by exporting SLURM_CONF before each call.
  • Guides partition and GPU architecture choices (e.g., gorgonas and medusas with cu124/cu128/cu130) and recommends dataset staging to fast filesystems.
  • Covers environment management and data handling tips, including venv placement and dataset caching strategies to minimize I/O bottlenecks.

Quick Start

Submit your first SLURM job from phocus4 after exporting SLURM_CONF and selecting an idle partition.

Frequently Asked Questions about slurm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit a SLURM job on the SONIC cluster from phocus4?

To submit a SLURM job on SONIC from phocus4, you must export SLURM_CONF before executing sbatch, enforce an idle partition, and stage datasets to designated filesystems to prevent mismatches and timeouts.

Why do I need to export SLURM_CONF before running squeue or sbatch on SONIC?

Exporting SLURM_CONF before running squeue, sinfo, or sbatch is required on SONIC to ensure the SLURM commands correctly target the cluster configuration, preventing command failures and job submission errors.

What is the best way to manage CUDA versions when deploying GPU jobs on gorgonas and medusas?

Managing CUDA versions for gorgonas and medusas requires selecting compatible environments matching cu124, cu128, or cu130, while properly configuring venv paths to avoid runtime mismatches during GPU-accelerated training runs.

Where should I stage datasets for SLURM jobs to minimize I/O bottlenecks on SONIC?

To minimize I/O bottlenecks on SONIC, stage datasets to fast filesystems such as /tmp, /snfs2, or /sonic_home, utilizing dataset caching strategies to optimize data loading during model evaluation and training.

Can I use this workflow to launch data processing and model evaluation across different GPU architectures?

Yes, this workflow supports launching training runs, data processing, and model evaluation across different GPU architectures like gorgonas and medusas by guiding partition selection and environment variable management.

What are common limitations when deploying training runs on the SONIC SLURM cluster?

Limitations when deploying on SONIC include potential dataset staging mismatches if not placed on /tmp, /snfs2, or /sonic_home, and job timeouts if idle partitions are not strictly enforced before submission.