What problem does it solve?
This Skill solves the operational pain of running large multi-seed or phased ML experiment batches without losing progress to OOM failures, stale detached screens, or wave-order race conditions.
Core Features & Use Cases
- Wave-based orchestration: Runs jobs in GPU-fit waves and only starts the next wave after processes fully settle, stale screens are cleared, GPU free memory is sufficient, and preconditions pass.
- OOM-aware retry: Detects CUDA OOM from per-job logs, kills the failed screen, waits, re-queues, and limits retries before marking jobs as stuck.
- Stale-screen cleanup & resume: Detects “screen exists but Python exited,” verifies expected outputs, cleans up, persists queue state to JSON continuously, and supports restarting/reloading without rebuilding.
- Phased dependency chaining: Enforces teacher→student or other depends_on phase workflows so downstream jobs wait for checkpoints.
- Grid/manifest driven execution: Builds a reproducible manifest from declarative grid specs, including phase templates, expected outputs, and resource scheduling parameters.
Quick Start
Use the experiment-queue skill to run batch experiments by asking: “Batch experiments on SSH GPU servers using the provided manifest or grid spec, orchestrate waves with OOM retry and stale-screen cleanup, and resume from state if needed.”