x5-accuracy-diagnostics

Diagnoses the first accuracy drop stage in X5 PTQ or Plugin QAT quantization pipelines.

3|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/D-Robotics/rdk-skills --skill x5-accuracy-diagnostics-d-robotics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: x5-accuracy-diagnostics
Source: https://github.com/D-Robotics/rdk-skills/tree/main/skills/oe-skills-x5/skills/x5-accuracy-diagnostics
Command: npx skills add https://github.com/D-Robotics/rdk-skills --skill x5-accuracy-diagnostics-d-robotics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a quantized model loses accuracy on the D-Robotics X5 platform, it is hard to tell whether the drop comes from preprocessing, calibration, fake quantization, fixed-point conversion, compilation, or board-side runtime. This Skill systematically locates the first stage where accuracy diverges, so you fix the actual root cause instead of tuning parameters blindly. ## Core Features & Use Cases - Stage-by-stage comparison: Builds a stage matrix over fixed samples covering float, calibration/fake-quant, quantized, compile, and runtime outputs, computing task metrics and numerical differences such as cosine similarity and max absolute error. - Single-variable experiment design: Produces one prioritized experiment and one fallback (e.g., replacing the calibration set, fixing preprocessing, adjusting one qconfig item, or extending QAT) with expected outcomes, stop conditions, and rollback plans. - Structured handoff: Routes unresolved issues to the right workflow — calibration data preparation, PTQ config authoring, or QAT training — and stays read-only without retraining or recompiling. - Use Case: You have floating-point, PTQ, and board-side metrics for the same evaluation set and the board-side accuracy dropped sharply. Use this Skill to identify that the first divergence appears at the fixed-point conversion stage, linked to calibration saturation, and receive a targeted single-variable fix. ## Quick Start Ask the agent to diagnose where the accuracy drop first occurs using your floating-point, calibration, quantized, and board-side metrics on a fixed set of input samples.

Frequently Asked Questions about x5-accuracy-diagnostics

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

FAQPage Schema
How do I find where quantization accuracy drops in a PTQ pipeline?▼

Build a stage matrix over fixed samples covering float, calibration/fake-quant, quantized, compile, and runtime outputs, then compute task metrics and numerical differences like cosine similarity and max absolute error. The first stage exceeding your threshold is where the accuracy drop originates.

How to debug accuracy loss in X5 QAT models?▼

Compare floating-point, fake-quant, fixed-point, and board-side metrics on the same evaluation set with identical preprocessing and label mapping. Keep QAT .hbm/.hbir artifacts separate from PTQ .bin outputs, since their tool parameters are not cross-comparable.

Why do quantization metrics differ between stages on the same model?▼

Differences often come from inconsistent preprocessing, dtype/layout or color format mismatches, duplicated or missing mean/scale normalization, or differing evaluation criteria. Verify all stages use the same preprocessing, postprocessing, and label mapping before comparing numbers.

Does this diagnostic workflow retrain or recompile the model?▼

No. The analysis is read-only: it compares existing metrics and dumps, then designs a single-variable experiment. Regenerating calibration sets, retraining, or recompiling must be handed off to the corresponding workflow with cost and output directory confirmation.

What inputs are needed to diagnose quantization accuracy issues?▼

You need metrics from each quantization stage on the same evaluation set, fixed samples with per-stage outputs or dumps, the calibration manifest, YAML/QAT source and logs, plus evaluation code, thresholds, and model/data hashes for reproducibility.

What happens when the accuracy drop stage cannot be located?▼

The Skill lists the minimum missing dumps or metrics and remains in a blocked state rather than guessing. It will not emit an unordered list of parameter tweaks; each hypothesis is attempted at most twice before handoff.