quark-onnx-debug

Diagnose Quark ONNX installation, calibration, quantization, and custom-op failures.

154|27|Updated Jun 19, 2024
One-click install
npx skills add https://github.com/amd/Quark --skill quark-onnx-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quark-onnx-debug
Source: https://github.com/amd/Quark/tree/main/.claude/skills-impl/l1-atomic/onnx/quark-onnx-debug
Command: npx skills add https://github.com/amd/Quark --skill quark-onnx-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve failures in AMD Quark's ONNX workflow, including installation issues, runtime errors, calibration crashes, custom-op compilation problems, and unexpected quantization results.

Core Features & Use Cases

  • Installation Troubleshooting: Identify missing or conflicting onnx, onnxruntime, and Quark dependencies.
  • Runtime and EP Debugging: Diagnose CUDA, ROCm, and silent CPU fallback issues caused by unavailable or misconfigured execution providers.
  • Quantization and Calibration Recovery: Handle calibration reader bugs, OOM conditions, unsupported quantization settings, and algorithm-specific failures.
  • Custom Op and Export Validation: Resolve custom-op load failures, ABI mismatches, large-model external data issues, and graph or shape validation errors.

Quick Start

Paste the full Quark ONNX error message, stack trace, exact call, model details, and environment info so the Skill can produce a structured diagnostic report and smallest safe fix.

Frequently Asked Questions about quark-onnx-debug

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

FAQPage Schema
How do I fix Quark ONNX quantization failures and calibration crashes?

To fix Quark ONNX quantization and calibration failures, provide the full error trace, model details, and environment info to diagnose calibration reader bugs, OOM conditions, and unsupported settings for a structured recovery report.

Why does ONNXRuntime silently fall back to CPU during execution on CUDA or ROCm?

ONNXRuntime silently falls back to CPU when execution providers are unavailable or misconfigured; debugging requires validating your environment details and provider setup to resolve CUDA or ROCm configuration issues.

How do I resolve custom op compilation errors when exporting PyTorch models to ONNX?

Resolving custom op compilation errors when exporting PyTorch models to ONNX involves validating custom-op load failures, ABI mismatches, and graph or shape validation errors using your exact call stack and model context.

Does Quark ONNX debugging support NPU execution providers?

Yes, Quark ONNX debugging supports NPU execution providers, applying to PyTorch-to-ONNX and ONNX graph optimization scenarios across CPU, CUDA, ROCm, and NPU environments to validate versions and provider compatibility.

What is the best way to diagnose missing or conflicting onnxruntime dependencies during Quark installation?

The best way to diagnose onnxruntime dependency conflicts during Quark installation is to analyze environment details and version info to identify missing or conflicting onnx, onnxruntime, and Quark packages.