HPC Run

Submit and manage SLURM-based MDClaw workloads on HPC clusters.

11|2|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/matsunagalab/mdclaw --skill hpc-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: HPC Run
Source: https://github.com/matsunagalab/mdclaw/tree/main/skills/hpc-run
Command: npx skills add https://github.com/matsunagalab/mdclaw --skill hpc-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating efficient SLURM submissions for the MDClaw workflow on HPC clusters, handling login-node interactions, array jobs, and checkpoint extensions.

Core Features & Use Cases

  • Submits eq/prod nodes with SLURM, supports single-node and array patterns, and tracks DAG state and job metadata.
  • Provides cluster discovery, policy validation, and Singularity container integration to streamline GPU-enabled runs.
  • Suitable for multi-system campaigns, job chaining with per-entry failure isolation, and checkpoint restarts.

Quick Start

Create an eq node and submit a corresponding prod job on the target cluster using mdclaw.

Frequently Asked Questions about HPC Run

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

FAQPage Schema
How do I submit MDClaw workloads to a SLURM cluster?

Submitting MDClaw workloads to a SLURM cluster requires SLURM tooling like sbatch and a prepared MDClaw job directory with topo inputs and optional container configuration to manage single-node runs and job arrays.

Can I use Singularity containers for GPU-enabled SLURM job submissions?

Yes, Singularity container integration is supported to streamline GPU-enabled SLURM job submissions, allowing you to execute MDClaw workflows with proper environment isolation and policy validation on HPC clusters.

How do I manage job arrays and checkpoint restarts for MDClaw simulations?

Managing job arrays and checkpoint restarts for MDClaw simulations involves tracking DAG state and job metadata, enabling per-entry failure isolation and chained workflows across multiple systems for robust HPC campaign execution.

What SLURM tools are needed to run MDClaw workflows on HPC?

Running MDClaw workflows on HPC requires SLURM tooling including sinfo for cluster discovery, sbatch for job submission, squeue for tracking, and sacct for accounting to validate policies and manage job state.

How do I chain eq and prod nodes in a SLURM-based MDClaw workflow?

Chaining eq and prod nodes in a SLURM-based MDClaw workflow is achieved by creating an eq node and submitting a corresponding prod job on the target cluster, tracking DAG state to ensure proper execution order.

Does this approach handle multi-system campaign submissions for MDClaw?

Yes, multi-system campaign submissions are supported, providing cluster discovery, policy validation, and per-entry failure isolation to coordinate efficient SLURM submissions across different HPC environments for MDClaw.