TPD Feedback and Issues
-
- Posts: 41
- Joined: Mon Jun 05, 2017 3:38 pm
Belmont at the Big A not being recognised as a supported track
Its Aqueductsheffutd1889 wrote: ↑Thu Sep 14, 2023 6:43 pmBelmont at the Big A not being recognised as a supported track
We are aware of there has been a change of name for the Belmont Fall Meeting and will be updating in the software asap in the coming daysNaffman wrote: ↑Thu Sep 14, 2023 7:01 pmIts Aqueductsheffutd1889 wrote: ↑Thu Sep 14, 2023 6:43 pmBelmont at the Big A not being recognised as a supported track
Just an update to let you's know the names have been remapped so should now be working, but any problems just drop a note hereDallas wrote: ↑Thu Sep 14, 2023 7:21 pmWe are aware of there has been a change of name for the Belmont Fall Meeting and will be updating in the software asap in the coming daysNaffman wrote: ↑Thu Sep 14, 2023 7:01 pmIts Aqueductsheffutd1889 wrote: ↑Thu Sep 14, 2023 6:43 pmBelmont at the Big A not being recognised as a supported track
-
- Posts: 41
- Joined: Mon Jun 05, 2017 3:38 pm
Thanks Dallas.
Missed this post in time for tonight's fixture but will reload ready for tomorrow
Missed this post in time for tonight's fixture but will reload ready for tomorrow
- jamesedwards
- Posts: 2934
- Joined: Wed Nov 21, 2018 6:16 pm
Had a few races today with very brief data-flow outages affecting at least speed, but possibly more.
Some races affected;
Brighton 17:40
Keeneland 18:00
Keeneland 18:32
Last one cost me a bit. Will be switching off TPD for the rest of the day.
BA speed graph for Keeneland 18:32 below:
Some races affected;
Brighton 17:40
Keeneland 18:00
Keeneland 18:32
Last one cost me a bit. Will be switching off TPD for the rest of the day.
BA speed graph for Keeneland 18:32 below:
jamesedwards wrote: ↑Thu Oct 19, 2023 6:42 pmHad a few races today with very brief data-flow outages affecting at least speed, but possibly more.
Some races affected;
Brighton 17:40
Keeneland 18:00
Keeneland 18:32
Last one cost me a bit. Will be switching off TPD for the rest of the day.
BA speed graph for Keeneland 18:32 below:
Capture.PNG
Yep I had same issues with the 1740 Brighton and there were others who reported issues on the telegram chat. I called it a day whilst I was up as I nearly lost money on the 1740 due to it cutting out 3 times in the middle of that race.
Good Morning and apologies to the disruption to the data feed, which a number of you will have experienced yesterday. The Developers are investigating and hopefully a fix will be applied before today's TPD offerings, which have been badly affected by the weather - our first race being the 16:25 at Newcastle.
In the meantime, if you were affected, please drop an email to [email protected], using your TPD account email address and we will of course credit the races back to your account. Many thanks.
In the meantime, if you were affected, please drop an email to [email protected], using your TPD account email address and we will of course credit the races back to your account. Many thanks.
- jamesedwards
- Posts: 2934
- Joined: Wed Nov 21, 2018 6:16 pm
Big data issue in the middle of Keeneland 20:08. Could have cost me a few K but I got lucky. Switching off TPD for the rest of the evening.
Yikesjamesedwards wrote: ↑Fri Oct 20, 2023 8:15 pmBig data issue in the middle of Keeneland 20:08. Could have cost me a few K but I got lucky. Switching off TPD for the rest of the evening.
- jamesedwards
- Posts: 2934
- Joined: Wed Nov 21, 2018 6:16 pm
The issue was 'Smokey Smokey' skipped from 578m-to-finish to 0m-to-finish in the space of 3 secs, even though it was 11th and going nowhere at the time. It traded at least as low as 1.13 in the market so there were some burnt fingers out there.jamesedwards wrote: ↑Fri Oct 20, 2023 8:15 pmBig data issue in the middle of Keeneland 20:08. Could have cost me a few K but I got lucky. Switching off TPD for the rest of the evening.
There were issues at Newcastle today also but think it was the weather effecting the Internet at the track. Id rather leave the races alone than risk it when there are issues.jamesedwards wrote: ↑Fri Oct 20, 2023 8:34 pmThe issue was 'Smokey Smokey' skipped from 578m-to-finish to 0m-to-finish in the space of 3 secs, even though it was 11th and going nowhere at the time. It traded at least as low as 1.13 in the market so there were some burnt fingers out there.jamesedwards wrote: ↑Fri Oct 20, 2023 8:15 pmBig data issue in the middle of Keeneland 20:08. Could have cost me a few K but I got lucky. Switching off TPD for the rest of the evening.
TPD did re credit me a batch of races for yesterday's problems which is fair enough. But yeah if you get burnt it's going to hurt.
I spent 3 hours last night on the US races.
Most were won by a horse breaking away to win although a couple were pipped at the post. On the majority of races the horse that accelerated away to win was not showing on TPD as the fastest horse. Sometimes it was the third or fourth fastest. I can understand a spurt to get away and the others trying to catch up but the winning horse was never the fastest at any stage in these races apart from a couple. This is on speed, last 5 seconds and last 10 seconds.
I could see the horses speeding off on live stream and betangel. Conversely the speed TPD showed for winners in UK races was accurate.
Is this how it normally works with TPD on US tracks?
Most were won by a horse breaking away to win although a couple were pipped at the post. On the majority of races the horse that accelerated away to win was not showing on TPD as the fastest horse. Sometimes it was the third or fourth fastest. I can understand a spurt to get away and the others trying to catch up but the winning horse was never the fastest at any stage in these races apart from a couple. This is on speed, last 5 seconds and last 10 seconds.
I could see the horses speeding off on live stream and betangel. Conversely the speed TPD showed for winners in UK races was accurate.
Is this how it normally works with TPD on US tracks?
- jamesedwards
- Posts: 2934
- Joined: Wed Nov 21, 2018 6:16 pm
Can you name a couple of specific races where you saw this happen.parrettt wrote: ↑Sun Oct 29, 2023 1:08 pmI spent 3 hours last night on the US races.
Most were won by a horse breaking away to win although a couple were pipped at the post. On the majority of races the horse that accelerated away to win was not showing on TPD as the fastest horse. Sometimes it was the third or fourth fastest. I can understand a spurt to get away and the others trying to catch up but the winning horse was never the fastest at any stage in these races apart from a couple. This is on speed, last 5 seconds and last 10 seconds.
I could see the horses speeding off on live stream and betangel. Conversely the speed TPD showed for winners in UK races was accurate.
Is this how it normally works with TPD on US tracks?
29-Oct-23 00:41 29-Oct-23 00:50
Horse Racing / Santa Anita Park (US) 28th Oct : R7 1m Allw Claim
28-Oct-23 23:24 28-Oct-23 23:31
Horse Racing / Santa Anita Park (US) 28th Oct : R5 1m Mdn
28-Oct-23 23:07 28-Oct-23 23:19
Horse Racing / Woodbine (US) 28th Oct : R9 1m Allw
28-Oct-23 22:20 28-Oct-23 22:28
Horse Racing / Laurel Park (US) 28th Oct : R7 1m Allw Claim
These are examples
It has me baffled!
Horse Racing / Santa Anita Park (US) 28th Oct : R7 1m Allw Claim
28-Oct-23 23:24 28-Oct-23 23:31
Horse Racing / Santa Anita Park (US) 28th Oct : R5 1m Mdn
28-Oct-23 23:07 28-Oct-23 23:19
Horse Racing / Woodbine (US) 28th Oct : R9 1m Allw
28-Oct-23 22:20 28-Oct-23 22:28
Horse Racing / Laurel Park (US) 28th Oct : R7 1m Allw Claim
These are examples
It has me baffled!