submit-slurm-job

To submit a SLURM job on the Gilbreth cluster, use predefined SBATCH headers and submission commands tailored for the FRESCO pipeline. This process applies to both production and development runs, ensuring proper resource allocation and job execution.

Monitoring SLURM job status on Gilbreth involves using standard SLURM commands to track queue state and resource usage. Following runbook guidance helps verify progress after submission and prevents stalled work in the HPC environment.

Debugging stalled or failed SLURM jobs on Gilbreth requires following prescribed runbook constraints to diagnose common issues. The Skill applies specific monitoring techniques to identify why a job is stuck and provides routine troubleshooting steps.

Yes, predefined SBATCH headers can be used for both production and development SLURM job submissions on Gilbreth. This ensures consistent environment setup and satisfies runbook constraints for the FRESCO pipeline execution.

Yes, specific SBATCH header definitions are required to properly allocate GPU resources for SLURM jobs on the Gilbreth HPC environment. These definitions ensure the cluster correctly provisions hardware for the FRESCO pipeline workload.