Understanding the PIDoctor tune score
The tune score sums up how good your tune really is — not by feel, but measurably. What matters, though, is not just the number but the sub-scores behind it.
How the score is composed
The overall score (0–100 with a grade) is fed by several dimensions: tracking and step response (the PID side) plus noise and filter effectiveness (the filter side). That separation is exactly what tells you which problem is yours.
What a good number is
Roughly: 80+ (grade A/B) is a solid, well-flyable tune; 60–80 has clear room; below 60 usually means a concrete problem. A high overall value with one red sub-score is more telling than the average alone.
Stability becomes measurable
Beyond the step response, PIDoctor estimates control-theory metrics like phase margin — how far your tune is from instability. That turns a feeling (feels sharp) into a solid statement (has margin left or not).
From score to change
The score isn't an end in itself: each weak sub-score points to concrete CLI commands and the matching guides. You don't just see that something is off, but what to do about it — and on the next log, whether it helped.