Save that message for when it happens again.lotora wrote: ↑Mon Aug 12, 2024 7:56 pmThanks!jamesedwards wrote: ↑Mon Aug 12, 2024 4:39 pmIt turns out that Colonial Downs delayed their racing by three hours vs publicised off-time yesterday, so for once this one wasn't Betfair's fault.
TPD Feedback and Issues
- jamesedwards
- Posts: 2925
- Joined: Wed Nov 21, 2018 6:16 pm
Hey James, definitely, my conversations with Betfair are automatically saved, so if anyone else encounters similar issues, just post them here, and I'll take it up with Betfair.jamesedwards wrote: ↑Mon Aug 12, 2024 8:26 pmSave that message for when it happens again.lotora wrote: ↑Mon Aug 12, 2024 7:56 pmThanks!jamesedwards wrote: ↑Mon Aug 12, 2024 4:39 pmIt turns out that Colonial Downs delayed their racing by three hours vs publicised off-time yesterday, so for once this one wasn't Betfair's fault.
-
- Posts: 2
- Joined: Fri Jul 12, 2024 7:37 am
13/08/2024 Lingfield race 1, my Guardian automation recorded what may be some TPD data errors relating to the winner Split Elevens. My bot stores various TPD metrics at intervals of 1 second after inplay.
The first six seconds show 'Distance behind leader' for this horse to be:
12.8
19.2
9.3
9.1
6.5
5.2
Speed:
7.83
7.83
14.74
13.47
16.36
17.04
VER:
448
481
432
467
481
476
Watching the replay of the race, the first two metrics don't match what occurred. Assuming this is a TPD error, which I expect on occasion, my query relates to VER. Does this type of early error affect the calculation of VER throughout the race?
The first six seconds show 'Distance behind leader' for this horse to be:
12.8
19.2
9.3
9.1
6.5
5.2
Speed:
7.83
7.83
14.74
13.47
16.36
17.04
VER:
448
481
432
467
481
476
Watching the replay of the race, the first two metrics don't match what occurred. Assuming this is a TPD error, which I expect on occasion, my query relates to VER. Does this type of early error affect the calculation of VER throughout the race?
Re Lingfield race 1, 13 Aug; Unfortunately there was only 84% radio success at the start of the race and hence the errors. To confirm that the calculation of VE (Velocity Error) later in the race would not be affected by the earlier flawed data - the calculation is constantly comparing the velocity of each horse to the par value at that particular point in the race. Hope this provides the necessary clarity.
-
- Posts: 2
- Joined: Fri Jul 12, 2024 7:37 am
Hi, thanks. I became aware of various warning flags available in the newer beta version, so will use it in future. In a situation like that with 84% radio success at the start, would a Data Accuracy Warning flag activate?
Hi yes to a Data Accuracy warning re the 84% radio success if this was spotted in "real time" so to speak. However, on this occasion it was only diagnosed a short time after the race had finished.aronpeace2015 wrote: ↑Fri Aug 16, 2024 11:53 amHi, thanks. I became aware of various warning flags available in the newer beta version, so will use it in future. In a situation like that with 84% radio success at the start, would a Data Accuracy Warning flag activate?
Used TPD for the first time today on races at Windsor.
Seems pretty good however a couple of issues I had. In the race in the 19.45 I think it was, the TPD live map had horse number 3 in front by a decent advantage very close towards the end of the race,however when I glanced at the in play trader odds they were very low (1.40-1.60) for Horse number 1 which the data showed to be in 3rd I think at that exact time.
Seemed like an obvious mistake and within seconds the TPD live map "caught up" with the odds and Horse number 1 went on to win.
Second issue was the colour scheme of the live map data, Horse number 3 is shown in red but the actual silks are blue for example. Blue is shown as a different horse. Quite confusing, is there any way I can edit them myself or get them to match?
Thanks for any help.
Seems pretty good however a couple of issues I had. In the race in the 19.45 I think it was, the TPD live map had horse number 3 in front by a decent advantage very close towards the end of the race,however when I glanced at the in play trader odds they were very low (1.40-1.60) for Horse number 1 which the data showed to be in 3rd I think at that exact time.
Seemed like an obvious mistake and within seconds the TPD live map "caught up" with the odds and Horse number 1 went on to win.
Second issue was the colour scheme of the live map data, Horse number 3 is shown in red but the actual silks are blue for example. Blue is shown as a different horse. Quite confusing, is there any way I can edit them myself or get them to match?
Thanks for any help.
Hi Just had a look at the 19:45 at Windsor and #1 was a non-runner!! We are talking Sat 24th Aug? Anyway re the colour scheme of the live map data; if in Bet Angel you navigate to Settings / Edit Settings / Total Performance Data / here you will find the "Runner colours" drop down menu via which you can chose how they are displayed. Hope this helps and apologies for the delayed response.Scotty66 wrote: ↑Sat Aug 24, 2024 11:07 pmUsed TPD for the first time today on races at Windsor.
Seems pretty good however a couple of issues I had. In the race in the 19.45 I think it was, the TPD live map had horse number 3 in front by a decent advantage very close towards the end of the race,however when I glanced at the in play trader odds they were very low (1.40-1.60) for Horse number 1 which the data showed to be in 3rd I think at that exact time.
Seemed like an obvious mistake and within seconds the TPD live map "caught up" with the odds and Horse number 1 went on to win.
Second issue was the colour scheme of the live map data, Horse number 3 is shown in red but the actual silks are blue for example. Blue is shown as a different horse. Quite confusing, is there any way I can edit them myself or get them to match?
Thanks for any help.
- jamesedwards
- Posts: 2925
- Joined: Wed Nov 21, 2018 6:16 pm
Not been getting any Horseshoe Indianapolis data this evening.
This appears to have been caused by a timing issue - one of the data suppliers had the race times incorrectly loaded in their systems. The Developers are looking at how this happened with a view to circumventing any future such issues. Apologies for the inconvenience.jamesedwards wrote: ↑Tue Sep 10, 2024 10:00 pmNot been getting any Horseshoe Indianapolis data this evening.