wandb-clean-empty-runs

Deletes W&B run directories and server records lacking successful step metrics.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/Kirrito-k423/AutoResearch --skill wandb-clean-empty-runs-kirrito-k423
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wandb-clean-empty-runs
Source: https://github.com/Kirrito-k423/AutoResearch/tree/main/workspace-core/wandb-clean-empty-runs
Command: npx skills add https://github.com/Kirrito-k423/AutoResearch --skill wandb-clean-empty-runs-kirrito-k423

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? W&B experiment directories and local server databases accumulate empty or failed runs that contain no useful step metrics, wasting disk space and cluttering the experiment UI. This Skill identifies and removes only those runs that lack any successful step evidence, while preserving runs with real training or validation signals. ## Core Features & Use Cases - Filesystem Cleanup: Scans wandb and offline-run-* directories for success signals such as wandb-summary.json metrics, step:N log lines, and val-core//val-aux/ validation output, then dry-runs or deletes no-signal units. - Local Server Cleanup: Soft-deletes empty runs in the Dockerized local W&B MySQL database (runs, runs_flat, files tables) and optionally removes matching MinIO object directories. - Safe Deletion Workflow: Always supports dry-run reporting first, deletes only the highest nested candidate to avoid double counting, and can prune leftover empty directories. - Use Case: After a series of failed smoke tests left dozens of empty offline runs under ~/autoResearchData/autoresearch-log/wandb/offline-runs, run a dry-run to review candidates, then delete them and rebuild the local W&B UI. ## Quick Start Ask the assistant to dry-run the W&B empty run cleanup over the default AutoResearch roots and show which runs would be deleted before confirming deletion.

Frequently Asked Questions about wandb-clean-empty-runs

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

FAQPage Schema
How do I delete empty W&B runs from disk?▼

Run the clean_wandb_empty_runs.py script against your W&B roots first without flags for a dry-run, then add --delete to remove the selected no-signal units. It scans wandb and offline-run-* directories and only deletes runs lacking step or validation metrics.

How do I remove empty runs from a local W&B server?▼

Use clean_wandb_local_server.py with your entity and project to dry-run candidates, then add --delete to soft-delete rows in the runs, runs_flat, and files MySQL tables. Add --remove-files to also remove the matching MinIO object directories.

What counts as a successful W&B run worth keeping?▼

A run is kept when wandb-summary.json contains non-system metric keys, logs contain step lines like step:0, or validation text such as val-core/ or val-aux/ metrics appears. A bare _step value alone is treated as insufficient evidence.

Does the cleanup script delete entire experiment directories?▼

No, it only deletes candidate W&B units, meaning directories named wandb or standalone offline-run-* directories. When candidates are nested, only the highest candidate parent is removed so files are not counted twice.

Why does the local W&B UI still show deleted runs?▼

The server cleanup soft-deletes database rows by setting deleted_at, but the browser may show stale cached results. Restart the ar-wandb container after DB cleanup to refresh the UI.