Question about TS on fractals..

[lone speed]

Ted.....

I was curious if the calculations for TS on Rdss are the same as from older programs before Validator or have they evolved????:)

[Ted Craven]

True Speed in RDSS (and Speculator and Validator for sure, also likely Synthesis, working our way backward in the historical sequence of programs) - is one of the simplest calculations we use. It is simply: today's race distance (not the original distance of the paceline) divided by Final Adjusted Time ('Adjusted' by DTV, ITV, distance and surface equalizations to today). In other words, average velocity from beginning to end - no segments. It is also distinct from Total Energy which is the sum of the 3 fractional velocities.

Not possessing the code for earlier software (except EXDC/Thoromation) I cannot answer accurately if TS True Speed (or Total Speed, whatever) on Fractals, or Quad-Rater, or PaceLauncher or API (written for Doc by Guy Wadsworth), or other programs written by Jim Bradshaw which may use the TS caption - are based on the same formula. Sorry about that.

But the above is the absolute calculation today (and since circa 1998) for True Speed. You can try a few examples in RDSS (or in screenshots you see) by taking using Adjusted Final Time from the Adjusted Screen and dividing it into today's race distance and observing the resulting velocity on the Velocity Screen, PoH (use races which the horse won, so you don't have to deal with the effect of beaten lengths) - OR, check velocities under TS on the Velocity Screen, PoR, which exclude beaten lengths (since Velocity PoR relates to pace of the race, not pace of the horse).

33381

RDSS2 rounds up to the nearest 1 decimal place.

Lonespeed, I apologize: I know I owe you responses on a couple of other posts regarding RDSS factors as they relate to older ones, and will get to them this weekend!

cheers,

Ted

[lone speed]

True Speed in RDSS (and Speculator and Validator for sure, also likely Synthesis, working our way backward in the historical sequence of programs) - is one of the simplest calculations we use. It is simply: today's race distance (not the original distance of the paceline) divided by Final Adjusted Time ('Adjusted' by DTV, ITV, distance and surface equalizations to today). In other words, average velocity from beginning to end - no segments. It is also distinct from Total Energy which is the sum of the 3 fractional velocities.

Not possessing the code for earlier software (except EXDC/Thoromation) I cannot answer accurately if TS True Speed (or Total Speed, whatever) on Fractals, or Quad-Rater, or PaceLauncher or API (written for Doc by Guy Wadsworth), or other programs written by Jim Bradshaw which may use the TS caption - are based on the same formula. Sorry about that.

But the above is the absolute calculation today (and since circa 1998) for True Speed. You can try a few examples in RDSS (or in screenshots you see) by taking using Adjusted Final Time from the Adjusted Screen and dividing it into today's race distance and observing the resulting velocity on the Velocity Screen, PoH (use races which the horse won, so you don't have to deal with the effect of beaten lengths) - OR, check velocities under TS on the Velocity Screen, PoR, which exclude beaten lengths (since Velocity PoR relates to pace of the race, not pace of the horse).

33381

RDSS2 rounds up to the nearest 1 decimal place.

Lonespeed, I apologize: I know I owe you responses on a couple of other posts regarding RDSS factors as they relate to older ones, and will get to them this weekend!

cheers,

Ted

Ted...:cool:

Thanks for the quick response and detailed explanations....you do not owe me any explanations as you are the one with a full plate with the release of Rdss 2.0 and trying to make videos for Rdss aspirants, and most importantly, to make a prosperous living in this endeavors........