Measured vs. modeled: not all launch monitor numbers are equal

Not every number on a launch monitor was measured. A range radar tracks the full ball flight, so speed, launch, carry, height, and curve are genuinely seen, but spin is usually inferred from the trajectory unless the facility uses RCT, or marked, balls. A bay unit with a premium ball adds real club data on top: club speed, attack angle, path, and face. Advice built on an inferred number should carry less weight than advice built on a measured one.

So every metric you enter is tagged one of two ways, measured or estimated. There is no third 'converted' tag on your result, and it is worth being clear about that, because the word gets thrown around. Converting or normalizing is something the Trackman app can do to a session before you ever export it, rewriting your numbers to premium-ball equivalents. That happens upstream of us. What Dialed labels is only whether the radar measured a figure or inferred it.

The clearest case is club speed. When your source reports ball flight but no club speed, the engine estimates club speed by dividing ball speed by a fixed factor, about 1.46 for the driver and 1.3 for a 7-iron, and marks the result estimated. That estimate then has a knock-on effect: smash factor is ball speed over club speed, so a smash built on an estimated club speed would just be circular arithmetic. Rather than show a number that only looks like a measurement, the engine drops it, and keeps smash only when both speeds were genuinely measured.

Estimated does not mean ignored; it means discounted, and the discount is concrete. When your spin is estimated rather than measured, any prescription that leans on spin drops one confidence tier, from high to medium, automatically. Your result also carries an overall data-quality grade of minimal, partial, or full, and reaching full requires measured club data. None of this is hedging for its own sake. It is the tool refusing to sound more certain than the data underneath it allows.

The practical takeaway is simple. Tell the tool honestly where your numbers came from, because a bay session and a range session are not interchangeable inputs even when the screen looks the same, and the confidence attached to your advice should, and does, move with the quality of what you fed it.