Hi,
I've been using TPD today very successfully! So I automated a few things and again worked brilliantly, but then I start getting weird results in the averages, see below (this was happening IP, I just didn't get the screenshot on time as I was on a call).
The averages were way out! 700mph horse at 740, I'd have backed that I did change the "Connect to TPD" rule to start 30seconds before the start time, but it was working fine for the other races.
Any ideas? I'll try again tomorrow and see how I get on. Also what US tracks does TPD support?
Thanks
Chris
Strange results with TPD??
-
- Posts: 23
- Joined: Wed Jul 15, 2020 10:06 am
You do not have the required permissions to view the files attached to this post.
It looks like you MPH are very similar to the price of the runner, so perhaps you're overwriting the history list that is used to create the 5 & 10 second moving averages. i.e. You're overwriting the speed with the current price and so it's taking the moving average of that
- jamesedwards
- Posts: 2315
- Joined: Wed Nov 21, 2018 6:16 pm
My guess would be it's a glitch in the tracking. If the tracker loses connection for a few seconds then I assume the system just sees the horse magically move X metres in a millisecond, hence the sudden whacky increase in reported speed?
-
- Posts: 23
- Joined: Wed Jul 15, 2020 10:06 am
100% User Error! sorry!
I was working with other automation files and imported a rule that also utilized "History List 1". I simply changed this to another history list and all sorted.
I traded 3 races manually and made £3 a race with £2 stakes, really with no effort at all. I was just playing around.
Can't wait to test again tomorrow and if I get the automation correct then this is going to be a game changer!
Cheers
Chris
I was working with other automation files and imported a rule that also utilized "History List 1". I simply changed this to another history list and all sorted.
I traded 3 races manually and made £3 a race with £2 stakes, really with no effort at all. I was just playing around.
Can't wait to test again tomorrow and if I get the automation correct then this is going to be a game changer!
Cheers
Chris
- jamesedwards
- Posts: 2315
- Joined: Wed Nov 21, 2018 6:16 pm
@BetAngel, would be useful to understand how the system handles connection drop outs.jamesedwards wrote: ↑Wed Nov 10, 2021 8:39 pmMy guess would be it's a glitch in the tracking. If the tracker loses connection for a few seconds then I assume the system just sees the horse magically move X metres in a millisecond, hence the sudden whacky increase in reported speed?
This page lists all the UK and US tracks supported by TPD, its worth noting not all the US tracks are available on Betfair
https://www.totalperformancedata.com/datafeeds
There is a new Total Performance Data condition which allows you to test if the last update was received within a specified time frame, which enables you to ensure your rule/s don't trigger on old/stale datajamesedwards wrote: ↑Wed Nov 10, 2021 8:53 pm@BetAngel, would be useful to understand how the system handles connection drop outs.jamesedwards wrote: ↑Wed Nov 10, 2021 8:39 pmMy guess would be it's a glitch in the tracking. If the tracker loses connection for a few seconds then I assume the system just sees the horse magically move X metres in a millisecond, hence the sudden whacky increase in reported speed?
https://www.betangel.com/user-guide/tot ... ata_1.html
Also if the connection to TPD is broken, or if no new data arrives when expected, Bet Angel will auto-recover the connection. The number of times it’ll attempt this per race is configurable in the settings.
However as Dallas mentioned, the TPD Automation Condition is your best defence and allows you to stop betting and perhaps trigger greening if required, if the data update hasn’t occurred in your specified timeframe.
However as Dallas mentioned, the TPD Automation Condition is your best defence and allows you to stop betting and perhaps trigger greening if required, if the data update hasn’t occurred in your specified timeframe.