The BTC Horse Racing Thread
-
@robert-cooke is your bot set to take a couple of ticks lower/higher so it gets matched?
-
@fraser-cord I'm happy with today's result just curious about the last one. got on at 2.44. I thought 2.42 was the maximum on my bot.
-
@robert-cooke Cant grumble too much can I. I guess its small differences with speed of fairbot vs BFBM etc but as long as the profit keeps coming, I wont be caring.
-
@fraser-cord 5.00 taunton. Was 2.38
-
My bot only hit 6 today, but all winners, happy days indeed.
What ones did I miss, was on Market 13:45, Taunton 14:30 and 15:30, Wolves 18:00,18:30 and 19:30
-
@lee-colvin what odds was the last one mate.
-
@robert-cooke 7/9 the last one was 2.44 . Not sure why the bot got on that one.
-
Unbelievable day on John’s Short Odds eh? 7/9 and just over 3.5 points profit
-
7/8 for short odds today
-
@michael-meier
Thanks,
Thats the one. -
@philip-brogan said in The BTC Horse Racing Thread:
Hi Martin,
0_1674585045394_rules_export(3).json I have uploaded revision 3.1 Back the Favourite
Many thanks
@Jonathan-Jones This one was posted a few weeks back. I think this is it, but you might want to wait for Martin to confirm.
-
@Martin
You did a video on Back the fav v3. Where is that version please? I tried just adding the age to V2 and wasnt getting anything close to the profits you had with V3 so thinking there must be some other subtly change too (like maybe different course choice). -
@alex-rendell back the favourite if it's in the target odds range, original horse given is irrelevant
-
Hello all, apologies for the newbie Q, but I'm just seeking some clarity please if anyone can help; if the "back the favourite at the off (@ odds 2.50 - 6.0)" strategy generates a selection, are we looking to only back THAT selection if it is the favourite, or are we backing the favourite in that race at the start, regardless of the selection thrown up by the software?
Hope that makes sense! Cheers guys
-
@paul-foster said in The BTC Horse Racing Thread:
@greg-mitchell because it was over 15f the bot discounted it, so there would be a difference between the results and what the bot actually placed. My strat doesn't know the horse selection until the off, so I'm not just using the bot to bet on a specific horse.
@Adam I would prefer to round to the nearest whole furlong please.
Makes sense. I agree
-
@greg-mitchell because it was over 15f the bot discounted it, so there would be a difference between the results and what the bot actually placed. My strat doesn't know the horse selection until the off, so I'm not just using the bot to bet on a specific horse.
@Adam I would prefer to round to the nearest whole furlong please.
-
If you are using a strategy developed from back testing the software and using the software to pick your selections it doesn't matter what the distance is set to as will be 15f furlongs in backtesting and selections won't it.
But I guess rounding two the nearest whole furlong makes better sense.
-
@paul-foster The exact distance was actually slightly short of 16 furlongs, which is why it was shown as 15.
If people prefer, we can round to the nearest whole furlong distance value.
-
Just reported an issue with the results on one of my strategies from yesterday.
The 20:30 at Kempton yesterday has come up with a selection, but this race was outside of my criteria as the race was 2-miles, so 16f, however the software has this listed as 15f. My strategy race distance criteria is for 15f or less.
I only noticed bacause I was testing an tweak to my bot and so was paying attention to the reports tab, so not sure if this is a one off, but worth keeping an eye on when looking at differences between actual bets placed and when the software is reporting.
