experiment-queue

Automate large-scale ML experiment batches on remote SSH GPU servers.

2|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/goupup-ai/miccai25 --skill experiment-queue-goupup-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-queue
Source: https://github.com/goupup-ai/miccai25/tree/main/ARIS/skills/experiment-queue
Command: npx skills add https://github.com/goupup-ai/miccai25 --skill experiment-queue-goupup-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

Running 10 or more machine learning experiments (such as multi-seed sweeps, grid searches, or teacher-student training chains) manually requires constant monitoring for stale screen sessions, out-of-memory errors, and wave transition timing, leading to wasted wall-clock time, lost state on scheduler crashes, and repeated engineering work for each new experiment batch.

Core Features & Use Cases

  • Automated Batch Scheduling: Runs 10+ parallel jobs across multiple GPUs with automatic wave transitions, eliminating the need to manually coordinate job launches and GPU allocation.
  • Resilient Failure Handling: Auto-detects CUDA out-of-memory errors to retry jobs after a configurable delay, cleans up stale screen sessions where Python processes have exited, and persists full state to disk to recover from scheduler crashes or SSH disconnections.
  • Phase Dependency Support: Enforces sequential workflows like teacher model training followed by student distillation, so later jobs only launch when their required checkpoint outputs exist.
  • Use Case: If you need to run 42 experiments across 2 training phases (teacher training then student distillation) with 3 random seeds per configuration, this skill automatically schedules jobs across available GPUs, retries any OOM failures, and generates a summary report when all jobs finish.

Quick Start

Use the experiment-queue skill to run your multi-seed vertebrae segmentation experiment grid with automatic wave transitions and OOM retry.

Frequently Asked Questions about experiment-queue

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

FAQPage Schema
How do I automate multi-seed ML experiment sweeps across remote GPUs?

Automating multi-seed ML experiment sweeps requires a job queue that schedules parallel jobs across available GPUs with automatic wave transitions. This skill orchestrates batches of 10 or more jobs and persists state to disk to eliminate manual coordination overhead.

How does out-of-memory retry work for long-running GPU training pipelines?

Out-of-memory retry for GPU training pipelines detects CUDA OOM errors and automatically retries the failed job after a configurable delay. It cleans up stale screen sessions where Python processes have exited, ensuring the pipeline continues without manual intervention.

Can I enforce phase dependencies for sequential teacher-student training chains?

Enforcing phase dependencies for sequential teacher-student training chains ensures later jobs only launch when required checkpoint outputs exist. The scheduler tracks these dependencies automatically, preventing student distillation from starting before teacher training completes.

What is the best way to recover ML experiment state after an SSH disconnection?

Recovering ML experiment state after SSH disconnection requires persisting full scheduler state to disk. This skill saves the queue state continuously, allowing the orchestration process to resume batch jobs seamlessly upon reconnection without losing progress.

How do I clean up stale screen sessions from crashed Python processes on a GPU server?

Cleaning up stale screen sessions from crashed Python processes on a GPU server is handled automatically during wave transitions. The scheduler detects inactive screens where the Python process has exited and removes them before launching the next batch of jobs.

Does experiment-queue work for large grid searches with bounded automatic retry logic?

Experiment-queue works for large grid searches by applying bounded automatic retry logic to failed jobs. It coordinates scheduling across multiple GPUs and generates a summary report when all configurations finish, reducing wall-clock time for extensive sweeps.