Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Working really well, one question #7

Closed
stevemoulton opened this issue Feb 18, 2019 · 2 comments
Closed

Working really well, one question #7

stevemoulton opened this issue Feb 18, 2019 · 2 comments

Comments

@stevemoulton
Copy link

Hi

Just wanted to check in and say that I found this yesterday and in about an hour I had every Cheltenham race since 2010 in a sqlite database and I'm having great fun messing around with the data.
Just one thing I wanted to ask about, it looks like you are using some algorithm to approximate the times of all horses (except the winner) as bizarrely this information still isn't made available in racing. Could you give me a brief rundown of how the algorithm works?

Thanks again
Steve

@joenano
Copy link
Owner

joenano commented Feb 18, 2019

"Distances are calculated on the elapsed time between each horse and then a scale known as the Lengths per Second Scale (Lps) is used dependent upon whether it is Flat or Jumps racing, the type of surface in use at the all-weather fixtures and the official going description issued on the day. The Scales used vary from four to five Lps for Jumps racing and from five to six Lps on the Flat."

https://www.britishhorseracing.com/wp-content/uploads/2014/04/Lengths-Per-Second-Scale-Tables-2019.pdf

The algorithm is just reversing this.

@stevemoulton
Copy link
Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants