sue-fullrun-diagnose

Diagnose missing GPU utilization metrics and attribute GPU hours to waste buckets from completed ML/HPC run bundles.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dongzhuoyao/deepresearch --skill sue-fullrun-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sue-fullrun-diagnose
Source: https://github.com/dongzhuoyao/deepresearch/tree/main/.codex/skills/sue-fullrun-diagnose
Command: npx skills add https://github.com/dongzhuoyao/deepresearch --skill sue-fullrun-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the problem of unquantified GPU hour waste and missing GPU resource utilization metrics after a completed ML/HPC scale-up experiment full run, which occurs when initial run summaries have MISSING GPU-R cells or users suspect low GPU efficiency without actionable breakdowns.

Core Features & Use Cases

  • Post-run GPU waste attribution: Reduces per-shard timing and log artifacts to assign GPU hours to discrete waste buckets (cancelled retries, setup overhead, compile tax, etc.) without launching new compute.
  • Enriched diagnostic outputs: Generates per-variant stage timing CSVs, error summaries, and updated summary reports that replace MISSING metrics with real values.
  • Use Case: After a DINOv3 evaluator fullrun on LUMI shows 15-25% GPU efficiency with missing useful_gpu_work_hours values, use this skill to identify that 40% of waste is pre-stage tail overhead and 17% is cancelled retries, so you can prioritize targeted fixes for the next run.

Quick Start

Use the sue-fullrun-diagnose skill to analyze your most recent completed fullrun bundle and fill all missing GPU efficiency metrics in the existing experiment summary.

Frequently Asked Questions about sue-fullrun-diagnose

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

FAQPage Schema
How do I diagnose GPU waste and missing utilization metrics from completed HPC experiment runs?

To diagnose GPU waste from completed HPC experiments, reduce existing per-shard timing and log artifacts to attribute GPU hours to discrete waste buckets without launching new compute. This fills missing GPU resource utilization metrics in post-run summaries.

What is GPU hour waste attribution in ML scale-up experiments?

GPU hour waste attribution is the forensic analysis of completed ML scale-up runs to assign GPU hours to discrete waste buckets like cancelled retries and setup overhead. It replaces missing GPU-R cells with real values to quantify efficiency gaps.

Can I analyze GPU efficiency breakdowns for existing runs without launching new compute?

Yes, you can analyze GPU efficiency breakdowns without launching new compute by applying post-summary forensic analysis to existing full run bundles. This reduces log artifacts to generate per-variant stage timing diagnostics and enriched outputs.

Does GPU diagnostics for HPC sandboxes require specific dependencies or components?

GPU diagnostics for HPC sandboxes requires no specific dependencies or components, operating directly on existing full run bundles. It applies to supported HPC sandboxes where initial run summaries contain missing GPU-R cells.

When should I use post-run forensic analysis for GPU resource utilization?

Use post-run forensic analysis for GPU resource utilization when initial run summaries have missing GPU-R cells, users suspect low GPU efficiency, or per-variant stage timing diagnostics are needed for existing runs on supported HPC sandboxes.