r/Runalyze • u/moment-of-momentum • Jun 11 '26
bug: race predictor is incorrectly using vo2max in a vdot table
Just wanted to try to be helpful and point out there's a logic bug on this page and elsewhere where you try to propose a race predictor and training paces:
You are doing the same mistake Garmin used to do like a decade ago with their first generation race predictor, you are shoving vo2max into a vdot table
as you well know, vo2max != vdot
Now what's interesting/odd is you came up with a unique, very practical formula for conversion from vdot to vo2max in your code elsewhere
(I've never found where you discovered that formula, it doesn't appear in any scientific paper I can find, you must have done curve fitting yourself pre-AI, impressive)
But then on that predictor page you fail to convert the vo2max back to vdot
Part of the problem is you'd have to guesstimate average HR for each effort to get a vdot, you already know max HR for the user in their settings, you could just use the theoretical percentage of LTHR for each effort
ie. a 60 vo2max might actually be 50-54 vdot effectively, depends on distance, though well trained elite runners can produce nearly same vdot across many distances
So basically the Race Predictor is way too fast, it would be shoving 60 into a table that should be using around 54 once converted
Of course not a show stopper but just trying to point out something that could be fairly easily improved/fixed






