Seconds per mile

[Dynamite21]

…
The RACING POST topspeed guru is Dave Edwards, his team come up with the Going Correction.
They no doubt trim out the blatantly slow or super fast races, take into account the wind, going stick, previous similar G.C. assessments and their secret sauce. (It’s best guess terrority, really)
in this case it’s (0.24) …Good/Good to Firm

If you produce your own Going Corrections and Standard Time Averages you will get your own
SPEED RATINGS. (it makes me twitch just thinking about amount of work involved)

“Mordin on Time”

Mordin On Time Reviewed

D21

ps “another speed ace guy is Andy Holding”

[twmills]

Mordin on time is selling fromm £200-£700 on ebay, so not sure abot that, and Andrew Holding does he show anywhere how he calulates his figures.

[Dynamite21]

…………….WOW! deal ive got a copy……………
(might produce some scans when iam less busy)

Andy Holding service does all the work.
https://andyholdingspeedfigures.co.uk/

[Dynamite21]

how do i go about geeting this into excel.

(rightCLICK “View Image” …to enlarge”)

D21

[twmills]

Thank you D21 have it now in excel, but still need to know about calculating the going correction, in order to do the figures.

[Dynamite21]

The RACING POST topspeed guru is Dave Edwards, his team come up with the Going Correction. They no doubt trim out the blatantly slow or super fast races, take into account the wind, going stick, previous similar G.C. assessments and their secret sauce. (It’s best guess terrority, really)

your just GOING to have to create your own method.
Use any and every number variable available.
Slowly run races are the main problem
A lot of the meetings may produce no worthwhile G.C. so you will have to make an educated guess.
Most of the calculations will be based on the Standard Average time (comparison -/+)
more of an art than a science

Here’s a baseline G.C. framework
(Firm)…………+1.00s/f to +0.57s/f _f1,f2,f3,f4,f5
(Good/Firm)…+0.56s/f to +0.36s/f _m1,m2,m3,m4,m5
(Good)………..+0.35s/f to -0.35s/f _g1,g2,g3,g4,g5
(Good/Soft)…..-0.36s/f to -1.19s/f _y1,y2,y3,y4,y5
(Soft)………….-1.20s/f to -1.49s/f _s1,s2,s3,s4,s5
(Heavy)……….-1.50s/f to -3.00s/f _v1,v2,v3,v4,v5

Best of luck

D21 “God bless the RACING POST going correction …is what i say “

[twmills]

How to do you determine the going correction from that framework, in the example they had 0.24 as going correction G/F is that right. how did they arrive at 0.24. why not 0.56 0r 0.36.

[Dynamite21]

…
Dealing with going descriptions can get VERY MESSY, i have simplified this by giving it a discrete two character data tag. In this way it’s easy to use with coding projects or database manipulation.
This is done manually with experience and best guess FEEL.
(takes me about 40mins per week)

f1 =(is this safe? almost HARD
f2
f3 =(FIRM)
f4
f5
m1 =(borderline almost firm) (0.56 here)
m2
m3 =(GOOD/FIRM)
m4
m5 (0.36 here)
g1 =(borderline almost good/firm
g2
g3 =(GOOD)… 0.24 lives here or maybe g2
g4
g5
y1
y2
y3 =(GOOD/SOFT)
y4
y5 =(borderline almost SOFT)
etc…

THE BIG PROBLEM THOUGH… the g.c.
includes a wind consideration >>>

it’s an inexact science… give up now
unless you want to WORK like a dog with a bone.

D21

“the only thing that matters …is bottomLine annual PROFIT”

[Author]

Posts