Forum Replies Created
-
Posts
-
Hi Kieran,
Thanks for the question… the short answer is, it depends on the prediction models the system generates each night.
At the moment the system is picking runners that are on average position 1.3 in the pre-race betting order. The number 1.3 means the sytem will heavily prefer favourites, but will occassionally go for a runner in position 2, or maybe position 3, in the betting order.
At other times this year, the system has generated models that pick runners, further down the betting order. We have prevously seen models averaging position 3.5, which usually means the system has no idea what its doing! We tend to pause betting when these types of models appear.
At this point in the season I can see from the model predictor weightings, that the system in preferring speed ratings, presumably because most horses have now had a few runs throughout the summer. Speed ratings are not reliable at every part of the year – their predictive strength, like all predictors, varies constantly.
Hope that helps,
Cheers
Nick.There is something else you might like to include – is a check to see if we recommend betting at the present time. This is a new feature we are adding today:
You can make a direct call to this URL to see our Betting Status:
Our Betting Statusor via CURL:
GET https://tips.flat-racing.com/wp-json/wp/v2/pages?slug=our-betting-status
Hi,
Tips are published 30 seconds before a race start time. They remain on the server for 60 seconds after the start time.
This list of races for each day is published here: Racing Schedule
The Stop Loss mechanism is handled on our side. We simply stop publishing tips for a specific race course, or on a specific day when loss limits have been reached. You should bet immediately when a tip is retrieved, though we recommend submitting the bet for BSP (starting price). See Pre Race Prices versus BSP for the current pre-race prices compared to the starting Price.
A tip will look like this in html:
2020-09-02 15:30:00Al Daiha,2Al Daiha,3Al Daiha,4Al Daiha,5Al Daiha,6 The format is: (race time), (Runner name),(prediction model number (1-6))
Whereas when a course OR daily stop loss has been reached, you will see this message:
‘2020-09-02 17:05:00,Daily Stop Loss triggered. ‘You should keep polling our servers until the last race of each day, due to the way the Gen2 Stop Loss works, see Gen2 Stop Loss.
Let me know if you need more guidance,
Cheers
NickI’m changing some of the code today (in between races). When I restart the system, occasionally it throws a stop-loss message, when the SL is NOT activated.
Apologies for confusion… it will carry on though.
BetDAQ seemed to have fixed the problem, the runner names are back to the usual format.
Issue resolved for the 13:15 hrs race at Uttoxeter.
If you’re using BetDAQ, most likely you will have missed the first few tips of the day.
Cheers
NickHi Roman,
Have a look in the “Service Status” forum, a new version of the spreadsheet has been released tonight, v2.02, it might help.
If that doesn’t work, get me via webchat tomorrow..
Cheers
Nickhi Dan,
saving results is a Gruss feature.
you might get some joy by trying the Gruss forum
cheers
nickThat’s a great idea…
We’ll abandon the current method of “Service Status” messages (on the home page), and create a new forum, called “Service Status”.
You can subscribe to any of the forums on this site (I guess you probably already know that!)
thanks again,
Cheers
NickThanks Andrew – superb info there..
We’ve run the system on several really old, 2008! spec, refurbished business laptops (from various sellers on eBay for around £150). Typical spec is Intel i5 (3rd generation), dual core, 8gb ram. Model HP 8470p or similar.
I still use several of these laptops today, they were standard issue when I worked for HP, solid machines to this day. So a VPC of similar spec or higher should be fine.
I’ll have a read of the link for “simplyhosting” when time permits – but thanks very much – hope others will contribute their experiences too.
Cheers
Nick
